agentleFS
Sign inStart free
niksavisniksavis/basicly/.claude/skills/skill-creator/SKILL.md

skill-creator

Skill2 starsChanged 6 days agoMITView on GitHub

Writes a new skill or improves one with evals, a benchmark, graded versions and description tuning. Use when adding a new skill to the catalog, turning a workflow into a skill, comparing runs with and without a skill, or when a skill never gets picked up.

189 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use taskflow-inbox-triage, mermaid-diagram-generator and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AtomicBot-aiSkill

    taskflow-inbox-triage

    Also in 6 projects that use this

  • shalombSkill

    mermaid-diagram-generator

    Guide on creating and editing Mermaid charts safely. Use when asked to draw a diagram, flowchart, or architecture chart. Triggers on: 'mermaid', 'diagram', 'flowchart', 'visualize'.

    Also in 5 projects that use this

  • naman10parikhSkill

    ecosystem-reference

    Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.

    Also in 5 projects that use this

  • naman10parikhSkill

    fractal-delegation

    Also in 5 projects that use this

  • Liang-MHSkill

    stock_analysis

    获取 A 股、基金和港股的实时行情和技术分析数据

    Also in 5 projects that use this

  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • +6 more from naman10parikh

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 185 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a skill, test it on real prompts, measure it, and improve it until the user is satisfied.

    line 16
  2. Very specific:

    Write a draft as a skill.yaml source.

    line 22
  3. Very specific:

    Write the trigger cases and task cases in evals.yaml, then run a few task cases with and without the skill.

    line 23
  4. Distinctive:

    When does it trigger: which phrases and situations?

    line 39
  5. Very specific:

    Ask about edge cases, formats, example files, success criteria and dependencies before you write task cases.

    line 46
  6. Very specific:

    Before source authoring, read authoring.

    line 52
  7. Distinctive:

    Read grader, comparator, analyzer or schemas only for the step that names it.

    line 55

“Common” is measured: kept by at least 6 in 10 of the 185 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Generated by `basicly skills-build` from skill.yaml. Do not edit; edit the source. -->

Skill Creator

Modified by basicly on 2026-10-02 from anthropics/skills skill-creator at 8a1541c4 (Apache-2.0, see LICENSE.txt).

Create a skill, test it on real prompts, measure it, and improve it until the user is satisfied. This skill owns the eval loop.

The loop:

  1. Decide what the skill does and roughly how.
  2. Write a draft as a skill.yaml source.
  3. Write the trigger cases and task cases in evals.yaml, then run a few task cases with and without the skill.
  4. Evaluate the results with the user, both by reading them and by the numbers.
  5. Rewrite the skill from the feedback and from flaws that the benchmark shows.
  6. Repeat. Then add task cases and run again at a larger scale.

Find out where the user is in this loop and continue from there. A user with a draft goes straight to the eval step. A user who wants no formal evals gets a quick draft and a conversation. Description tuning comes last.

Capture the intent

The conversation may already hold the workflow, for example "turn this into a skill". Then take the answers from it first: the tools used, the order of steps, the corrections the user made, the input and output formats. Ask only for missing facts that change the result.

  1. What does the skill let the agent do?
  2. When does it trigger: which phrases and situations?
  3. What is the expected output?
  4. Does it need task cases? A skill with a verifiable output (a file transform, data extraction, generated code, fixed workflow steps) benefits from them. A skill with a subjective output (writing style, design) often does not. Suggest a default and let the user decide.

Ask about edge cases, formats, example files, success criteria and dependencies before you write task cases. Before you build, check that no installed or published skill already does the job: the find-skills skill does that search.

Read when needed

  • Before source authoring, read authoring; catalog-authoring owns catalog format and projections.
  • For trigger cases, test runs with and without the skill, grading and timing, read evaluation. The run with the skill and the run without it may go to parallel agents; you write the skill yourself.
  • For feedback, blind comparison, description tuning or evaluator script commands, read improvement. Execute the scripts; do not paste their source into the prompt.
  • Read grader, comparator, analyzer or schemas only for the step that names it.
  • Done when every task case passes with the skill, graded by an agent that did not write it, every trigger case passes in basicly catalog lint, and basicly skills-check passes.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free