. A skill used across multiple repositories belongs in the
skills/
directory of masseater/skills.
Validate it. Ensure that the frontmatter contains
name
and
description
, referenced files exist, and links to other skills resolve correctly.
Write test cases for structural content. Do not write them for subjective content.
Open a PR using the repository's process.
When in doubt, delete it. Keep only sentences that change a decision. State what to do, not why. Explain only rules that would be confusing without an explanation. Match the tone of the writing to its scope. Point to sources of structural information (types, README, configuration), and turn repeated instructions into lint, metadata, runtime checks, or scripts instead of adding more sentences. Delegate to other skills by path, and do not restate their content. If a procedure is performed repeatedly but has not been turned into a skill, propose a new skill.
Response: A summary of the skill, the main design decisions, and the validation results.