[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77MNST925MPH471PKCVWF5E":3,"skill-same:01M77MNST925MPH471PKCVWF5E":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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77MNST925MPH471PKCVWF5E","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.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhads\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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","58843b159d7a4050d6b785a98b908cce505c0b92",".agents\u002Fskills\u002Fhads",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill hads",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill hads",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill hads","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhads\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]