skill-creator

Create, evaluate, and iteratively improve Claude skills with benchmarks and description optimization.

1|Updated Feb 1, 2025
One-click install
npx skills add https://github.com/TiagoDanin/TiagoDanin.github.io --skill skill-creator-tiagodanin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/TiagoDanin/TiagoDanin.github.io/tree/main/.claude/skills/skill-creator
Command: npx skills add https://github.com/TiagoDanin/TiagoDanin.github.io --skill skill-creator-tiagodanin

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Writing an effective skill is hard to get right on the first try: descriptions may fail to trigger, instructions may be ambiguous, and there is no built-in way to know whether a change actually improved performance. This Skill provides a structured draft-test-review-iterate workflow with quantitative benchmarking so skill quality is measured rather than guessed. ## Core Features & Use Cases - Guided Skill Authoring: Interviews the user about intent, trigger contexts, and output formats, then drafts a SKILL.md following progressive disclosure and writing-style best practices. - Evaluation Harness: Runs test prompts with and without the skill via parallel subagents, grades outputs against assertions, and aggregates pass rates, timing, and token usage into benchmark reports. - Review Viewer: Generates an HTML viewer for side-by-side qualitative review of outputs plus a quantitative benchmark tab, collecting user feedback per iteration. - Description Optimization: Generates realistic trigger/no-trigger eval queries and runs an automated loop that rewrites the skill description to maximize triggering accuracy on held-out test queries. - Use Case: You want a skill that formats weekly sales spreadsheets. This Skill helps you draft it, runs three realistic test prompts with and without the skill, shows you the results in a browser viewer, and iterates until the outputs pass your review. ## Quick Start Ask the assistant to help you create a new skill for your workflow, or to evaluate and improve an existing skill using test cases and benchmarks.

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 Claude skill from scratch?

Start by describing what the skill should do and when it should trigger. The skill creator interviews you about intent and output formats, drafts a SKILL.md with proper frontmatter, then runs test prompts so you can review and iterate on the results.

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. The workflow grades both outputs against assertions and aggregates pass rates, timing, and token usage into a benchmark report for comparison.

How can I improve my skill description so it triggers more reliably?

Generate 20 realistic trigger and no-trigger eval queries, review them in the HTML template, then run the optimization loop. It rewrites the description iteratively and selects the best version based on held-out test scores to avoid overfitting.

What makes a good SKILL.md file?

Keep the body under 500 lines, put all trigger conditions in the description field, and use progressive disclosure by moving detailed content into references files. Explain why instructions matter rather than relying on rigid MUST statements.

Does skill evaluation work on Claude.ai without subagents?

Yes, but with limitations. Without subagents you run test cases sequentially yourself, skip baseline comparisons and quantitative benchmarking, and present results inline in the conversation instead of using the browser-based review viewer.

When should I use blind comparison for skill evaluation?

Use blind comparison when you need a rigorous judgment between two skill versions, such as verifying a rewrite is actually better. An independent agent judges both outputs without knowing which skill produced them, then an analyzer explains why the winner won.