Guide · Agent skill
How to use the Create Forge Agents agent skill (create-agent)
Updated · written with AI from the project's own documentation and checked against our catalogue data
The create-agent skill teaches an AI agent the exact file format that the code-forge application expects for custom agents. It is for developers who want to define their own specialized agents for code-forge, and for teams that want agent definitions to look the same across a project. After this guide you will know how to install the skill, ask for a new or changed agent in plain language, and check the result.
Quick start
- 1Download the ZIP. Download the create-agent ZIP from this page. It contains SKILL.md.
- 2Install the skill. Unzip it into ~/.claude/skills/ for all projects, or into a project's .claude/skills/ folder. In the Claude apps, upload it under Settings → Capabilities → Skills.
- 3Confirm you use code-forge. The skill only produces files that the code-forge application loads, so make sure your project runs code-forge.
- 4Describe the agent. Ask in plain language for the agent's purpose, tasks, tools and limits.
- 5Save to .forge/agents. Make sure the file is saved as {agent-id}.md in <cwd>/.forge/agents.
- 6Review the file. Check the frontmatter fields, the tools list and the instructions before using the agent.
What is an agent skill and what does this one do?
An agent skill is a folder containing a SKILL.md file that gives an AI assistant extra instructions for a specific task. This skill covers one task: creating and editing agents for the code-forge application.
Agents in code-forge are stored as markdown files. Each file has YAML frontmatter with the fields id, title, description, reasoning, tools and user_prompt, followed by a markdown body with the agent's instructions. When the skill is active, the agent knows this structure and the naming convention, so forge can discover and load the new agent.
- It knows the required frontmatter fields and the body sections to include.
- It places files in the correct folder and names them consistently.
- It does not add any new tools or capabilities to the agent itself.
Install the create-agent skill
Download the create-agent ZIP from this page. The package contains one file, SKILL.md. Install it in one of these ways.
For a personal install that applies to all your projects, unzip it into ~/.claude/skills/. For a single project, unzip it into that project's .claude/skills/ folder.
In the Claude apps, you can instead upload the ZIP under Settings → Capabilities → Skills.
- Personal: ~/.claude/skills/
- Project: .claude/skills/ inside your project
- Claude apps: Settings → Capabilities → Skills, then upload the ZIP
Where agent files must go
Every custom agent must be saved in <cwd>/.forge/agents, where <cwd> is the working directory of your code-forge project. The file name is {agent-id}.md. The source states that this is the only location where forge will discover and load custom agents, so a file saved anywhere else will be ignored.
- Directory: <cwd>/.forge/agents
- File name: {agent-id}.md, for example code-reviewer.md
- Example: a project at /home/user/my-project stores agents in /home/user/my-project/.forge/agents/
Ask for an agent with a natural request
Once the skill is installed, describe the agent you want in plain language. The skill is meant to be used when you need to add a new agent, modify an existing one, or understand the agent file structure.
Give the agent a purpose, the tasks it should handle, the tools it needs and its limits. The source recommends choosing tools by purpose: implementation agents usually use read, write, patch, shell, sem_search and fs_search, while research agents use sem_search, search, read, fetch and sage.
- "Create a code-forge agent called test-automation that writes and runs unit tests. It should use read, write, patch, shell and sem_search."
- "Add a code-forge agent for reviewing pull requests. It is read-only, so give it read, sem_search and fetch."
- "Show me the file structure for a code-forge agent and update my existing reviewer agent's description."
Check the generated agent file
Open the file the agent creates and confirm it matches the required structure: frontmatter with id, title, description, reasoning with enabled set to true or false, tools as a list, and a user_prompt block. The skill does not verify that an agent is safe or well-behaved, so read the tools list and the instructions yourself before relying on the agent.
Check the id and file name match, and that the file sits in <cwd>/.forge/agents.
- Frontmatter fields are all present.
- File name matches the id value.
- Tools list contains only what the agent needs.
- The body covers identity, principles, capabilities, methodology, best practices and limits.
Safety notes
According to the skill's listing, it runs no scripts and uses no network access. It only guides how the agent writes files. The tools you assign to a custom agent determine what that agent can do once forge loads it, for example shell gives it the ability to run shell commands.
Review each new agent's tools list before use, especially if it includes shell, write, remove or wildcard entries such as mcp_*.
- Scripts: none included
- Network: none used by the skill
- Permissions come from the tools list you approve in the agent file
What people use it for
- Building a specialized test-automation agent for a project with its own tool set.
- Creating a read-only research agent that uses sem_search, search, read and fetch.
- Updating the description or tools of an existing agent so forge loads it with the right behaviour.
- Keeping agent definitions consistent across a team by following one file structure.
- Learning how code-forge agent files are structured by asking the skill to explain each field.
Frequently asked questions
Is the create-agent skill free to use?
The source lists the licence as Apache-2.0 for the tailcallhq/forgecode repository that contains this skill. Check the repository's licence file for full terms before reuse.
What do I need to use the create-agent skill?
You need the code-forge application (tailcallhq/forgecode). The files this skill produces only work in code-forge, because the format is specific to forge.
Where do I put the agent file?
Save it in <cwd>/.forge/agents, named {agent-id}.md. The source says this is the only location where forge discovers custom agents.
Why isn't my new agent showing up in code-forge?
The most likely cause is the location or name. Confirm the file is in <cwd>/.forge/agents of the project you are running and that the file name matches the id in its frontmatter.
Does this skill make the agent safer or add new tools?
No. The skill only changes how the agent writes agent files. It does not verify that a generated agent is safe, and it adds no new tools, so review the tools list and instructions yourself.
What is the alternative if I do not use code-forge?
This skill covers only code-forge agent files, so it is not useful for other tools. If you need general coding help unrelated to defining agents, use a skill or assistant built for that task.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you customize code-forge with your own agents or want a consistent agent format across a team. Skip it if you do not use code-forge, or if you want general coding help, since it only covers agent file structure and gives guidance without checking the result.
Download the skill