Classify each concern's severity on an absolute scale, not relative to what else was found - do not inflate a minor, unclear flaw into a major one just because the skill is otherwise clean. Do not invent issues that are not there.
A
has two clauses, in order:
Add a third clause only to disambiguate from an adjacent/similarly-named skill: "invoke from
", "standalone, or via
", "in place of
(which is for ...)". Backtick any referenced skill/command name.
Keep the whole thing to 1-3 sentences.
The
section in README.md states why the skill exists - not what it does or when to use it, both already covered by the frontmatter
. Flag it if missing, or if it restates function/trigger instead of rationale (e.g. history, relation to adjacent skills, design tradeoff).
For every concern found, suggest a solution. Write results to
inside the skill's directory.
in the skill's directory, listing each concern with its suggested fix.