# Skill Creator

Create, improve, and evaluate agent skills (SKILL.md plus reference files).

- Repository: https://github.com/himself65/finance-skills (3487 stars)
- Category: Design
- License: MIT
- Last updated: 2026-10-25
- Runs scripts: no, instructions only

## Install

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

## Description

Create, improve, and evaluate agent skills (SKILL.md plus reference files). Use this skill whenever the user wants to build, scaffold, or design a new skill, improve or fix an existing skill that isn't working well, score or benchmark a skill's quality or run evals on it, or turn a repeated manual workflow into a skill ("I keep doing X manually", "can you remember how to do X", "turn this into a skill").

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

# Skill Creator

Create, evaluate, and iterate on high-quality agent skills. This skill covers the whole lifecycle: planning what the skill should do, writing SKILL.md and reference files, scoring quality against a rubric, and iterating until the skill meets production standards.

**Philosophy:** A great skill is precise, not long. Its description routes the right requests to it. Its body gives the model the context it can't get anywhere else, the environment, tool contracts, defaults, domain judgment, and the reasons behind each constraint, and leaves out what a capable model already does on its own. Current Claude models follow instructions closely and literally, so every line gets acted on: an over-scripted or shouting skill produces rigid, over-cautious output, while a clear goal and quality bar let the model plan the work itself. `references/writing-guide.md` covers this in detail.

**Runtime adaptation:** Skills that touch external tools should detect what is installed, authenticated, and reachable at runtime and adapt, rather than assuming a single method. Offer fallback paths where real alternatives exist. See `references/dynamic-calling.md` for the pattern catalog.

---

## Step 1: Understand What the User Wants

Classify the request into one of these modes:

| User Intent | Mode | Jump To |
|---|---|---|
| Create a brand-new skill | **Create** | Step 2 |
| Improve / fix an existing skill | **Improve** | Step 6 |
| Evaluate / score a skill's quality | **Evaluate** | Step 7 |

If ambiguous, ask: "Do you want to create a new skill, improve an existing one, or evaluate one?"

### Gather Requirements (for Create mode)

Before writing anything, answer these questions (ask the user if unclear):

The rest: https://github.com/himself65/finance-skills/blob/HEAD/plugins/skill-creator/skills/skill-creator/SKILL.md