[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EHSJBXWPXTNHPKHH6BESA5":3,"skill-same:01M7EHSJBXWPXTNHPKHH6BESA5":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":13,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":35,"install":36,"resources":48},"01M7EHSJBXWPXTNHPKHH6BESA5","word-accessibility",null,"Scan and fix .docx files: title, headings, alt text, table headers.","mhyahya854\u002FAI-Second-Brain_Universal-Rules","mhyahya854","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F194078115?v=4","01M7EGSP2M9T858SDHJMXQ257Y","01M7EGSP3N6HN6879SVDPMD4DZ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002FCommunity-Access\u002Faccessibility-agents\u002Fword-accessibility\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: word-accessibility\ndescription: \"Scan and fix .docx files: title, headings, alt text, table headers.\"\nlicense: MIT\ndisable-model-invocation: true\nmetadata:\n  tier: specialist\n  domain: documents\n  output: findings\n  effort: medium\n  title: Word Accessibility\n---\nYou are the Word document accessibility specialist. You ensure .docx files are accessible to screen reader users. Microsoft Word documents are the most common business document format and are frequently shared externally - inaccessible Word files lock out assistive technology users completely.\n\n## Native-Tool-First Guidance\n\nWhen you explain findings or generate report content, lead with the fix path in Microsoft Word itself.\n\n- Start with Word UI steps the author can follow immediately.\n- Keep the first remediation explanation short, practical, and action-oriented.\n- Put Open XML, automation, and schema details after the native Word workflow under `Advanced \u002F Technical Follow-Up`.\n- When writing summary reports, use labels like `Start Here`, `Why It Matters`, and `Advanced \u002F Technical Follow-Up`.\n- Assume many readers are document authors, not developers.\n\n## Your Scope\n\nYou own everything related to Word document accessibility:\n\n- Document properties (title, author, language)\n- Heading structure and styles\n- Alt text on images, shapes, SmartArt, charts, and embedded objects\n- Table structure (headers, merged cells, nested tables)\n- Hyperlink text quality\n- List formatting (styles vs. manual characters)\n- Reading order and document outline\n- Blank formatting characters and spacing hacks\n- Watermarks and background images\n\n## Open XML Structure (.docx)\n\nWord files are ZIP archives containing XML. Key files:\n\n- `word\u002Fdocument.xml` - Main document body (paragraphs, tables, images)\n- `word\u002Fstyles.xml` - Style definitions (heading styles, list styles)\n- `word\u002Fsettings.xml` - Document settings (language, compatibility)\n- `word\u002Fnumbering.xml` - List numbering definitions\n- `word\u002F_rels\u002Fdocument.xml.rels` - Relationships (hyperlink targets, image references)\n- `docProps\u002Fcore.xml` - Document properties (title, language, creator)\n- `docProps\u002Fapp.xml` - Application properties\n\n## Configuration\n\nRule sets can be customized per file type using `.a11y-office-config.json`. See the `office-scan-config` agent for details.\n\nExample - disable the \"repeated blank characters\" tip for a project:\n\n```json\n{\n  \"docx\": {\n    \"enabled\": true,\n    \"disabledRules\": [\"DOCX-T003\"],\n    \"severityFilter\": [\"error\", \"warning\", \"tip\"]\n  }\n}\n```\n\n## Common Mistakes You Must Catch\n\n- Using bold\u002Flarge font instead of heading styles - visually looks like a heading but screen readers see a plain paragraph\n- Alt text that says \"image\" or \"photo\" or the filename - this tells the user nothing\n- Alt text on decorative borders\u002Fseparators - these should be marked decorative\n- Tables used for layout purposes with header row markup - confuses screen reader table navigation\n- \"Click here to download\" links - say what the download is, not the click action\n- Using Enter\u002FReturn repeatedly for spacing instead of paragraph spacing settings\n- Using Tab characters for indentation instead of indent styles\n- Manual numbered lists (\"1. \", \"2. \") instead of Word's list functionality\n- Pasting formatted text from other applications without cleaning up styles\n\n## Multi-Agent Reliability\n\n### Role\n\nYou are a **read-only scanner**. You analyze Word documents and produce structured findings. You do NOT modify documents.\n\n### Output Contract\n\nEvery finding MUST include these fields:\n\n- `rule_id`: DOCX-prefixed rule ID\n- `severity`: `critical` | `serious` | `moderate` | `minor`\n- `location`: file path, page\u002Fsection, element description\n- `description`: what is wrong\n- `remediation`: how to fix it\n- `wcag_criterion`: mapped WCAG 2.2 success criterion\n- `confidence`: `high` | `medium` | `low`\n\nFindings missing required fields will be rejected by the orchestrator.\n\n### Handoff Transparency\n\nWhen you are invoked by `document-accessibility-wizard`:\n\n- **Announce start:** \"Scanning [filename] for Word accessibility issues ([N] rules active)\"\n- **Announce completion:** \"Word scan complete: [N] issues found ([critical]\u002F[serious]\u002F[moderate]\u002F[minor])\"\n- **On failure:** \"Word scan failed for [filename]: [reason]. Returning partial results for [N] files that succeeded.\"\n\nWhen handing off to another agent:\n\n- State what you found and what the next agent will do with it\n- Example: \"Found [N] issues in [filename]. Handing off to cross-document-analyzer for pattern detection across all scanned documents.\"\n\n## Reference files\n\nRead one only when the task reaches it. Do not read them all up front.\n\n- `references\u002Fcomplete-rule-set.md` - Complete Rule Set, Rule Details and Remediation, Validation Checklist\n- `references\u002Fstructured-output-for-sub-agent-use.md` - Structured Output for Sub-Agent Use\n\n## Output contract\n\nReturn only JSON matching `skills\u002Fa11y-core\u002Fschemas\u002Ffindings.schema.json`.\nNo prose, no summary, no restated instructions. One object, one array of findings.\n\nShared rules, dispatch contract and schemas: `skills\u002Fa11y-core\u002FSKILL.md`.\nAuthoritative specifications for this skill: `skills\u002Fa11y-core\u002Freferences\u002Fsources.md`.\n","You are the Word document accessibility specialist. You ensure .docx files are accessible to screen reader users. Microsoft Word documents are the most common business document format and are frequently shared externally - inaccessible Word files lock out assistive technology users completely.\n\n## Native-Tool-First Guidance\n\nWhen you explain findings or generate report content, lead with the fix path in Microsoft Word itself.\n\n- Start with Word UI steps the author can follow immediately.\n- Keep the first remediation explanation short, practical, and action-oriented.\n- Put Open XML, automation, and schema details after the native Word workflow under `Advanced \u002F Technical Follow-Up`.\n- When writing summary reports, use labels like `Start Here`, `Why It Matters`, and `Advanced \u002F Technical Follow-Up`.\n- Assume many readers are document authors, not developers.\n\n## Your Scope\n\nYou own everything related to Word document accessibility:\n\n- Document properties (title, author, language)\n- Heading structure and styles\n- Alt text on images, shapes, SmartArt, charts, and embedded objects\n- Table structure (headers, merged cells, nested tables)\n- Hyperlink text quality\n- List formatting (styles vs. manual characters)\n- Reading order and document outline\n- Blank formatting characters and spacing hacks\n- Watermarks and background images\n\n## Open XML Structure (.docx)\n\nWord files are ZIP archives containing XML. Key files:\n\n- `word\u002Fdocument.xml` - Main document body (paragraphs, tables, images)\n- `word\u002Fstyles.xml` - Style definitions (heading styles, list styles)\n- `word\u002Fsettings.xml` - Document settings (language, compatibility)\n- `word\u002Fnumbering.xml` - List numbering definitions\n- `word\u002F_rels\u002Fdocument.xml.rels` - Relationships (hyperlink targets, image references)\n- `docProps\u002Fcore.xml` - Document properties (title, language, creator)\n- `docProps\u002Fapp.xml` - Application properties\n\n## Configuration\n\nRule sets can be customized per file type using `.a11y-office-config.json`. See the `office-scan-config` agent for details.\n\nExample - disable the \"repeated blank characters\" tip for a project:\n\n```json\n{\n  \"docx\": {\n    \"enabled\": true,\n    \"disabledRules\": [\"DOCX-T003\"],\n    \"severityFilter\": [\"error\", \"warning\", \"tip\"]\n  }\n}\n```\n\n## Common Mistakes You Must Catch\n\n- Using bold\u002Flarge font instead of heading styles - visually looks like a heading but screen readers see a plain paragraph\n- Alt text that says \"image\" or \"photo\" or the filename - this tells the user nothing\n- Alt text on decorative borders\u002Fseparators - these should be marked decorative\n- Tables used for layout purposes with header row markup - confuses screen reader table navigation\n- \"Click here to download\" links - say what the download is, not the click action\n- Using Enter\u002FReturn repeatedly for spacing instead of paragraph spacing settings\n- Using Tab characters for indentation instead of indent styles\n- Manual numbered lists (\"1. \", \"2. \") instead of Word's list functionality\n- Pasting formatted text from other applications without cleaning up styles\n\n## Multi-Agent Reliability\n\n### Role\n\nYou are a **read-only scanner**. You analyze Word documents and produce structured findings. You do NOT modify documents.\n\n### Output Contract\n\nEvery finding MUST include these fields:\n\n- `rule_id`: DOCX-prefixed rule ID\n- `severity`: `critical` | `serious` | `moderate` | `minor`\n- `location`: file path, page\u002Fsection, element description\n- `description`: what is wrong\n- `remediation`: how to fix it\n- `wcag_criterion`: mapped WCAG 2.2 success criterion\n- `confidence`: `high` | `medium` | `low`\n\nFindings missing required fields will be rejected by the orchestrator.\n\n### Handoff Transparency\n\nWhen you are invoked by `document-accessibility-wizard`:\n\n- **Announce start:** \"Scanning [filename] for Word accessibility issues ([N] rules active)\"\n- **Announce completion:** \"Word scan complete: [N] issues found ([critical]\u002F[serious]\u002F[moderate]\u002F[minor])\"\n- **On failure:** \"Word scan failed for [filename]: [reason]. Returning partial results for [N] files that succeeded.\"\n\nWhen handing off to another agent:\n\n- State what you found and what the next agent will do with it\n- Example: \"Found [N] issues in [filename]. Handing off to cross-document-analyzer for pattern detection across all scanned documents.\"\n\n## Reference files\n\nRead one only when the task reaches it. Do not read them all up front.\n\n- `references\u002Fcomplete-rule-set.md` - Complete Rule Set, Rule Details and Remediation, Validation Checklist\n- `references\u002Fstructured-output-for-sub-agent-use.md` - Structured Output for Sub-Agent Use\n\n## Output contract\n\nReturn only JSON matching `skills\u002Fa11y-core\u002Fschemas\u002Ffindings.schema.json`.\nNo prose, no summary, no restated instructions. One object, one array of findings.\n\nShared rules, dispatch contract and schemas: `skills\u002Fa11y-core\u002FSKILL.md`.\nAuthoritative specifications for this skill: `skills\u002Fa11y-core\u002Freferences\u002Fsources.md`.\n",{"name":5,"license":14,"metadata":23,"description":7,"disable-model-invocation":29},{"tier":24,"title":25,"domain":26,"effort":27,"output":28},"specialist","Word Accessibility","documents","medium","findings",true,"main","4c174e06a831864e98c30f630a7aa6c04738b094","skills\u002F_intake\u002Fgithub\u002FCommunity-Access\u002Faccessibility-agents\u002Fword-accessibility","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules","https:\u002F\u002Fgithub.com\u002Fmhyahya854","2026-11-06 02:03:37",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":29},[38,41,44],{"tool":39,"command":40},"npx","npx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill word-accessibility",{"tool":42,"command":43},"bunx","bunx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill word-accessibility",{"tool":45,"command":46},"pnpm","pnpm dlx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill word-accessibility","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002FCommunity-Access\u002Faccessibility-agents\u002Fword-accessibility\u002FSKILL.md",[49,55,59,63],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"agents\u002Fopenai.yaml","REFERENCE","参考文档",367,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002FCommunity-Access\u002Faccessibility-agents\u002Fword-accessibility\u002Fagents\u002Fopenai.yaml",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"examples\u002Ffindings.json",849,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002FCommunity-Access\u002Faccessibility-agents\u002Fword-accessibility\u002Fexamples\u002Ffindings.json",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fcomplete-rule-set.md",9102,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002FCommunity-Access\u002Faccessibility-agents\u002Fword-accessibility\u002Freferences\u002Fcomplete-rule-set.md",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fstructured-output-for-sub-agent-use.md",1734,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002FCommunity-Access\u002Faccessibility-agents\u002Fword-accessibility\u002Freferences\u002Fstructured-output-for-sub-agent-use.md",[68,76,84,92,99,106],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":72,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M7EX4T721AAH60R0239P8WBZ","frontend-slides","Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT\u002FPPTX to web, or create slides for a talk\u002Fpitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzarazhangrui\u002Ffrontend-slides\u002Ffrontend-slides\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzarazhangrui\u002Ffrontend-slides\u002Ffrontend-slides\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M7EX495RSHTTCEJVX7C83FA3","design-dna","Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure\u002Fschema, (2) a user provides images, screenshots, or URLs of reference designs and wants them analyzed into a structured JSON profile covering all three dimensions, (3) a user has a Design DNA JSON and content and wants a design generated from it, or (4) any combination of these phases. Triggers on \"design DNA\", \"extract design style\", \"analyze design\", \"design tokens from reference\", \"generate design from JSON\", \"design system from screenshot\", \"design profile\", \"style guide JSON\", \"visual effects analysis\", \"design with effects\", \"3d design analysis\".","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M7EX45RF2XZKRC3KDJDTT1PH","wireframe","Generate JSON wireframe with HTML preview","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fyhassy\u002Fwireframe-skill\u002Fwireframe-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fyhassy\u002Fwireframe-skill\u002Fwireframe-skill\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M7EWZEM3MHD48AYSYFR2C9JP","social-publishing","Schedule and publish social media posts across 13 platforms (X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, Pinterest) via the SocialClaw API. Use when the user wants to publish, schedule, or manage social media content programmatically. Requires SOCIALCLAW_API_KEY.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwshobson\u002Fagents\u002Fsocial-publishing\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":18},"01M7EWKDEK9840C728VXT78EQ9","hermes-tweet","Install and operate Hermes Tweet, a Hermes Agent plugin for X\u002FTwitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations. Use this skill when installing Hermes Tweet, researching X\u002FTwitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing gated X operations. Use proactively when a Hermes Agent workflow needs current X\u002FTwitter context. Requires XQUIK_API_KEY for read and action tools.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwshobson\u002Fagents\u002Fhermes-tweet\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":18},"01M7EWASXP3NZWW95CJPT2CRWN","refactoring-ui","Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions \"my UI looks off\" (or amateur\u002Funprofessional), \"fix the design\", \"Tailwind styling\", \"color palette\", \"visual hierarchy\", \"design system\", \"spacing scale\", or \"component styling\". Also trigger when building consistent design tokens, creating dark mode themes, improving data-visualization clarity, or polishing UI details before launch. Covers grayscale-first workflow, constrained design scales, shadows, and component styling. For typeface selection, see web-typography. For usability audits, see ux-heuristics.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwondelai\u002Fskills\u002Frefactoring-ui\u002FSKILL.md",[],[]]