Adding a Skill
85TrustedInstructions onlyRepository standards for authoring and distributing public assistant skill packages.
What it does
This skill acts as a technical guide for developers maintaining the BuilderIO/skills repository. It establishes the criteria for categorizing different types of agent capabilities, ensuring that new additions follow consistent structural and documentation patterns necessary for automated discovery.
When it earns its place
Reach for it when…
Use this when creating, modifying, or publishing new skills within the BuilderIO ecosystem. It provides the specific workflow for ensuring your local developments are correctly indexed, validated, and ready for CLI-based installation.
Look elsewhere when…
This is not intended for managing individual agent prompt files outside the BuilderIO repository structure. It does not provide general-purpose advice on writing system prompts or designing agent workflows unless they are being prepared for public contribution to this specific codebase.
What to say to use it
You never invoke a skill directly — the assistant picks it up when your request matches what it covers. These are the kinds of things that do that.
- how do I publish a new skill to the repo
- validate my new skill directory structure
- what are the requirements for a new public skill
- update the catalog documentation for my skill
Install it
Install for all your projects
Copy the skill directory into your personal skills folder. Claude picks it up on its own the next time your request matches what it does — there is nothing to enable.
git clone --depth 1 --branch main https://github.com/BuilderIO/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/.agents/skills/adding-a-skill ~/.claude/skills/adding-a-skillInstall for one project only
Put it in the project's own skills folder instead, so it can be committed and shared with everyone working on that repository.
cp -r /tmp/skills/.agents/skills/adding-a-skill .claude/skills/adding-a-skillIf a skill of the same name exists in both places, the personal one wins.
Installing on Claude.ai or through the API instead? The full guide covers every surface.
Pair it with an MCP server
Adding a Skill changes how the work is done. These servers change what Claude can reach while doing it.
- GitHub MCP Server53The skill sets the conventions the code should follow; GitHub MCP Server is what lets Claude read the repository it is writing into.
- Context Forge MCP Server86Context Forge MCP Server gives the code somewhere to actually run, so the skill's guidance can be checked instead of assumed.
- Supabase MCP Server100Pair with Supabase MCP Server when the code being written has to match a real schema rather than a described one.