Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
When writing technical docs that must be readable by both humans and AI, converting existing docs to HADS, validating a HADS doc, or optimizing docs for token-efficient AI consumption.
[SPEC], [NOTE], [BUG], [?]) with bold tags and rules[SPEC]/[BUG] blocks, skip [NOTE] unless neededDocumentation in HADS format: explicitly marked for AI vs human reading, token-efficient, with facts separated from context and known failures captured as reusable knowledge.
Use Cases
A developer maintains a REST API and needs docs usable by both teammates and AI coding assistants. Using HADS, they write a doc with `[SPEC]` blocks for endpoints, `[NOTE]` for rationale, and `[BUG]` for known issues. The AI manifest lets the assistant read only facts, reducing tokens and errors. Value: faster, more accurate AI help and cleaner human docs.
A tech writer must convert a legacy README into a format optimized for LLM consumption. With HADS skill, they extract facts into `[SPEC]`, move history to `[NOTE]`, surface failures as `[BUG]`, and add a manifest. The result validates against HADS rules and is token-efficient for models. Value: preserved knowledge, easier AI onboarding.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
Skill File