Block Guideline

[ntindle]

We need a place for best practices for blocks before we start building tons of them

• What is a block?
  • Examples
  • A block should be thought of as a single verb-noun pair ex Call LLM
  • What isn't a block?
    • An Agent!
    • A process such as scheduling a task is an agent but connecting to your calendar is a block
• Guidelines to follow
  • Naming, inputs, outputs
  • General Purpose use, while keeping value. We want them to be general, but they should be easy to use. When in doubt, remember Blocks can inherit from base blocks, so you can have generic code but useful blocks.

[github-actions[bot]]

This issue has automatically been marked as stale because it has not had any activity in the last 50 days. You can unstale it by commenting or removing the label. Otherwise, this issue will be closed in 10 days.

[ntindle]

@Bentlybro is this something that's on your schedule

[github-actions[bot]]

This issue has automatically been marked as stale because it has not had any activity in the last 50 days. You can unstale it by commenting or removing the label. Otherwise, this issue will be closed in 10 days.