Create and validate Minsky rules with consistent frontmatter and cross-references.
npx skills add https://github.com/edobry/minsky --skill create-rule-edobry
Please help me install this Agent Skill. Skill: create-rule Source: https://github.com/edobry/minsky/tree/main/.claude/skills/create-rule Command: npx skills add https://github.com/edobry/minsky --skill create-rule-edobry
This skill ensures Minsky rules have consistent structure, frontmatter, and cross-references, improving discoverability and quality.
Provide a new rule name and description, then have this skill structure it with proper frontmatter and formatting.
High-intent search queries and answers about installing and using this skill.
To write documentation rules with consistent frontmatter, use a skill that validates required metadata like name and description. It enforces a clear template with Title, Introduction, Core requirements, Examples, Rationale, and cross-references to related rules.
The standard structure for Minsky rules requires frontmatter with a name and description, followed by a template featuring Title, Introduction, Core requirements, Examples, Rationale, and See also sections to ensure quality and discoverability.
To validate rule quality and cross-references across projects, apply a rule-checking skill during drafting or reviews. It checks for consistent structure, required frontmatter, and links to related rules to ensure compliance.
Yes, you can update existing documentation rules without breaking the template format by using a validation skill. It enforces the standardized frontmatter and structural sections during updates, ensuring rule quality remains intact.
The best way to structure rule templates is using a standardized format with frontmatter for metadata and specific sections: Title, Introduction, Core requirements, Examples, and Rationale. This improves discoverability and cross-referencing.
Yes, you need specific frontmatter tags when drafting new rules. The required format includes a name and description, while tags are also enforced to ensure the rule is properly categorized and discoverable across projects.
pkuppensDefine explicit out-of-scope items for issues to prevent scope creep.
vndkubiValidate Copilot bootstrap configurations against a real project codebase.
alongor666Transform scattered project knowledge into structured knowledge assets with automated templates and indices.
newmoon-orgDefine and standardize coding rules for Augment Agent with frontmatter templates.
