[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AD59FD42M8AVRC1MV5DWGQ":3,"skill-same:01M6AD59FD42M8AVRC1MV5DWGQ":70},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":39,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M6AD59FD42M8AVRC1MV5DWGQ","documentation",null,"Write concise Diataxis docs for gh-aw with Starlight markdown conventions.","github\u002Fgh-aw","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3VCZ4WKQSFSRTPN7N9DN",5636,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fdocumentation\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28],"docs","markdown","gh","write","markdown conventions","conventions","diataxis","with","concise","for","2026-11-10 10:12:30",false,"---\nname: documentation\ndescription: Write concise Diataxis docs for gh-aw with Starlight markdown conventions.\n---\n\n### Documentation\n\nDocumentation lives in `docs\u002F`, uses GitHub-flavored Markdown, renders with Astro Starlight, and follows Diátaxis.\n\n## Diátaxis Framework\n\nOrganize documentation into four Diátaxis types:\n\n### 1. Tutorials (Learning-Oriented)\n**Purpose**: Guide beginners through achieving a specific outcome to build confidence.\n\n- Start with what the user will build or achieve\n- Provide a clear, step-by-step path from start to finish\n- Include concrete examples and working code\n- Assume minimal prior knowledge\n- Focus on the happy path (avoid edge cases and alternatives)\n- End with a working result the user can see and use\n- Use imperative mood: \"Create a file\", \"Run the command\"\n\n**Avoid**: Explaining concepts in depth, multiple options, troubleshooting\n\n### 2. How-to Guides (Goal-Oriented)\n**Purpose**: Show how to solve a specific real-world problem or accomplish a particular task.\n\n- Title format: \"How to [accomplish specific goal]\"\n- Assume the user knows the basics\n- Focus on practical steps to solve one problem\n- Include necessary context but stay focused\n- Show multiple approaches only when genuinely useful\n- End when the goal is achieved\n- Use imperative mood: \"Configure the setting\", \"Add the following\"\n\n**Avoid**: Teaching fundamentals, explaining every detail, being exhaustive\n\n### 3. Reference (Information-Oriented)\n**Purpose**: Provide accurate, complete technical descriptions of the system.\n\n- Organized by structure (CLI commands, configuration options, API endpoints)\n- Comprehensive and authoritative\n- Consistent format across all entries\n- Technical accuracy is paramount\n- Include all parameters, options, and return values\n- Use descriptive mood: \"The command accepts\", \"Returns a string\"\n- Minimal narrative or explanation\n\n**Avoid**: Instructions, tutorials, opinions on usage\n\n### 4. Explanation (Understanding-Oriented)\n**Purpose**: Clarify and illuminate topics to deepen understanding.\n\n- Discuss why things are the way they are\n- Explain design decisions and tradeoffs\n- Provide context and background\n- Connect concepts to help form mental models\n- Discuss alternatives and their implications\n- Use indicative mood: \"This approach provides\", \"The engine uses\"\n\n**Avoid**: Step-by-step instructions, exhaustive reference material\n\n## General Style Guidelines\n\n- **Tone**: Neutral, technical, not promotional\n- **Voice**: Avoid \"we\", \"our\", \"us\" (use \"the tool\", \"this command\")\n- **Headings**: Use markdown heading syntax, not bold text as headings\n- **Lists**: Avoid long bullet point lists; prefer prose with structure\n- **Code samples**: Minimal and focused; exclude optional fields unless relevant\n- **Language tag**: Use `aw` for agentic workflow snippets with YAML frontmatter\n\n**Example workflow code block**:\n```aw wrap\non: push\n# Your workflow steps here\n```\n\n## GitHub-Flavored Markdown Syntax\n\nDocumentation files use GitHub-flavored markdown with Astro Starlight for rendering. Key syntax elements:\n\n### Frontmatter\nEvery documentation page must have frontmatter:\n```markdown\ntitle: Page Title\ndescription: Brief description for SEO and navigation\n```\n\n### GitHub Alerts\nUse GitHub's alert syntax for notes, tips, warnings, and cautions:\n```markdown\n> [!NOTE]\n> Important information the reader should notice.\n\n> [!TIP]\n> Helpful advice for the reader.\n\n> [!WARNING]\n> Warning about potential issues or pitfalls.\n\n> [!CAUTION]\n> Critical warning about dangerous operations.\n\n> [!IMPORTANT]\n> Key information users need to know.\n```\n\n### Code Blocks\n- Use syntax highlighting with language tags\n- Add `title` attribute for file names: ` ```yaml title=\".github\u002Fworkflows\u002Fexample.yml\" `\n- Use `aw` language for agentic workflow files with YAML frontmatter\n- Add `wrap` for line wrapping: ` ```aw wrap `\n\n### Links\n- Internal links: Use relative paths between documentation pages\n- External links: Open in new tab automatically\n- Link text: Use descriptive text, avoid \"click here\"\n\n### Tabs\nUse tabs for showing alternatives (e.g., different languages, platforms):\n```markdown\nimport { Tabs, TabItem } from '@astrojs\u002Fstarlight\u002Fcomponents';\n\n\u003CTabs>\n  \u003CTabItem label=\"npm\">\n    ```bash\n    npm install package\n    ```\n  \u003C\u002FTabItem>\n  \u003CTabItem label=\"yarn\">\n    ```bash\n    yarn add package\n    ```\n  \u003C\u002FTabItem>\n\u003C\u002FTabs>\n```\n\n### Cards\nUse cards for navigation or highlighting multiple options:\n```markdown\nimport { Card, CardGrid } from '@astrojs\u002Fstarlight\u002Fcomponents';\n\n\u003CCardGrid>\n  \u003CCard title=\"Getting Started\" icon=\"rocket\">\n    Quick introduction to the basics.\n  \u003C\u002FCard>\n  \u003CCard title=\"Advanced Usage\" icon=\"setting\">\n    Deep dive into advanced features.\n  \u003C\u002FCard>\n\u003C\u002FCardGrid>\n```\n\n**Remember**: Keep components minimal. Prefer standard markdown when possible.\n\n## Content to Avoid\n\n- \"Key Features\" sections\n- Marketing language or selling points\n- Excessive bullet points (prefer structured prose)\n- Overly verbose examples with all optional parameters\n- Mixing documentation types (e.g., tutorials that become reference)\n\n## Avoiding Documentation Bloat\n\nDocumentation bloat reduces clarity and makes content harder to navigate. Common types of bloat include:\n\n### Types of Documentation Bloat\n\n1. **Duplicate content**: Same information repeated in different sections\n2. **Excessive bullet points**: Long lists that could be condensed into prose or tables\n3. **Redundant examples**: Multiple examples showing the same concept\n4. **Verbose descriptions**: Overly wordy explanations that could be more concise\n5. **Repetitive structure**: The same \"What it does\" \u002F \"Why it's valuable\" pattern overused\n\n### Writing Concise Documentation\n\nWhen editing documentation, focus on:\n\n**Consolidate bullet points**: \n- Convert long bullet lists into concise prose or tables\n- Remove redundant points that say the same thing differently\n\n**Eliminate duplicates**:\n- Remove repeated information\n- Consolidate similar sections\n\n**Condense verbose text**:\n- Make descriptions more direct and concise\n- Remove filler words and phrases\n- Keep technical accuracy while reducing word count\n\n**Standardize structure**:\n- Reduce repetitive \"What it does\" \u002F \"Why it's valuable\" patterns\n- Use varied, natural language\n\n**Simplify code samples**:\n- Remove unnecessary complexity from code examples\n- Focus on demonstrating the core concept clearly\n- Eliminate boilerplate or setup code unless essential for understanding\n- Keep examples minimal yet complete\n- Use realistic but simple scenarios\n\n### Example: Before and After\n\n**Before (Bloated)**:\n```markdown\n### Tool Name\nDescription of the tool.\n\n- **What it does**: This tool does X, Y, and Z\n- **Why it's valuable**: It's valuable because A, B, and C\n- **How to use**: You use it by doing steps 1, 2, 3, 4, 5\n- **When to use**: Use it when you need X\n- **Benefits**: Gets you benefit A, benefit B, benefit C\n- **Learn more**: [Link](url)\n```\n\n**After (Concise)**:\n```markdown\n### Tool Name\nDescription of the tool that does X, Y, and Z to achieve A, B, and C.\n\nUse it when you need X by following steps 1-5. [Learn more](url)\n```\n\n### Documentation Quality Guidelines\n\n1. **Preserve meaning**: Never lose important information\n2. **Be surgical**: Make precise edits, don't rewrite everything\n3. **Maintain tone**: Keep the neutral, technical tone\n4. **Test locally**: Verify links and formatting are still correct\n\n## Structure by File Type\n\n- **Getting Started**: Tutorial format\n- **How-to Guides**: Goal-oriented, one task per guide\n- **CLI Reference**: Reference format, complete command documentation\n- **Concepts**: Explanation format, building understanding\n- **API Reference**: Reference format, complete API documentation\n","### Documentation\n\nDocumentation lives in `docs\u002F`, uses GitHub-flavored Markdown, renders with Astro Starlight, and follows Diátaxis.\n\n## Diátaxis Framework\n\nOrganize documentation into four Diátaxis types:\n\n### 1. Tutorials (Learning-Oriented)\n**Purpose**: Guide beginners through achieving a specific outcome to build confidence.\n\n- Start with what the user will build or achieve\n- Provide a clear, step-by-step path from start to finish\n- Include concrete examples and working code\n- Assume minimal prior knowledge\n- Focus on the happy path (avoid edge cases and alternatives)\n- End with a working result the user can see and use\n- Use imperative mood: \"Create a file\", \"Run the command\"\n\n**Avoid**: Explaining concepts in depth, multiple options, troubleshooting\n\n### 2. How-to Guides (Goal-Oriented)\n**Purpose**: Show how to solve a specific real-world problem or accomplish a particular task.\n\n- Title format: \"How to [accomplish specific goal]\"\n- Assume the user knows the basics\n- Focus on practical steps to solve one problem\n- Include necessary context but stay focused\n- Show multiple approaches only when genuinely useful\n- End when the goal is achieved\n- Use imperative mood: \"Configure the setting\", \"Add the following\"\n\n**Avoid**: Teaching fundamentals, explaining every detail, being exhaustive\n\n### 3. Reference (Information-Oriented)\n**Purpose**: Provide accurate, complete technical descriptions of the system.\n\n- Organized by structure (CLI commands, configuration options, API endpoints)\n- Comprehensive and authoritative\n- Consistent format across all entries\n- Technical accuracy is paramount\n- Include all parameters, options, and return values\n- Use descriptive mood: \"The command accepts\", \"Returns a string\"\n- Minimal narrative or explanation\n\n**Avoid**: Instructions, tutorials, opinions on usage\n\n### 4. Explanation (Understanding-Oriented)\n**Purpose**: Clarify and illuminate topics to deepen understanding.\n\n- Discuss why things are the way they are\n- Explain design decisions and tradeoffs\n- Provide context and background\n- Connect concepts to help form mental models\n- Discuss alternatives and their implications\n- Use indicative mood: \"This approach provides\", \"The engine uses\"\n\n**Avoid**: Step-by-step instructions, exhaustive reference material\n\n## General Style Guidelines\n\n- **Tone**: Neutral, technical, not promotional\n- **Voice**: Avoid \"we\", \"our\", \"us\" (use \"the tool\", \"this command\")\n- **Headings**: Use markdown heading syntax, not bold text as headings\n- **Lists**: Avoid long bullet point lists; prefer prose with structure\n- **Code samples**: Minimal and focused; exclude optional fields unless relevant\n- **Language tag**: Use `aw` for agentic workflow snippets with YAML frontmatter\n\n**Example workflow code block**:\n```aw wrap\non: push\n# Your workflow steps here\n```\n\n## GitHub-Flavored Markdown Syntax\n\nDocumentation files use GitHub-flavored markdown with Astro Starlight for rendering. Key syntax elements:\n\n### Frontmatter\nEvery documentation page must have frontmatter:\n```markdown\ntitle: Page Title\ndescription: Brief description for SEO and navigation\n```\n\n### GitHub Alerts\nUse GitHub's alert syntax for notes, tips, warnings, and cautions:\n```markdown\n> [!NOTE]\n> Important information the reader should notice.\n\n> [!TIP]\n> Helpful advice for the reader.\n\n> [!WARNING]\n> Warning about potential issues or pitfalls.\n\n> [!CAUTION]\n> Critical warning about dangerous operations.\n\n> [!IMPORTANT]\n> Key information users need to know.\n```\n\n### Code Blocks\n- Use syntax highlighting with language tags\n- Add `title` attribute for file names: ` ```yaml title=\".github\u002Fworkflows\u002Fexample.yml\" `\n- Use `aw` language for agentic workflow files with YAML frontmatter\n- Add `wrap` for line wrapping: ` ```aw wrap `\n\n### Links\n- Internal links: Use relative paths between documentation pages\n- External links: Open in new tab automatically\n- Link text: Use descriptive text, avoid \"click here\"\n\n### Tabs\nUse tabs for showing alternatives (e.g., different languages, platforms):\n```markdown\nimport { Tabs, TabItem } from '@astrojs\u002Fstarlight\u002Fcomponents';\n\n\u003CTabs>\n  \u003CTabItem label=\"npm\">\n    ```bash\n    npm install package\n    ```\n  \u003C\u002FTabItem>\n  \u003CTabItem label=\"yarn\">\n    ```bash\n    yarn add package\n    ```\n  \u003C\u002FTabItem>\n\u003C\u002FTabs>\n```\n\n### Cards\nUse cards for navigation or highlighting multiple options:\n```markdown\nimport { Card, CardGrid } from '@astrojs\u002Fstarlight\u002Fcomponents';\n\n\u003CCardGrid>\n  \u003CCard title=\"Getting Started\" icon=\"rocket\">\n    Quick introduction to the basics.\n  \u003C\u002FCard>\n  \u003CCard title=\"Advanced Usage\" icon=\"setting\">\n    Deep dive into advanced features.\n  \u003C\u002FCard>\n\u003C\u002FCardGrid>\n```\n\n**Remember**: Keep components minimal. Prefer standard markdown when possible.\n\n## Content to Avoid\n\n- \"Key Features\" sections\n- Marketing language or selling points\n- Excessive bullet points (prefer structured prose)\n- Overly verbose examples with all optional parameters\n- Mixing documentation types (e.g., tutorials that become reference)\n\n## Avoiding Documentation Bloat\n\nDocumentation bloat reduces clarity and makes content harder to navigate. Common types of bloat include:\n\n### Types of Documentation Bloat\n\n1. **Duplicate content**: Same information repeated in different sections\n2. **Excessive bullet points**: Long lists that could be condensed into prose or tables\n3. **Redundant examples**: Multiple examples showing the same concept\n4. **Verbose descriptions**: Overly wordy explanations that could be more concise\n5. **Repetitive structure**: The same \"What it does\" \u002F \"Why it's valuable\" pattern overused\n\n### Writing Concise Documentation\n\nWhen editing documentation, focus on:\n\n**Consolidate bullet points**: \n- Convert long bullet lists into concise prose or tables\n- Remove redundant points that say the same thing differently\n\n**Eliminate duplicates**:\n- Remove repeated information\n- Consolidate similar sections\n\n**Condense verbose text**:\n- Make descriptions more direct and concise\n- Remove filler words and phrases\n- Keep technical accuracy while reducing word count\n\n**Standardize structure**:\n- Reduce repetitive \"What it does\" \u002F \"Why it's valuable\" patterns\n- Use varied, natural language\n\n**Simplify code samples**:\n- Remove unnecessary complexity from code examples\n- Focus on demonstrating the core concept clearly\n- Eliminate boilerplate or setup code unless essential for understanding\n- Keep examples minimal yet complete\n- Use realistic but simple scenarios\n\n### Example: Before and After\n\n**Before (Bloated)**:\n```markdown\n### Tool Name\nDescription of the tool.\n\n- **What it does**: This tool does X, Y, and Z\n- **Why it's valuable**: It's valuable because A, B, and C\n- **How to use**: You use it by doing steps 1, 2, 3, 4, 5\n- **When to use**: Use it when you need X\n- **Benefits**: Gets you benefit A, benefit B, benefit C\n- **Learn more**: [Link](url)\n```\n\n**After (Concise)**:\n```markdown\n### Tool Name\nDescription of the tool that does X, Y, and Z to achieve A, B, and C.\n\nUse it when you need X by following steps 1-5. [Learn more](url)\n```\n\n### Documentation Quality Guidelines\n\n1. **Preserve meaning**: Never lose important information\n2. **Be surgical**: Make precise edits, don't rewrite everything\n3. **Maintain tone**: Keep the neutral, technical tone\n4. **Test locally**: Verify links and formatting are still correct\n\n## Structure by File Type\n\n- **Getting Started**: Tutorial format\n- **How-to Guides**: Goal-oriented, one task per guide\n- **CLI Reference**: Reference format, complete command documentation\n- **Concepts**: Explanation format, building understanding\n- **API Reference**: Reference format, complete API documentation\n",{"name":5,"description":7},"main","8541229759617347888641eba917d3b0ad66a984",".github\u002Fskills\u002Fdocumentation",626,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw","https:\u002F\u002Fgh.io\u002Fgh-aw","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-15 06:45:15",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add github\u002Fgh-aw --skill documentation",{"tool":50,"command":51},"bunx","bunx skills add github\u002Fgh-aw --skill documentation",{"tool":53,"command":54},"pnpm","pnpm dlx skills add github\u002Fgh-aw --skill documentation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fdocumentation\u002FSKILL.md",true,[58,64],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fdecision-log-template.tsv","REFERENCE","参考文档",38,"https:\u002F\u002Fgithub.com\u002Faliyome\u002Fenv\u002Fblob\u002Fmaster\u002F.rulesync\u002Fskills\u002F.curated\u002Fshow-me-your-work\u002Freferences\u002Fdecision-log-template.tsv",{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"scripts\u002Flog.sh","SCRIPT","脚本",1377,"https:\u002F\u002Fgithub.com\u002Faliyome\u002Fenv\u002Fblob\u002Fmaster\u002F.rulesync\u002Fskills\u002F.curated\u002Fshow-me-your-work\u002Fscripts\u002Flog.sh",[71,79,87,113,131,156],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":78},"01M7DQYVZ9W9DDXKQ9452SNP8J","cracktro","Edit, preview, and verify the standalone interactive talk deck in docs\u002Fpublic\u002Fcracktro (slides, SVG diagrams, transitions, WebAudio sound).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcracktro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":86},"01M7612HQ4378TK8QZ5HPAF4KR","create-connector","Create or extend a declaration-only third-party connector, with narrow reads, separate safe outputs, optional protected triggers, and offline conformance evidence.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcreate-connector\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":101,"publishedAt":29},"01M6ADC942STTXHFV410J4DH0X","GitHub Agentic Workflows","GitHub Agentic Workflows (`gh-aw`) is a GitHub CLI extension for writing Agentic Workflows in markdown and compiling them to GitHub Actions.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002FSKILL.md",[93,98],{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":99,"categoryName":100,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000023","Skill与智能体开发",[9,102,103,104,105,106,20,107,108,21,28,109,110,111,112],"github agentic workflows","agentic workflows","workflows","agentic","extension","github cli","cli","compiling","writing","github actions","actions",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":29},"01M6ADC6ZXSA46N9XD6VNAP1MS","windows-compatibility","Cross-platform path handling and command patterns","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fwindows-compatibility\u002FSKILL.md",[],[120,121,122,123,124,125,126,127,128,129,130],"windows","windows compatibility","compatibility","command","git","bugs","platform","high","patterns","cross-platform","path",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":29},"01M6ADC44957SVQF96R5YY247P","versioning-policy","Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fversioning-policy\u002FSKILL.md",[],[138,139,140,141,142,108,143,144,145,146,147,148,149,150,28,151,152,153,154,155],"versioning","policy","versioning policy","gate","implementation","workspace","pr","sdk","release","ci","npm","semver","squad","incident","incidents","Rules","version","resolution",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":166,"publishedAt":29},"01M6ADC1PHMEAEVR87F8PDR89X","tiered-memory","Three-tier agent memory model (hot\u002Fcold\u002Fwiki) for context reduction per spawn","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Ftiered-memory\u002FSKILL.md",[162,165],{"categoryNo":163,"categoryName":164,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":99,"categoryName":100,"taxonomyType":96,"taxonomyTypeDesc":97},[167,168,169,170,171,172,173,174,175,176,177,178,179,28,180,181],"tiered memory","memory","performance","design","agent memory","proposal","cold","model","wiki","spawn","memory-management","context","three","runtime","management"]