BoldCreate CLI can be adapted to a project and workflow with instruction files, skills, custom agent files, and MCP servers. Use these features to give the agent project-specific guidance, reusable procedures, a specialized role, or access to external tools.
Choose the right extension
| If you want to… | Use… | How it helps |
|---|---|---|
| Give the agent guidance that should apply to a project or to all your work | Instruction files, such as AGENTS.md | Provides standing context and working rules to the agent. |
| Package a repeatable procedure for a specific kind of task | Skills | Lets the agent load step-by-step instructions when relevant, or lets you run a skill with /skill:<name>. |
| Give the agent a specialized role and instructions | A custom agent file | Starts a session with instructions from a Markdown file, optionally with a name, description, and model. |
| Let the agent use an external service or tool | An MCP server | Provides tools through a local command (stdio) or remote HTTP service. |
Plugins installed in Bold Create can bring skills, agents, rules, and tool servers too. See Plugins, skills, agents and rules.
These features can be combined. For example, project instructions can describe coding conventions, a skill can guide a release-note workflow, a custom agent can review changes, and an MCP server can provide access to an external service.
Instruction files: set project context
Instruction files provide guidance that BoldCreate reads while working. The CLI supports personal and project-level files, including AGENTS.md and compatible formats such as CLAUDE.md, .github/copilot-instructions.md, and scoped rules.
Personal instructions can express preferences that apply across projects. Put shared project facts and team conventions in the repository so collaborators can use them too. More specific instructions can override more general ones when they disagree.
Use instruction files for durable guidance such as:
- Project structure and important components
- Build, test, and lint commands
- Coding conventions
- Files or operations the agent should avoid
Keep instructions focused and actionable. Skills are a better fit for detailed procedures that apply only to certain tasks.
See Project context and instruction files for supported locations and details.
Skills: provide reusable workflows
A skill is a folder containing a SKILL.md file with instructions for a type of task. BoldCreate reads a skill’s name and description to decide whether it applies, then opens the instructions when needed. You can also run one directly by typing /skill:<name> in a chat.
Use skills for repeatable workflows such as preparing release notes or performing a particular review. A skill can include supporting files, such as templates, alongside SKILL.md.
See Skills for locations, required frontmatter, and how to identify skill errors.
Custom agent files: specialize a session
A custom agent file defines a role through Markdown instructions. Start BoldCreate with --agent-file and a path relative to the workspace:
boldcreate --agent-file .boldcreate/agents/reviewer.agent.mdOptional YAML frontmatter can provide the agent’s name, description, and model. Custom agents have access to tools like the standard agent, while the session’s approval mode still applies. Use the built-in Ask or Plan agents when you want read-only answers or planning rather than file changes.
See Custom agent files.
MCP servers: connect external tools
MCP (Model Context Protocol) servers provide tools from an external program or service. BoldCreate CLI supports local command (stdio) servers and remote HTTP servers. Manage them with boldcreate mcp commands or from within a chat.
Servers can be saved for your user account or in a project. User servers are available across your folders. Project servers apply to that project; command servers from a project configuration do not start until you trust the folder.
Use environment variables for secrets rather than placing credentials directly in configuration files. In manual approval mode, BoldCreate asks before using external tools unless you have allowed them for the session or configured them as approved.
See Manage MCP servers for commands and configuration, and Connecting MCP servers: step-by-step examples for setup walkthroughs.
A practical setup sequence
- Add concise project instructions in an
AGENTS.mdfile. - Create skills for procedures you repeat, and keep their instructions in
SKILL.md. - Add a custom agent file when a task needs a distinct role or review approach.
- Configure an MCP server only when the agent needs external tools.
- Review the project configuration and trust project MCP command servers only when you recognize and approve them.
- Start a session and check which instruction files and skills were loaded. Run
boldcreate mcp listto check configured MCP servers.