# Skill Creator

Create a skill or bring an existing one up to the same standard (validate + asm eval...

- Repository: https://github.com/luongnv89/asm (962 stars)
- Category: Writing
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add luongnv89/asm --skill skill-creator -g -a claude-code -y`
Codex: `npx skills add luongnv89/asm --skill skill-creator -g -a codex -y`
Cursor: `npx skills add luongnv89/asm --skill skill-creator -g -a cursor -y`
Gemini CLI: `npx skills add luongnv89/asm --skill skill-creator -g -a gemini-cli -y`

## Description

Create a skill or bring an existing one up to the same standard (validate + asm eval fix loop); run evals, tune triggering. Use when authoring, fixing, or retrofitting a skill. Don't use for invoking skills, writing prose, or Python scaffolds.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Skill Creator

A skill for creating new skills and iteratively improving them. The agent's context budget is the primary constraint, so this SKILL.md links out to focused reference files.

The core loop:

1. Decide what the skill should do and how it should do it
2. Write a draft
3. Run test prompts against claude-with-access-to-the-skill
4. Evaluate results with the user (qualitative review via `eval-viewer/generate_review.py`, plus quantitative evals)
5. Revise the skill based on feedback and benchmarks
6. Repeat until satisfied; expand the test set and try again at scale

Identify where the user is in this loop and jump in there. New skill from scratch → start at step 1. Existing draft → jump to step 3 or 4. User wants to vibe-iterate without formal evals → support that.

## Two entry paths

The skill supports two distinct workflows. **Identify which one the user is on before you do anything else**, they don't share a starting step.

- **Path A, Create a new skill from scratch.** The user wants to capture a workflow, codify a pattern, or build a new capability. Start at **"Creating a skill"** below (Capture Intent → Interview → Write SKILL.md → Test → Eval).
- **Path B, Improve an existing skill.** The user points to a skill that already exists and wants it brought up to standard, fixed, optimized, or iterated based on eval feedback. **Do not start with Capture Intent**, the intent is already encoded in the existing SKILL.md. Start at **"Improving an existing skill"** below.

If the request is ambiguous ("can you look at this skill?"), assume **Path B** and confirm before interviewing as if it were new. Path B also fires when `/skill-creator` is invoked on a skill directory or file.

Both paths share the mandatory rules below: **Repo Sync Before Edits**, **Dependency Preflight**, **Self-Improve**, **Version Management**, **YAML Frontmatter Safety**, and **Frontmatter Audit on Review/Evaluation**. Both close with the **Run stats** block.

The rest: https://github.com/luongnv89/asm/blob/HEAD/skills/skill-creator/SKILL.md