skill-creator
Create a SKILL.md, write test prompts, and compare agent runs with and without the skill.
npx skills add anthropics/skills --skill skill-creatorFour skills for people extending the agent rather than using it: building a skill, building a tool server for it, testing what you built, and getting straight answers about the API underneath. These are the ones that reward reading the source before you install, because they change how your agent behaves rather than just what it can open.
A skill only acts when its description matches what you asked for, so a vague description is the usual reason an installed skill never fires. skill-creator exists to close that loop: it writes test prompts and compares runs with and without the skill, instead of trusting the wording.
Create a SKILL.md, write test prompts, and compare agent runs with and without the skill.
npx skills add anthropics/skills --skill skill-creatorBuild an MCP server that gives an AI agent access to an external API or data source.
npx skills add anthropics/skills --skill mcp-builderTest a running web app with Playwright. Click, fill forms, verify results, and capture screenshots.
npx skills add anthropics/skills --skill webapp-testingBuild with the Claude API using examples for messages, tool calls, and streaming.
npx skills add anthropics/skills --skill claude-apiNo skill in this category has a full write-up yet.
The four skills on this page look similar and answer different questions. skill-creator is about writing reusable instructions well. mcp-builder is about giving an agent a tool it does not have. webapp-testing is about proving that something runs. claude-api is about the API those instructions and tools end up calling. Installing all four because they share a repository is how people end up with a skill that never fires.
A useful way to read the page: if the agent does not know how to do something, write instructions. If the agent cannot reach something, build a tool. If you cannot tell whether either worked, test it.
| Skill | Question it answers | Proof it worked |
|---|---|---|
| skill-creator | How should this instruction be written and described? | Two runs, with and without the skill, compared |
| mcp-builder | How does the agent reach this API or data source? | The tool is discovered and returns a real response |
| webapp-testing | Does the workflow actually run in a browser? | Steps, assertions and a captured screenshot |
| claude-api | How does this API call work in practice? | Working example with messages, tools and streaming |
Decide whether you need to write reusable instructions, connect an external tool or verify a running application. Each outcome needs a different test.
Use a fixture with known inputs and expected results. Check one success case plus an empty or invalid input before putting the workflow into regular use.
A skill supplies reusable instructions for an agent. An MCP server exposes tools or data the agent can call. A workflow can use both.