skill-creator

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

Updated Jul 15, 2026
One-click install
npx skills add https://github.com/skyoxu/taptapmarker --skill skill-creator-skyoxu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/skyoxu/taptapmarker/tree/main/.cursor/skills/skill-creator
Command: npx skills add https://github.com/skyoxu/taptapmarker --skill skill-creator-skyoxu

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Writing an effective skill for an AI agent is hard to get right on the first try: descriptions undertrigger, instructions overfit to examples, and there is no systematic way to know whether a change actually helped. This Skill provides a complete authoring and evaluation workflow for creating new skills, improving existing ones, and measuring their performance with quantitative benchmarks and trigger-accuracy tests. ## Core Features & Use Cases - Guided skill authoring: Captures intent through interview questions, drafts SKILL.md files following progressive-disclosure and naming conventions, and detects the correct target directory (UrhoX repo vs. user workspace). - Eval-driven iteration loop: Spawns parallel with-skill and baseline subagent runs, drafts assertions, captures timing/token data, grades outputs, and aggregates results into benchmark.json with pass-rate deltas. - Review viewer and feedback loop: Launches a local HTML viewer (or static file in headless environments) showing outputs and benchmark tabs, collects user feedback into feedback.json, and drives the next iteration. - Description optimization: Generates realistic should-trigger/should-not-trigger eval queries, runs an automated train/test optimization loop, and reports the best-performing description. - Use Case: A user says "I want to make a skill that converts meeting notes into Jira tickets." The Skill interviews them, drafts the skill, creates test prompts, runs with-skill vs. baseline comparisons, shows results in a browser viewer, and iterates until the user is satisfied. ## Quick Start Help me create a new skill that converts my weekly meeting notes into structured Jira tickets, then 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 AI agent skill with SKILL.md?▼

Start by defining what the skill should do, when it should trigger, and its expected output format. Then write a SKILL.md with YAML frontmatter containing a name and description, followed by markdown instructions, and optionally add scripts, references, or assets directories.

How do I test whether my skill actually improves agent output?▼

Create 2-3 realistic test prompts, then run each prompt twice in parallel: once with the skill and once without (baseline). Grade the outputs against assertions, aggregate results into a benchmark comparing pass rates, time, and tokens, and review outputs in the HTML viewer.

How do I improve a skill description so it triggers correctly?▼

Generate about 20 realistic eval queries split between should-trigger and should-not-trigger cases, review them with the user, then run the automated optimization loop. It evaluates descriptions on a train set, proposes improvements, and selects the best by held-out test score.

What makes a good skill description for triggering?▼

A good description states both what the skill does and specific contexts for when to use it, including concrete trigger phrases. Slightly pushy phrasing helps because agents tend to undertrigger skills on tasks they think they can handle alone.

When should a skill include test cases and assertions?▼

Skills with objectively verifiable outputs like file transforms, data extraction, or code generation benefit from quantitative assertions. Skills with subjective outputs like writing style or design are better evaluated through qualitative human review instead.

Where should eval workspaces and iteration results be stored?▼

Eval workspaces should go under a gitignored .tmp directory, such as .tmp/skills/<name>-workspace/, organized by iteration folders. Placing them next to the skill directory would pollute the tracked skills tree.