Skip to content

Develop

This section is for extending CraftBot rather than driving it. Extending means adding new capability to the agent and its runtime: a single action that calls your code, a skill that packages a repeatable workflow, an integration that connects a new external service, or an agent bundle with its own personality and knowledge. It also means understanding the architecture the agent runs on, so your addition lands in the right place and loads the way the built-in ones do. Every extension point below follows the same shape: you write plain Python or a small bundle of files, register it, reload, and the agent can use it. Read Architecture first if you want the map before you build; jump straight to a build page if you already know what you need.

Extension points

  • Architecture

    How the agent_core engine, the app runtime, and their data flows fit together. Read this first.

  • Custom action

    Write one action: a Python function with input and output schemas the agent can call.

  • Skills overview

    What a skill is, when to write one, and where skills live on disk.

  • Write a CraftBot skill

    Scaffold a skill, define its actions and prompt, reload, and test it end to end.

  • External skills

    Load community-built or shared skills from disk without adding them to the repo.

  • Custom agent

    Subclass AgentBase into a bundle with its own personality, RAG docs, and actions.

  • Custom integration

    Add a new external service (a messaging platform or SaaS API) to the integration framework.

  • Contributing

    Development setup, the branch and PR workflow, and how to run lint and smoke tests locally.

Which extension point do I need?

Match your goal to the page that covers it.

Your goal Extension point Page
Give the agent one new tool that calls your code or an API A custom action Custom action
Package a repeatable workflow (actions plus prompt instructions) the agent loads on demand A skill Write a CraftBot skill
Reuse a skill someone else wrote, or share yours across machines An external skill External skills
Connect a new external service with authentication and a listener An integration Custom integration
Ship a dedicated agent with its own persona and knowledge base An agent bundle Custom agent
Import tools from an existing MCP server instead of writing code An MCP connection MCP servers
Understand where any of the above plugs into the runtime Architecture reference Architecture

Actions are the primitive underneath every extension point. A skill groups actions, an integration adds actions plus a connection and listener, and an agent bundle can ship its own actions alongside a personality. When you are unsure whether you need an action or a skill, start with a custom action and promote it to a skill once you have more than one related action to package.

Next