skill-creator

Create, test, and iteratively improve SKILL.md skills through evaluation loops.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/RavitejaKarra24/dotfiles --skill skill-creator-ravitejakarra24
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/RavitejaKarra24/dotfiles/tree/main/agents/.agents/skills/skill-creator
Command: npx skills add https://github.com/RavitejaKarra24/dotfiles --skill skill-creator-ravitejakarra24

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Writing an effective AI skill is hard to get right on the first try: descriptions fail to trigger, instructions are ambiguous, and there is no systematic way to know if a skill actually improves results. This Skill provides a structured draft-test-review-iterate workflow for building and refining skills with quantitative benchmarks and human feedback. ## 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. - Evaluation Harness: Runs test prompts with and without the skill in parallel subagents, grades outputs against assertions, and aggregates pass rates, timing, and token usage into benchmark reports. - Interactive Review Viewer: Generates an HTML viewer (via eval-viewer/generate_review.py) so users can inspect outputs side-by-side and leave feedback that drives the next iteration. - Description Optimization: Generates trigger/no-trigger eval queries and runs an automated loop (scripts/run_loop.py) to improve the skill's description for reliable triggering. - Use Case: You want to build a skill that formats weekly sales reports. This Skill helps you draft it, creates realistic test prompts, runs baseline comparisons, shows you the results in a browser, and iterates until the outputs are consistently correct. ## Quick Start Ask the assistant to help you create a new skill for your workflow, and it will interview you, draft the SKILL.md, and run test evaluations. ## Quick Start Tell the assistant: help me create a new skill for my workflow, and it will interview you, draft the SKILL.md, and run test evaluations.

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 AI skill with SKILL.md?

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

How do I test whether my skill actually improves results?

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

How do I improve a skill description so it triggers reliably?

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

What is the difference between with-skill and baseline evaluation runs?

With-skill runs execute the test prompt with access to your skill, while baseline runs use no skill (for new skills) or the previous version (for improvements). Comparing them isolates the skill's actual contribution to output quality.

Does skill evaluation work without subagents, like on Claude.ai?

Yes, but with adaptations: run test cases sequentially yourself instead of in parallel subagents, skip baseline comparisons and quantitative benchmarking, and present outputs directly in the conversation for qualitative feedback.

When should a skill bundle scripts instead of inline instructions?

Bundle a script when test runs show agents repeatedly writing the same helper code across cases, or when a task is deterministic and repetitive. Scripts in the scripts/ directory execute without loading into context, saving effort on every invocation.