claude-skill-creator

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

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/lettucebo/Skills --skill claude-skill-creator-lettucebo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claude-skill-creator
Source: https://github.com/lettucebo/Skills/tree/main/skills/claude/skill-creator
Command: npx skills add https://github.com/lettucebo/Skills --skill claude-skill-creator-lettucebo

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 systematic way to know whether a change actually improved the skill. 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 writes a SKILL.md following progressive disclosure and writing-style best practices. - Evaluation & Benchmarking: Runs test prompts with and without the skill via parallel subagents, grades assertions, and aggregates pass rates, timing, and token usage into benchmark.json with variance analysis. - Description Optimization: Generates realistic trigger eval queries, reviews them in an HTML template, and runs an automated train/test optimization loop to improve skill triggering accuracy. - Use Case: You want to build a skill that converts meeting notes into Jira tickets. This Skill helps you draft it, creates test prompts, runs with-skill vs baseline comparisons, shows results in a browser-based review 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 claude-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 the SKILL.md with proper frontmatter, then creates test prompts to verify the skill works before iterating on feedback.

How do I test whether my skill actually improves results?▼

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

How can I improve my skill description for better triggering?▼

Generate 20 realistic trigger eval queries mixing should-trigger and should-not-trigger cases, review them in the HTML template, then run the optimization loop. It splits queries into train and test sets and iterates on the description up to 5 times, selecting by held-out test score.

What is the difference between with_skill and without_skill benchmark runs?▼

With_skill runs execute the test prompt with the skill loaded, while without_skill baselines run the same prompt with no skill. When improving an existing skill, the baseline can instead be a snapshot of the old skill version for direct comparison.

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

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

When should I not add quantitative assertions to a skill eval?▼

Skip assertions for skills with subjective outputs like writing style or design quality, where human judgment matters more than programmatic checks. Assertions work best for objectively verifiable outputs such as file transforms, data extraction, and fixed workflow steps.