skill-creator

Create, evaluate, and iteratively improve Claude skills with benchmarked test runs.

Updated Jun 21, 2025
One-click install
npx skills add https://github.com/seriiserii825/dotfiles --skill skill-creator-seriiserii825
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/seriiserii825/dotfiles/tree/main/apps/claude/skills/synced/48e265c5-be08-4ca3-88ab-78707f398de7_1df978a8-b501-4d2b-b556-83317b565971/skill-creator
Command: npx skills add https://github.com/seriiserii825/dotfiles --skill skill-creator-seriiserii825

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Writing a skill that triggers reliably and performs well is hard to do by intuition alone. This Skill guides the full lifecycle of skill development: drafting SKILL.md files, running test prompts with and without the skill, grading outputs against assertions, benchmarking pass rates and token usage, and optimizing the description field for accurate triggering. ## 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 & Benchmarking: Spawns parallel with-skill and baseline runs, grades outputs against assertions, aggregates pass rate, timing, and token statistics, and renders results in an interactive HTML review viewer. - Description Optimization: Generates realistic trigger/no-trigger eval queries, runs an automated train/test optimization loop, and applies the best-performing description to improve skill triggering accuracy. - Use Case: A user says "turn this workflow into a skill." The Skill captures the intent, writes a draft, runs three test prompts against baselines, opens a browser viewer for feedback, iterates on the skill, and finally tunes the description so the skill triggers on the right prompts. ## Quick Start Ask Claude to create a new skill for your workflow and let it draft, test, and refine the skill through an evaluation loop.

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 defining what the skill should do, when it should trigger, and its expected output format. Then write a SKILL.md with name and description frontmatter, draft 2-3 realistic test prompts, run them with and without the skill, and iterate based on feedback.

How do I test whether a skill actually improves results?

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 pass rates, execution time, and token usage into a benchmark comparing the two configurations.

How do I improve a skill description for better triggering?

Generate about 20 realistic eval queries split between should-trigger and should-not-trigger cases, including tricky near-misses. Run the optimization loop, which tests description variants on a train split and selects the best by held-out test score.

What files can a skill contain besides SKILL.md?

A skill can include scripts/ for executable helper code, references/ for documentation loaded on demand, and assets/ for templates or files used in outputs. SKILL.md should reference these clearly so the model knows when to use each resource.

Why is my skill not triggering when it should?

Skills undertrigger when descriptions are too narrow or passive. Include both what the skill does and specific trigger contexts in the description, and note that simple one-step queries may never trigger because Claude handles them directly without consulting skills.

Can I use skill-creator on Claude.ai without subagents?

Yes, but with adaptations: run test cases sequentially yourself instead of spawning subagents, skip baseline runs and quantitative benchmarking, present results inline instead of the browser viewer, and skip description optimization since it requires the claude CLI.