skill-creator

Create, evaluate, and iteratively improve Agent Skills with benchmarked test runs.

1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/rockcookies/skills --skill skill-creator-rockcookies
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/rockcookies/skills/tree/main/skills/anthropics/skill-creator
Command: npx skills add https://github.com/rockcookies/skills --skill skill-creator-rockcookies

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve? Writing an effective Agent Skill is hard to get right on the first try, and there is no built-in way to know whether a skill actually improves Claude's output or triggers when it should. This Skill provides a structured draft-test-review-improve loop with quantitative benchmarking so skill authors can iterate based on evidence instead of guesswork. ## Core Features & Use Cases - Guided Skill Authoring: Interviews the user to capture intent, then drafts a SKILL.md with proper frontmatter, progressive disclosure structure, and writing-style guidance. - Parallel Eval Runs with Baselines: Spawns with-skill and without-skill subagent runs for each test prompt, captures timing and token data, and grades outputs against assertions. - Benchmark Aggregation & Review Viewer: Aggregates grading results into benchmark.json/benchmark.md with pass-rate, time, and token deltas, and serves an HTML viewer for qualitative feedback. - Description Optimization Loop: Generates trigger/no-trigger eval queries, reviews them in an HTML template, and runs an automated optimization loop to improve skill triggering accuracy. - Use Case: You want to build a skill that formats weekly sales reports. This Skill helps you draft it, run three realistic test prompts with and without the skill, compare pass rates and outputs side by side, then refine the instructions until the results are consistently better. ## Quick Start Help me create a new skill that converts meeting transcripts into structured action-item lists, and set up test cases to verify it works.

Frequently Asked Questions about skill-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new Agent Skill from scratch?▼

Start by defining what the skill should do and when it should trigger, then write a SKILL.md with name and description frontmatter plus markdown instructions. This Skill walks you through intent capture, drafting, test case creation, and iterative evaluation.

How do I test whether my skill actually improves Claude's output?▼

Run each test prompt twice in parallel: once with the skill and once without as a baseline. Grade both outputs against objective assertions, then aggregate results into a benchmark comparing pass rates, time, and token usage.

How can I improve my skill description so it triggers correctly?▼

Generate 20 realistic eval queries split between should-trigger and should-not-trigger cases, then run the automated optimization loop. It evaluates description variants on train and held-out test queries and returns the best-performing description.

Does skill evaluation work on Claude.ai without subagents?▼

Yes, but with limitations. Without subagents you run test prompts sequentially yourself, skip baseline comparisons and quantitative benchmarking, and collect qualitative feedback inline instead of using the browser-based review viewer.

What makes a good skill test assertion?▼

Good assertions are objectively verifiable conditions with descriptive names, such as checking that an output file exists or contains specific data. Subjective qualities like writing style should be evaluated through human review rather than forced into assertions.

When should I use blind comparison for skill evaluation?▼

Use blind comparison when you need rigorous evidence that one skill version beats another, such as before shipping a major revision. An independent agent judges both outputs without knowing which skill produced them, then an analyzer explains why the winner won.