skill-creator

Create or revise Feynman skills. Use when a research workflow needs a reusable on-demand capability, skill metadata, trigger wording, references, scripts, or skill validation.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an efficient, well-structured instruction skill with no padding and a clear workflow, held back only by a vague, command-less validation step.

Suggestions

Make step 5 executable by naming the concrete command(s) for skill-path tests and a pass/fail checkpoint, e.g., "Run `python skills/<name>/test_skill.py`; only commit when it passes."

Add an explicit feedback loop after validation (fix errors and re-run) so the verification is a checkpoint rather than a one-shot instruction.

Dimension	Reasoning	Score
Conciseness	The body is lean and operational with no padding and no explanation of concepts Claude already knows; every line earns its place, matching the top anchor.	5 / 5
Actionability	Steps give concrete, specific directives ("Use lowercase hyphenated names", "Put large references or scripts in adjacent files"), but the validation step says only "Run skill-path tests and command/resource discovery" without the actual command, leaving a minor executable gap.	4 / 5
Workflow Clarity	A clear five-step sequence is present with a validation/verification step at the end, but the verification ("Run skill-path tests and command/resource discovery after editing") is vague with no feedback loop or pass/fail checkpoint, keeping it just below a 5.	4 / 5
Progressive Disclosure	This is a sub-50-line simple skill with no need for external references and a well-organized numbered list, which per the simple-skills scoring note qualifies for the top anchor.	5 / 5
	Total	18 / 20 Passed

Description

80%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description cleanly answers both what and when with an explicit "Use when" clause and a scoped niche, but its trigger terms lean toward internal jargon over natural user phrasing.

Suggestions

Add natural-language trigger phrases a user would actually say (e.g., "Use when the user asks to make, fix, or improve a skill, or when a skill isn't triggering correctly").

Expand specificity from nouns to concrete verbs, e.g., "Create, update, or troubleshoot Feynman skills by editing frontmatter, authoring trigger wording, and validating skill paths."

Dimension	Reasoning	Score
Specificity	Names the domain ("Create or revise Feynman skills") and enumerates several concrete outputs (skill metadata, trigger wording, references, scripts, skill validation), but the actions are high-level rather than multiple distinct concrete verbs, so it sits just below a 5.	4 / 5
Completeness	It explicitly states both what ("Create or revise Feynman skills") and when ("Use when a research workflow needs a reusable on-demand capability, skill metadata, trigger wording, references, scripts, or skill validation") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	It surfaces relevant domain keywords ("skill metadata", "trigger wording", "references", "scripts", "skill validation"), but these are noun phrases a user would rarely utter verbatim and it lacks natural synonyms like "make a skill" or "skill isn't triggering", placing it at the "some relevant keywords, missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	The scope is tightly narrowed to "Feynman skills" with distinct, skill-authoring triggers, giving it a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: companion-inc/feynman
Path: skills/skill-creator/SKILL.md
Commit: 95c51d9

Reviewed: about 8 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.