[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0RK43PX2KB2CE8METMWR6":3,"skill-same:01M7F0RK43PX2KB2CE8METMWR6":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7F0RK43PX2KB2CE8METMWR6","hads",null,"Use when writing technical documentation that needs to be readable by both humans and AI models, converting existing docs to HADS format, validating a HADS document, or optimizing documentation for token-efficient AI consumption.","shotcowboystyle\u002Fag-skills","shotcowboystyle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62471?v=4","01M7EZTCFCZJ6K3MYW8BPM4X6R","Curtis Blanton","01M7EZTCG1S5M04J90A931X9BX",0,"MIT","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdocumentation-standards\u002Fskills\u002Fhads\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: hads\ndescription: Use when writing technical documentation that needs to be readable by both humans and AI models, converting existing docs to HADS format, validating a HADS document, or optimizing documentation for token-efficient AI consumption.\n---\n\n# HADS Claude Skill\n**Version 1.0.0** · Human-AI Document Standard · 2026 · HADS 1.0.0\n\n---\n\n## AI READING INSTRUCTION\n\nThis skill teaches Claude how to read, generate, and validate HADS documents.\nRead all `[SPEC]` blocks before responding to any HADS-related request.\nRead `[NOTE]` blocks if you need context on intent or edge cases.\n\n---\n\n## 1. WHAT IS HADS\n\n**[SPEC]**\n- HADS = Human-AI Document Standard\n- Convention for Markdown technical documentation\n- Four block types: `**[SPEC]**`, `**[NOTE]**`, `**[BUG]**`, `**[?]**`\n- Every HADS document requires: H1 title, version declaration, AI manifest\n- AI manifest appears before first content section, tells AI what to read\u002Fskip\n- File extension: `.md` — standard Markdown, no tooling required\n\n---\n\n## 2. BLOCK TYPES\n\n**[SPEC]**\n```\n**[SPEC]**   Authoritative fact. Terse. Bullet lists, tables, code. AI reads always.\n**[NOTE]**   Human context, history, examples. AI may skip.\n**[BUG]**    Verified failure + fix. Required fields: symptom, cause, fix. Always read.\n**[?]**      Unverified \u002F inferred. Lower confidence. Always flagged.\n```\n\nBlock tag rules:\n- Bold, on its own line: `**[SPEC]**`\n- Content follows immediately (no blank line between tag and content)\n- Multiple blocks of different types allowed per section\n- Titled BUG blocks allowed: `**[BUG] Short description**`\n- No nesting of blocks inside blocks\n\n---\n\n## 3. REQUIRED DOCUMENT STRUCTURE\n\n**[SPEC]**\n```markdown\n# Document Title\n**Version X.Y.Z** · Author · Date · [metadata]\n\n---\n\n## AI READING INSTRUCTION\n\nRead `[SPEC]` and `[BUG]` blocks for authoritative facts.\nRead `[NOTE]` only if additional context is needed.\n`[?]` blocks are unverified — treat with lower confidence.\n\n---\n\n## 1. First Section\n\n**[SPEC]**\n...\n```\n\nRequired elements in order:\n1. H1 title\n2. `**Version X.Y.Z**` in header (first 20 lines)\n3. AI manifest section before first content section\n4. Content sections (H2), subsections (H3)\n\n---\n\n## 4. HOW CLAUDE READS HADS\n\n**[SPEC]**\nWhen encountering a HADS document:\n1. Find and read the AI manifest first\n2. Read all `[SPEC]` blocks — these are ground truth\n3. Read all `[BUG]` blocks — always, before generating any code or config\n4. Read `[NOTE]` blocks only if `[SPEC]` is insufficient to answer the query\n5. Treat `[?]` content as hypothesis — note uncertainty in response\n\nToken optimization: for large documents, scan section headings first, then read only `[SPEC]` and `[BUG]` blocks in relevant sections.\n\n---\n\n## 5. HOW CLAUDE GENERATES HADS\n\n**[SPEC]**\nWhen asked to write documentation in HADS format:\n\n1. Start with header block (title, version, metadata)\n2. Add AI manifest — always include, never skip\n3. Organize content into numbered H2 sections\n4. For each fact: write as `[SPEC]` — terse, bullet or table or code\n5. For each \"why\" or context: write as `[NOTE]`\n6. For each known failure mode with confirmed fix: write as `[BUG]`\n7. For each unverified claim: write as `[?]`\n8. End with changelog section\n\nContent rules for `[SPEC]`:\n- Prefer bullet lists over prose\n- Prefer tables for multi-field facts\n- Prefer code blocks for syntax, formats, examples\n- Maximum 2 sentences of prose — if more needed, move to `[NOTE]`\n\nContent rules for `[BUG]`:\n- Always include: symptom, cause, fix\n- Optional: affected versions, workaround\n- Title on same line: `**[BUG] Short description**`\n\n**[NOTE]**\nWhen converting existing documentation to HADS: extract facts into `[SPEC]`, move narrative and history to `[NOTE]`, surface all known issues as `[BUG]`. Do not duplicate content between block types.\n\n---\n\n## 6. VALIDATION RULES\n\n**[SPEC]**\nA valid HADS document must have:\n- H1 title\n- `**Version X.Y.Z**` in first 20 lines\n- AI manifest before first content section\n- All block tags bold: `**[SPEC]**` not `[SPEC]` not *[SPEC]*\n- `[BUG]` blocks contain at minimum symptom + fix\n\nValidator: *(planned — not yet included in this release)*\n\n---\n\n## 7. EXAMPLE INTERACTIONS\n\n**[SPEC]**\n\nUser: *\"Write HADS documentation for this REST API\"*\n→ Generate full HADS document: header, manifest, sections with [SPEC]\u002F[NOTE]\u002F[BUG] blocks\n\nUser: *\"Convert this README to HADS format\"*\n→ Restructure existing content into HADS blocks, preserve all facts, add manifest\n\nUser: *\"Is this document valid HADS?\"*\n→ Check: H1 title, version, manifest, block tag formatting, BUG block completeness\n\nUser: *\"Summarize this HADS document\"*\n→ Read only [SPEC] and [BUG] blocks, return structured summary\n\nUser: *\"What does this API do?\"* (HADS doc provided)\n→ Read manifest, read [SPEC] blocks in relevant sections, answer directly\n\n---\n\n## 8. DESIGN INTENT\n\n**[NOTE]**\nHADS exists because AI models increasingly read documentation before humans do. The format optimizes for this reality without sacrificing human readability.\n\nKey insight: the AI manifest is the core innovation. It lets even small (7B) models know what to read and what to skip — without requiring them to reason about document structure. Explicit is better than implicit for model consumption.\n\nWhen generating HADS, think of `[SPEC]` as the API surface and `[NOTE]` as the comments. `[BUG]` blocks are the most valuable content — they represent hard-won knowledge that saves others from hitting the same wall.\n\n---\n\n## 9. QUICK REFERENCE\n\n**[SPEC]**\n```\nTag       | Bold format    | Reader  | Required content\n----------|----------------|---------|------------------\n[SPEC]    | **[SPEC]**     | AI      | Facts, terse\n[NOTE]    | **[NOTE]**     | Human   | Context, narrative\n[BUG]     | **[BUG] ...**  | Both    | Symptom + fix\n[?]       | **[?]**        | Both    | Unverified claims\n```\n\nManifest minimum:\n```markdown\n## AI READING INSTRUCTION\nRead `[SPEC]` and `[BUG]` blocks for authoritative facts.\nRead `[NOTE]` only if additional context is needed.\n`[?]` blocks are unverified.\n```\n","# HADS Claude Skill\n**Version 1.0.0** · Human-AI Document Standard · 2026 · HADS 1.0.0\n\n---\n\n## AI READING INSTRUCTION\n\nThis skill teaches Claude how to read, generate, and validate HADS documents.\nRead all `[SPEC]` blocks before responding to any HADS-related request.\nRead `[NOTE]` blocks if you need context on intent or edge cases.\n\n---\n\n## 1. WHAT IS HADS\n\n**[SPEC]**\n- HADS = Human-AI Document Standard\n- Convention for Markdown technical documentation\n- Four block types: `**[SPEC]**`, `**[NOTE]**`, `**[BUG]**`, `**[?]**`\n- Every HADS document requires: H1 title, version declaration, AI manifest\n- AI manifest appears before first content section, tells AI what to read\u002Fskip\n- File extension: `.md` — standard Markdown, no tooling required\n\n---\n\n## 2. BLOCK TYPES\n\n**[SPEC]**\n```\n**[SPEC]**   Authoritative fact. Terse. Bullet lists, tables, code. AI reads always.\n**[NOTE]**   Human context, history, examples. AI may skip.\n**[BUG]**    Verified failure + fix. Required fields: symptom, cause, fix. Always read.\n**[?]**      Unverified \u002F inferred. Lower confidence. Always flagged.\n```\n\nBlock tag rules:\n- Bold, on its own line: `**[SPEC]**`\n- Content follows immediately (no blank line between tag and content)\n- Multiple blocks of different types allowed per section\n- Titled BUG blocks allowed: `**[BUG] Short description**`\n- No nesting of blocks inside blocks\n\n---\n\n## 3. REQUIRED DOCUMENT STRUCTURE\n\n**[SPEC]**\n```markdown\n# Document Title\n**Version X.Y.Z** · Author · Date · [metadata]\n\n---\n\n## AI READING INSTRUCTION\n\nRead `[SPEC]` and `[BUG]` blocks for authoritative facts.\nRead `[NOTE]` only if additional context is needed.\n`[?]` blocks are unverified — treat with lower confidence.\n\n---\n\n## 1. First Section\n\n**[SPEC]**\n...\n```\n\nRequired elements in order:\n1. H1 title\n2. `**Version X.Y.Z**` in header (first 20 lines)\n3. AI manifest section before first content section\n4. Content sections (H2), subsections (H3)\n\n---\n\n## 4. HOW CLAUDE READS HADS\n\n**[SPEC]**\nWhen encountering a HADS document:\n1. Find and read the AI manifest first\n2. Read all `[SPEC]` blocks — these are ground truth\n3. Read all `[BUG]` blocks — always, before generating any code or config\n4. Read `[NOTE]` blocks only if `[SPEC]` is insufficient to answer the query\n5. Treat `[?]` content as hypothesis — note uncertainty in response\n\nToken optimization: for large documents, scan section headings first, then read only `[SPEC]` and `[BUG]` blocks in relevant sections.\n\n---\n\n## 5. HOW CLAUDE GENERATES HADS\n\n**[SPEC]**\nWhen asked to write documentation in HADS format:\n\n1. Start with header block (title, version, metadata)\n2. Add AI manifest — always include, never skip\n3. Organize content into numbered H2 sections\n4. For each fact: write as `[SPEC]` — terse, bullet or table or code\n5. For each \"why\" or context: write as `[NOTE]`\n6. For each known failure mode with confirmed fix: write as `[BUG]`\n7. For each unverified claim: write as `[?]`\n8. End with changelog section\n\nContent rules for `[SPEC]`:\n- Prefer bullet lists over prose\n- Prefer tables for multi-field facts\n- Prefer code blocks for syntax, formats, examples\n- Maximum 2 sentences of prose — if more needed, move to `[NOTE]`\n\nContent rules for `[BUG]`:\n- Always include: symptom, cause, fix\n- Optional: affected versions, workaround\n- Title on same line: `**[BUG] Short description**`\n\n**[NOTE]**\nWhen converting existing documentation to HADS: extract facts into `[SPEC]`, move narrative and history to `[NOTE]`, surface all known issues as `[BUG]`. Do not duplicate content between block types.\n\n---\n\n## 6. VALIDATION RULES\n\n**[SPEC]**\nA valid HADS document must have:\n- H1 title\n- `**Version X.Y.Z**` in first 20 lines\n- AI manifest before first content section\n- All block tags bold: `**[SPEC]**` not `[SPEC]` not *[SPEC]*\n- `[BUG]` blocks contain at minimum symptom + fix\n\nValidator: *(planned — not yet included in this release)*\n\n---\n\n## 7. EXAMPLE INTERACTIONS\n\n**[SPEC]**\n\nUser: *\"Write HADS documentation for this REST API\"*\n→ Generate full HADS document: header, manifest, sections with [SPEC]\u002F[NOTE]\u002F[BUG] blocks\n\nUser: *\"Convert this README to HADS format\"*\n→ Restructure existing content into HADS blocks, preserve all facts, add manifest\n\nUser: *\"Is this document valid HADS?\"*\n→ Check: H1 title, version, manifest, block tag formatting, BUG block completeness\n\nUser: *\"Summarize this HADS document\"*\n→ Read only [SPEC] and [BUG] blocks, return structured summary\n\nUser: *\"What does this API do?\"* (HADS doc provided)\n→ Read manifest, read [SPEC] blocks in relevant sections, answer directly\n\n---\n\n## 8. DESIGN INTENT\n\n**[NOTE]**\nHADS exists because AI models increasingly read documentation before humans do. The format optimizes for this reality without sacrificing human readability.\n\nKey insight: the AI manifest is the core innovation. It lets even small (7B) models know what to read and what to skip — without requiring them to reason about document structure. Explicit is better than implicit for model consumption.\n\nWhen generating HADS, think of `[SPEC]` as the API surface and `[NOTE]` as the comments. `[BUG]` blocks are the most valuable content — they represent hard-won knowledge that saves others from hitting the same wall.\n\n---\n\n## 9. QUICK REFERENCE\n\n**[SPEC]**\n```\nTag       | Bold format    | Reader  | Required content\n----------|----------------|---------|------------------\n[SPEC]    | **[SPEC]**     | AI      | Facts, terse\n[NOTE]    | **[NOTE]**     | Human   | Context, narrative\n[BUG]     | **[BUG] ...**  | Both    | Symptom + fix\n[?]       | **[?]**        | Both    | Unverified claims\n```\n\nManifest minimum:\n```markdown\n## AI READING INSTRUCTION\nRead `[SPEC]` and `[BUG]` blocks for authoritative facts.\nRead `[NOTE]` only if additional context is needed.\n`[?]` blocks are unverified.\n```\n",{"name":5,"description":7},"main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Fdocumentation-standards\u002Fskills\u002Fhads","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle","https:\u002F\u002Fshotcowboystyle.github.io","Building smarter with AI, automation & modern tools. Exploring how far one person can go without a big team using today’s AI.","2026-11-10 04:58:27",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add shotcowboystyle\u002Fag-skills --skill hads",{"tool":38,"command":39},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill hads",{"tool":41,"command":42},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill hads","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdocumentation-standards\u002Fskills\u002Fhads\u002FSKILL.md",true,[],[47,53,60,67,74,81],{"skillNo":48,"name":49,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7F1YRY5S5QRJ1V0BJS130QX","no-description","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-description\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7F1Y9BV2FJNQJ3NB32JS5CM","good-skill","Fixture skill that satisfies every rule.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fgood-skill\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7F1XXBQ3NQRXZSS0KAGAR9V","broken-link","Links to a reference file that does not exist.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbroken-link\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7F1XBX4R46NR9W0HXQ7XCDX","Bad_Name","Name violates the kebab-case rule and does not match the directory.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad-name\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7F1WNAF8WNEQ7S5HKT5VK0D","skill-authoring","Write, review, and validate portable agent skills in SKILL.md format. Use when creating a new skill, editing an existing one, or asked whether a skill follows the Agent Skills spec.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-authoring\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7F1W30TC0XFNSF7YBRGETK2","weigh-bags","Record scale readings for each bag — empty (tare), outbound, current, final — and reconcile them against the itemised inventory to find unaccounted weight. Use when the user gives a bag weight, says how heavy something is, weighs their luggage, or asks how close to the limit they are. Appends to bags.yaml and runs scripts\u002Freconcile.py.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Ftravel-packing-assistant\u002Fskills\u002Fweigh-bags\u002FSKILL.md",[],[]]