Skill Creator

What it does

Skill Creator helps package a recurring workflow into instructions, supporting files and evaluations. It is useful when repeatedly correcting an agent on the same procedure. Beyond drafting SKILL.md, it compares outputs, gathers human feedback and revises the description that determines when the skill is selected. It does not turn an unclear process into a reliable one without representative examples.

When to use it

• Package a team’s release-note rules so fixes, breaking changes and empty releases are handled consistently.
• Improve an existing skill that activates too often or fails to activate for relevant requests.
• Compare a revised instruction set with the previous version using the same task inputs.

Step-by-step workflow

1. Define what the skill does, when it should activate, its inputs and the expected artifact. Capture exceptions from real work before drafting.
2. Create a concise SKILL.md with useful discovery metadata. Move long references or deterministic helper code into supporting files only when needed.
3. Choose representative prompts including ordinary tasks, edge cases and requests where the skill should not trigger.
4. Run evaluations in an appropriate environment and compare output quality with and without the skill. Keep cases comparable and record concrete success criteria.
5. Review results with human judgment, revise instructions and repeat. Refine triggering separately from task execution quality.

Example request

Use skill-creator to package our release-note process. Inputs are merged PR titles and labels; output is customer-facing Markdown grouped into fixes, improvements and breaking changes. Exclude internal maintenance. Include three representative releases, an empty release and two unrelated requests that must not trigger the skill. Compare the draft against the existing manual instructions and explain remaining failures.

Worked example

A release-note skill might follow the requested headings while leaking internal ticket names. Include a case that makes this mistake visible and grade the output for customer-readable wording. Also test an unrelated request: a good task result does not excuse a description that activates for every writing task.

What you get

A skill folder with instructions and evaluation material appropriate to the task.

How to evaluate the result

• Expect a skill folder, representative evaluation inputs and a record of observed results. Added scripts should solve concrete repetitive work rather than duplicate natural-language instructions.
• Check triggering accuracy and task quality independently. Use realistic inputs that were not all written to fit the draft perfectly.
• Review bundled scripts, data access and failure behavior before adoption. Evaluation success is not a security approval.

What you need

A clear recurring task, representative inputs and a way to evaluate the desired results.

Setup and activation

The publisher README documents Claude Code’s anthropic-agent-skills marketplace and its example-skills plugin. After reviewing the selected source and bundled files, enable the appropriate plugin in your client and mention the skill by name. Keep the complete skill folder so relative references still resolve. Plugin availability and commands depend on the client version; the publisher README is linked below. This page installs nothing. Before local installation, review and security-scan the exact source/version; catalogue inclusion is not security approval.

Limits and considerations

For a one-off task, a clear prompt may be enough. The evaluation workflow can require a compatible agent runtime and consumes model usage. Avoid promising reliability from a handful of examples or treating a generated skill as automatically safe.

Related workflows

• Use a specialist skill as a reference for the task domain.
• Use the resulting skill on held-out examples before making it part of a team workflow.

License and reuse

Apache License 2.0, confirmed in this skill’s LICENSE.txt. Reuse remains subject to the license’s notice and other requirements; inspect the exact version and any separately licensed assets.

Further reading

• Publisher setup and repository README
• Skill-specific license