claudeers.
// Claude Skills

skill-creator-plus

Free Claude skill that audits, builds and improves other skills against Anthropic's skill-writing rules, including what changed for Opus 5.5, Sonnet 5.5 and…

// Claude Skills[ api ][ claude ]#claude#agent-skills#anthropic#claude-code#claude-skills#skills◷ MIT$open-sourceupdated 1 day ago

Install with your AI

Paste into Claude Code, Cursor, or any agent — it reads the repo and wires the tool into your project.

Install and set up skill-creator-plus (claude-skill project) into my current project.
Found on https://claudeers.com/skill-creator-plus
Repo: https://github.com/robonuggets/skill-creator-plus
Homepage/docs: —
Detected install method: claude-skill → # copy this skill into .claude/skills/skill-creator-plus/
Category: skills. Platforms: api.
Read the repo's README for exact setup and env vars, then install it and wire it into my project.

Claudeers Health Verdict:
unknown; community-verified: false. Confirm the source before running anything.
// or install directly (claude-skill)
# copy the skill dir into your project:
# .claude/skills/skill-creator-plus/   (or ~/.claude/skills/skill-creator-plus/ for all projects)
// or clone
git clone https://github.com/robonuggets/skill-creator-plus

// compatibility

Platformsapi
Operating systems—
AI compatibilityclaude
LicenseMIT
Pricingopen-source
LanguagePython

Get your FREE $2.50 API credits to access TickAtlas financial data ↗

skill-creator-plus

skill-creator-plus

A free Claude skill that audits, builds and improves other skills against Anthropic's own skill-writing rules, including what changed for the newest Claude models.

Point it at a skill (or a whole folder of skills) and it gives you a findings report first: every rule marked pass, fail or not applicable, with the file and line as evidence and a proposed fix. It changes nothing until you say which fixes to apply.

Why this matters now

A skill is a folder with a SKILL.md file that teaches Claude how to do a job the same way each time. Anthropic publishes clear rules for writing them, and it is easy to break several without noticing: descriptions that never trigger, reference files Claude only half reads, rules buried where compaction cuts them.

The core rules on Anthropic's skill authoring page have been stable for about a year. What changed is the models:

  • The prompting guide for Claude Fable 5 says skills written for older models are often too prescriptive and can make output worse. Review them and remove what the model now does better on its own, but test before you delete.
  • The guides for Fable 5, Opus 5.5 and Sonnet 5.5 all list a reasoning_extraction refusal: asking Claude to write out its reasoning in the reply can be declined. A short explanation of the answer is fine.
  • The Fable 5 guide also says to give the reason, not only the request, to steer with brief instructions instead of long lists, and to make checking explicit, preferring a fresh Claude as the checker over self-review.

Claude Code adds its own: put the most important instructions at the top of SKILL.md (compaction keeps only the first 5,000 tokens), and move any rule that has to hold on every run into a hook.

This skill checks all of that, and the validator script checks the mechanical parts in a second.

Install

Claude Code. Put the folder in your skills folder and name it skill-creator-plus:

# for all your projects
git clone https://github.com/robonuggets/skill-creator-plus ~/.claude/skills/skill-creator-plus

# or for one project only, from the project folder
git clone https://github.com/robonuggets/skill-creator-plus .claude/skills/skill-creator-plus

On Windows, ~/.claude is the .claude folder inside your user folder. Downloading the ZIP from GitHub and copying the folder there works too.

claude.ai. Zip the folder (SKILL.md, references/, scripts/ and LICENSE; you can leave out examples/) and upload it under Skills in claude.ai settings. The frontmatter uses only the fields claude.ai accepts. The validator needs code execution turned on.

Use it

Just ask in plain words. Three modes:

ModeSay something likeYou get
AUDIT"Audit my deploy skill against Anthropic's rules." / "Check every skill in ~/.claude/skills and tell me what to fix first."A report: one row per rule, fails first, ranked fixes. Nothing is edited until you pick.
NEW"Make this a skill, we write release notes like this every Friday."Test prompts first, then a new skill folder that passes the validator.
REFINE"The report skill keeps forgetting the date filter. Fix the skill."The rule rewritten around its reason, usually shorter than before.

"Improve my skill for Opus 5.5" runs AUDIT, then REFINE with the fixes you approve.

See examples/pdf-helper-report.md for a full audit of a deliberately broken sample skill.

The validator

scripts/validate_skill.py checks the rules a script can check. Python 3.8 or newer, standard library only, works on Windows, Mac and Linux.

python3 scripts/validate_skill.py path/to/my-skill              # one skill
python3 scripts/validate_skill.py --all ~/.claude/skills         # every skill in a folder, one table
python3 scripts/validate_skill.py path/to/my-skill --json       # machine-readable
python3 scripts/validate_skill.py path/to/my-skill --ban-em-dash # also flag em dashes
python3 scripts/init_skill.py my-new-skill --path ~/.claude/skills --refs --scripts

Exit codes: 0 no errors (warnings and notes are fine), 1 errors found, 2 could not run. Each finding carries a rule ID from the table below.

Part of the real output for the sample skill in examples/pdf-helper/:

Skill: examples/pdf-helper (name: Claude_PDF_Helper)

ERROR  FM1    SKILL.md:4  'description' has an unquoted ': ' (or ends with ':'), which YAML reads as a new key, so the frontmatter will not parse. Wrap the value in double quotes.
ERROR  ST4    reference/advanced.md:3  reference/details.md is reached only through other reference files (reference/advanced.md:3), never from SKILL.md. Claude may only preview files it reaches that way (for example with head -100). Link it from SKILL.md, or fold its content into the file that needs it.
ERROR  ST5    reference/api.md  reference/api.md is 124 lines with no contents list in its first 50 lines. Add a '## Contents' list at the top so a partial read still shows everything the file covers.
WARN   DS2    SKILL.md:4  description is not in third person (found "I can"). It is injected into the system prompt; write "Processes Excel files", not "I can help" or "You can use this".
WARN   NM2    SKILL.md:20  asks Claude to write out its reasoning ("Think step by step and write"). Newer models (Claude Fable 5, Opus 5.5, Sonnet 5.5) may decline this with the reasoning_extraction refusal. Ask for the answer, or a short explanation of it, instead.
NOTE   HK1    SKILL.md:11,31  words like "must always" mark a rule that must hold every time, and the frontmatter has no hooks. Prose can be skipped or cut by compaction; if the rule truly must hold, enforce it with a hook (frontmatter hooks:).
...
Result: 8 errors, 11 warnings, 6 notes - fix the errors first.

The full output is in examples/pdf-helper-validator-output.txt. With --all you get one table:

Skill       Errors  Warnings  Notes  Rules with errors or warnings
----------  ------  --------  -----  -----------------------------
pdf-helper       8        11      6  FM1 FM2 ST4 ST5

The rules

46 rules. Script means the validator decides. Script + read means the validator flags candidates and Claude confirms in context. Read means Claude judges it during an audit and cites the evidence. "Advice" marks rules from practice rather than from Anthropic's docs.

IDRuleChecked bySource
FM1Frontmatter starts on line 1 and parses as YAMLScriptClaude Code: Frontmatter reference
FM2Name: lowercase, numbers, hyphens, max 64, no "anthropic" or "claude", matches the folderScriptBest practices: YAML frontmatter requirements
FM3Name says the activity (processing-pdfs), not vague (helper)Script + readBest practices: Naming conventions
FM4Only recognised fields; only six for claude.ai and the Skills APIScriptClaude Code: Frontmatter outside Claude Code
FM5Invocation set on purpose (manual-only, background, paths)ReadClaude Code: Control who invokes a skill
DS1Description present, at most 1,024 characters, no XML tagsScriptBest practices: YAML frontmatter requirements
DS2Description in third personScript + readBest practices: Writing effective descriptions
DS3Says what it does and when to use it, in the user's wordsScript + readBest practices: Writing effective descriptions
DS4Key use case first; description plus when_to_use under 1,536 charactersScript + readClaude Code: Descriptions are cut short
ST1SKILL.md body under 500 linesScriptBest practices: Progressive disclosure
ST2Most important instructions near the topScript + readClaude Code: Claude stops following a skill
ST3Split by area, details on demandReadBest practices: Progressive disclosure
ST4References one level deep from SKILL.mdScriptBest practices: Avoid deeply nested references
ST5Contents list on reference files over 100 linesScriptBest practices: Table of contents
ST6Every file reachable and well named; no dead links or backupsScript + readBest practices: Runtime environment
ST7Forward slashes in every pathScriptBest practices: Avoid Windows-style paths
CT1Concise: only what Claude does not already knowReadBest practices: Concise is key
CT2Degrees of freedom match the risk; mix levels; "what if Claude does this differently?"ReadBest practices: Degrees of freedom + advice
CT3Nothing time-sensitive; old ways under "Old patterns"Script + readBest practices: Time-sensitive information
CT4One term per conceptReadBest practices: Consistent terminology
CT5Templates say how strict they areReadBest practices: Template pattern
CT6Input and output examples where style mattersReadBest practices: Examples pattern
CT7A default plus one escape hatch, not a menuReadBest practices: Too many options
CT8MCP tools named in full, ServerName:tool_nameReadBest practices: MCP tool references
CT9No TODO, FIXME or unfilled placeholdersScriptAdvice
CT10One rule, one placeReadAdvice
WF1Checklist with "done when" lines and a go-back lineScript + readBest practices: Workflows for complex tasks
WF2Feedback loop: check, fix, repeat (a style guide counts as a check)ReadBest practices: Feedback loops
WF3Plan, validate, execute for batch or destructive jobsReadBest practices: Verifiable intermediate outputs
WF4Standing instructions, not one-time stepsReadClaude Code: Skill content lifecycle
SC1Scripts solve errors instead of deferring themReadBest practices: Solve, don't defer
SC2No unexplained ("voodoo") constantsReadBest practices: Solve, don't defer
SC3Says whether to run or read each scriptReadBest practices: Utility scripts
SC4Error messages name the problem and the fixReadBest practices: Verifiable intermediate outputs
SC5Packages listed with install lines; the Claude API cannot installScript + readBest practices: Package dependencies
NM1Not too prescriptive for newer models; test before deletingRead + testFable 5: Scaffolding changes
NM2No instruction to write out the model's reasoningScript + readFable 5: Scaffolding changes, Opus 5.5
NM3Rules carry their reasonReadFable 5: Give the reason
NM4Brief steering; capitals only for real hard linesScript + readFable 5: Instruction following + advice
NM5Verification explicit; fresh-context verifier preferredReadFable 5: Scaffolding changes
HK1A rule that has to hold on every run lives in a hookScript + readClaude Code: Stops following, Hooks in skills
TS1At least three evaluations, built first, with a baselineReadBest practices: Build evaluations first
TS2Fresh Claude tests on real work, skill on and offReadBest practices: Iterate with Claude, Claude Code: Evaluate
TS3Tested on the models it runs on; full sweep only where it mattersReadBest practices: Test with all models + advice
LB1No two skills claim the same triggersReadAdvice
LB2Unused skills found with /skill-doctor and turned offReadClaude Code: Find unused skills

Rules were checked against Anthropic's pages on 2026-10-05.

What is in the box

SKILL.md                      the skill: rules, the three modes, links to the rest
references/audit-checklist.md every rule with why, how to check, and the report format
references/authoring-guide.md how to write each part of a skill
references/testing.md         evaluations, baselines, model sweeps, test before you delete
scripts/validate_skill.py     the validator
scripts/init_skill.py         scaffolds a new skill that passes the validator
examples/                     a broken sample skill, its validator output and its audit report

Credits and license

The failure-mode names used in audits (no-op, duplication, sediment, sprawl, premature completion) come from Matt Pocock's "writing-great-skills". Not affiliated with Anthropic. MIT license, see LICENSE.

Made by RoboNuggets

// faq

What is skill-creator-plus?

Free Claude skill that audits, builds and improves other skills against Anthropic's skill-writing rules, including what changed for Opus 5.5, Sonnet 5.5 and Fable 5.. It is open-source on GitHub.

Is skill-creator-plus free to use?

skill-creator-plus is open-source under the MIT license, so it is free to use.

What category does skill-creator-plus belong to?

skill-creator-plus is listed under skills in the Claudeers registry of Claude-compatible tools.

4 views
★ 22 stars
unclaimed
updated 1 day ago

// embed badge

skill-creator-plus on Claudeers
[![Claudeers](https://claudeers.com/api/badge/skill-creator-plus.svg)](https://claudeers.com/skill-creator-plus)

// retro hit counter

skill-creator-plus hit counter
[![Hits](https://claudeers.com/api/counter/skill-creator-plus.svg)](https://claudeers.com/skill-creator-plus)

// reviews

// guestbook

0/500

// related in Claude Skills

🔓

An agentic skills framework & software development methodology that works.

// skillsobra/⟨Shell⟩★ 292,190◷ MIT[ claude ]
🔓

Public repository for Agent Skills

// skillsanthropics/⟨Python⟩★ 178,324[ claude ]
🔓

💫 Toolkit to help you get started with Spec-Driven Development

// skillsgithub/⟨Python⟩★ 138,919◷ MIT[ claude ]
🔓

AI coding assistant skill (Claude Code, Codex, OpenCode, Cursor, Gemini CLI, and more). Turn any folder of code, SQL schemas, R scripts, shell scripts, docs,…

// skillsGraphify-Labs/⟨Python⟩★ 123,800◷ MIT[ claude ]
→ see how skill-creator-plus connects across the ecosystem