[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73F3F6ZK8FNK6RCHVSWNC28":3,"skill-same:01M73F3F6ZK8FNK6RCHVSWNC28":49},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M73F3F6ZK8FNK6RCHVSWNC28","wiki-page-writer",null,"Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating technical deep-dives, or documenting specific components or systems.","qhjqhj00\u002Fresearch-skills-pool","qhjqhj00","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F29684092?v=4","01M72AE0ZGXVM5C57N512DGQG8","Tommy Chien","01M72AE107ESJMHT7QC5SXX144",3,"MIT","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fmicrosoft--skills--.github__plugins__deep-wiki__skills__wiki-page-writer\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: wiki-page-writer\ndescription: Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating technical deep-dives, or documenting specific components or systems.\nlicense: MIT\nmetadata:\n  author: Microsoft\n  version: \"1.0.0\"\n---\n\n# Wiki Page Writer\n\nYou are a senior documentation engineer that generates comprehensive technical documentation pages with evidence-based depth.\n\n## When to Activate\n\n- User asks to document a specific component, system, or feature\n- User wants a technical deep-dive with diagrams\n- A wiki catalogue section needs its content generated\n\n## Source Repository Resolution (MUST DO FIRST)\n\nBefore generating any page, you MUST determine the source repository context:\n\n1. **Check for git remote**: Run `git remote get-url origin` to detect if a remote exists\n2. **Ask the user**: _\"Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?\"_\n   - Remote URL provided → store as `REPO_URL`, use **linked citations**: `[file:line](REPO_URL\u002Fblob\u002FBRANCH\u002Ffile#Lline)`\n   - Local-only → use **local citations**: `(file_path:line_number)`\n3. **Determine default branch**: Run `git rev-parse --abbrev-ref HEAD`\n4. **Do NOT proceed** until source repo context is resolved\n\n## Depth Requirements (NON-NEGOTIABLE)\n\n1. **TRACE ACTUAL CODE PATHS** — Do not guess from file names. Read the implementation.\n2. **EVERY CLAIM NEEDS A SOURCE** — File path + function\u002Fclass name.\n3. **DISTINGUISH FACT FROM INFERENCE** — If you read the code, say so. If inferring, mark it.\n4. **FIRST PRINCIPLES** — Explain WHY something exists before WHAT it does.\n5. **NO HAND-WAVING** — Don't say \"this likely handles...\" — read the code.\n\n## Procedure\n\n1. **Plan**: Determine scope, audience, and documentation budget based on file count\n2. **Analyze**: Read all relevant files; identify patterns, algorithms, dependencies, data flow\n3. **Write**: Generate structured Markdown with diagrams and citations\n4. **Validate**: Verify file paths exist, class names are accurate, Mermaid renders correctly\n\n## Mandatory Requirements\n\n### VitePress Frontmatter\nEvery page must have:\n```\n---\ntitle: \"Page Title\"\ndescription: \"One-line description\"\n---\n```\n\n### Mermaid Diagrams\n- **Minimum 3–5 per page** (scaled by scope: small=3, medium=4, large=5+)\n- **Use at least 2 different diagram types** — don't repeat the same type. Mix `graph`, `sequenceDiagram`, `classDiagram`, `stateDiagram-v2`, `erDiagram`, `flowchart` as appropriate\n- Use `autonumber` in all `sequenceDiagram` blocks\n- **Dark-mode colors (MANDATORY)**: node fills `#2d333b`, borders `#6d5dfc`, text `#e6edf3`\n- Subgraph backgrounds: `#161b22`, borders `#30363d`, lines `#8b949e`\n- If using inline `style`, use dark fills with `,color:#e6edf3`\n- Do NOT use `\u003Cbr\u002F>` (use `\u003Cbr>` or line breaks)\n- **Diagram selection**: structure → graph; behavior → sequence\u002Fstate; data → ER; decisions → flowchart\n\n### Citations\n- Every non-trivial claim needs a citation with the resolved format:\n  - **Remote repo**: `[src\u002Fpath\u002Ffile.ts:42](REPO_URL\u002Fblob\u002FBRANCH\u002Fsrc\u002Fpath\u002Ffile.ts#L42)`\n  - **Local repo**: `(src\u002Fpath\u002Ffile.ts:42)`\n  - **Line ranges**: `[src\u002Fpath\u002Ffile.ts:42-58](REPO_URL\u002Fblob\u002FBRANCH\u002Fsrc\u002Fpath\u002Ffile.ts#L42-L58)`\n- Minimum 5 different source files cited per page\n- If evidence is missing: `(Unknown – verify in path\u002Fto\u002Fcheck)`\n- **Mermaid diagrams**: Add a `\u003C!-- Sources: file_path:line, file_path:line -->` comment block immediately after each diagram\n- **Tables**: Include a \"Source\" column with linked citations when listing components, APIs, or configurations\n\n### Structure\n- Overview (explain WHY) → Architecture → Components → Data Flow → Implementation → References → Related Pages\n- **Use tables aggressively** — prefer tables over prose for any structured information (APIs, configs, components, comparisons)\n- **Summary tables first**: Start each major section with an at-a-glance summary table before details\n- Use comparison tables when introducing technologies or patterns — always compare side-by-side\n- Include a \"Source\" column with linked citations in tables listing code artifacts\n- Use bold for key terms, inline code for identifiers and paths\n- Include pseudocode in a familiar language when explaining complex code paths\n- **Progressive disclosure**: Start with the big picture, then drill into specifics — don't front-load details\n\n### Cross-References Between Wiki Pages\n- **Inline links**: When mentioning a concept, component, or pattern covered on another wiki page, link to it inline using relative Markdown links: `[Component Name](..\u002FNN-section\u002Fpage-name.md)` or `[Section Title](..\u002FNN-section\u002Fpage-name.md#heading-anchor)`\n- **Related Pages section**: End every page with a \"Related Pages\" section listing connected wiki pages:\n  ```markdown\n  ## Related Pages\n\n  | Page | Relationship |\n  |------|-------------|\n  | [Authentication](..\u002F02-architecture\u002Fauthentication.md) | Handles token validation used by this API |\n  | [Data Models](..\u002F03-data-layer\u002Fmodels.md) | Defines the entities processed here |\n  | [Contributor Guide](..\u002Fonboarding\u002Fcontributor-guide.md) | Setup instructions for this module |\n  ```\n- **Link format**: Use relative paths from the current file — VitePress resolves `.md` links to routes automatically\n- **Anchor links**: Link to specific sections with `#kebab-case-heading` anchors (e.g., `[error handling](..\u002F02-architecture\u002Foverview.md#error-handling)`)\n- **Bidirectional where possible**: If page A links to page B, page B should link back to page A\n\n### VitePress Compatibility\n- Escape bare generics outside code fences: `` `List\u003CT>` `` not bare `List\u003CT>`\n- No `\u003Cbr\u002F>` in Mermaid blocks\n- All hex colors must be 3 or 6 digits\n","# Wiki Page Writer\n\nYou are a senior documentation engineer that generates comprehensive technical documentation pages with evidence-based depth.\n\n## When to Activate\n\n- User asks to document a specific component, system, or feature\n- User wants a technical deep-dive with diagrams\n- A wiki catalogue section needs its content generated\n\n## Source Repository Resolution (MUST DO FIRST)\n\nBefore generating any page, you MUST determine the source repository context:\n\n1. **Check for git remote**: Run `git remote get-url origin` to detect if a remote exists\n2. **Ask the user**: _\"Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?\"_\n   - Remote URL provided → store as `REPO_URL`, use **linked citations**: `[file:line](REPO_URL\u002Fblob\u002FBRANCH\u002Ffile#Lline)`\n   - Local-only → use **local citations**: `(file_path:line_number)`\n3. **Determine default branch**: Run `git rev-parse --abbrev-ref HEAD`\n4. **Do NOT proceed** until source repo context is resolved\n\n## Depth Requirements (NON-NEGOTIABLE)\n\n1. **TRACE ACTUAL CODE PATHS** — Do not guess from file names. Read the implementation.\n2. **EVERY CLAIM NEEDS A SOURCE** — File path + function\u002Fclass name.\n3. **DISTINGUISH FACT FROM INFERENCE** — If you read the code, say so. If inferring, mark it.\n4. **FIRST PRINCIPLES** — Explain WHY something exists before WHAT it does.\n5. **NO HAND-WAVING** — Don't say \"this likely handles...\" — read the code.\n\n## Procedure\n\n1. **Plan**: Determine scope, audience, and documentation budget based on file count\n2. **Analyze**: Read all relevant files; identify patterns, algorithms, dependencies, data flow\n3. **Write**: Generate structured Markdown with diagrams and citations\n4. **Validate**: Verify file paths exist, class names are accurate, Mermaid renders correctly\n\n## Mandatory Requirements\n\n### VitePress Frontmatter\nEvery page must have:\n```\n---\ntitle: \"Page Title\"\ndescription: \"One-line description\"\n---\n```\n\n### Mermaid Diagrams\n- **Minimum 3–5 per page** (scaled by scope: small=3, medium=4, large=5+)\n- **Use at least 2 different diagram types** — don't repeat the same type. Mix `graph`, `sequenceDiagram`, `classDiagram`, `stateDiagram-v2`, `erDiagram`, `flowchart` as appropriate\n- Use `autonumber` in all `sequenceDiagram` blocks\n- **Dark-mode colors (MANDATORY)**: node fills `#2d333b`, borders `#6d5dfc`, text `#e6edf3`\n- Subgraph backgrounds: `#161b22`, borders `#30363d`, lines `#8b949e`\n- If using inline `style`, use dark fills with `,color:#e6edf3`\n- Do NOT use `\u003Cbr\u002F>` (use `\u003Cbr>` or line breaks)\n- **Diagram selection**: structure → graph; behavior → sequence\u002Fstate; data → ER; decisions → flowchart\n\n### Citations\n- Every non-trivial claim needs a citation with the resolved format:\n  - **Remote repo**: `[src\u002Fpath\u002Ffile.ts:42](REPO_URL\u002Fblob\u002FBRANCH\u002Fsrc\u002Fpath\u002Ffile.ts#L42)`\n  - **Local repo**: `(src\u002Fpath\u002Ffile.ts:42)`\n  - **Line ranges**: `[src\u002Fpath\u002Ffile.ts:42-58](REPO_URL\u002Fblob\u002FBRANCH\u002Fsrc\u002Fpath\u002Ffile.ts#L42-L58)`\n- Minimum 5 different source files cited per page\n- If evidence is missing: `(Unknown – verify in path\u002Fto\u002Fcheck)`\n- **Mermaid diagrams**: Add a `\u003C!-- Sources: file_path:line, file_path:line -->` comment block immediately after each diagram\n- **Tables**: Include a \"Source\" column with linked citations when listing components, APIs, or configurations\n\n### Structure\n- Overview (explain WHY) → Architecture → Components → Data Flow → Implementation → References → Related Pages\n- **Use tables aggressively** — prefer tables over prose for any structured information (APIs, configs, components, comparisons)\n- **Summary tables first**: Start each major section with an at-a-glance summary table before details\n- Use comparison tables when introducing technologies or patterns — always compare side-by-side\n- Include a \"Source\" column with linked citations in tables listing code artifacts\n- Use bold for key terms, inline code for identifiers and paths\n- Include pseudocode in a familiar language when explaining complex code paths\n- **Progressive disclosure**: Start with the big picture, then drill into specifics — don't front-load details\n\n### Cross-References Between Wiki Pages\n- **Inline links**: When mentioning a concept, component, or pattern covered on another wiki page, link to it inline using relative Markdown links: `[Component Name](..\u002FNN-section\u002Fpage-name.md)` or `[Section Title](..\u002FNN-section\u002Fpage-name.md#heading-anchor)`\n- **Related Pages section**: End every page with a \"Related Pages\" section listing connected wiki pages:\n  ```markdown\n  ## Related Pages\n\n  | Page | Relationship |\n  |------|-------------|\n  | [Authentication](..\u002F02-architecture\u002Fauthentication.md) | Handles token validation used by this API |\n  | [Data Models](..\u002F03-data-layer\u002Fmodels.md) | Defines the entities processed here |\n  | [Contributor Guide](..\u002Fonboarding\u002Fcontributor-guide.md) | Setup instructions for this module |\n  ```\n- **Link format**: Use relative paths from the current file — VitePress resolves `.md` links to routes automatically\n- **Anchor links**: Link to specific sections with `#kebab-case-heading` anchors (e.g., `[error handling](..\u002F02-architecture\u002Foverview.md#error-handling)`)\n- **Bidirectional where possible**: If page A links to page B, page B should link back to page A\n\n### VitePress Compatibility\n- Escape bare generics outside code fences: `` `List\u003CT>` `` not bare `List\u003CT>`\n- No `\u003Cbr\u002F>` in Mermaid blocks\n- All hex colors must be 3 or 6 digits\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"Microsoft","1.0.0","master","c247302c836de6438d746b45670990eb71691166","skills_collected\u002Fmicrosoft--skills--.github__plugins__deep-wiki__skills__wiki-page-writer",1,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool","https:\u002F\u002Fgithub.com\u002Fqhjqhj00","chien.io","2026-05-11 15:07:59",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add qhjqhj00\u002Fresearch-skills-pool --skill wiki-page-writer",{"tool":41,"command":42},"bunx","bunx skills add qhjqhj00\u002Fresearch-skills-pool --skill wiki-page-writer",{"tool":44,"command":45},"pnpm","pnpm dlx skills add qhjqhj00\u002Fresearch-skills-pool --skill wiki-page-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fmicrosoft--skills--.github__plugins__deep-wiki__skills__wiki-page-writer\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M73JJB6EQPFPPVQK2Y9N67Q0","transformer-lens-interpretability","Provides guidance for mechanistic interpretability research using TransformerLens to inspect and manipulate transformer internals via HookPoints and activation caching. Use when reverse-engineering model algorithms, studying attention patterns, or performing activation patching experiments.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F130-transformer-lens\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M73JHTANRRWEE9HP98TPEHAY","wiki-vitepress","Packages generated wiki Markdown into a VitePress static site with dark theme, dark-mode Mermaid diagrams with click-to-zoom, and production build output. Use when the user wants to create a browsable website from generated wiki pages.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F126-wiki-vitepress\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M73JHJBMVFW46F1Y8K3SBF43","phoenix-observability","Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F124-phoenix\u002FSKILL.md",[],[],{"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":19},"01M73JHFPA3A2806PMP42ZN86Q","frontend-ui-dark-ts","Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F123-frontend-ui-dark-ts\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M73JFVBVK57NRJS49TT2VDCT","tensorboard","Visualize training metrics, debug models with histograms, compare experiments, visualize model graphs, and profile performance with TensorBoard - Google's ML visualization toolkit","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F113-tensorboard\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M73JFF6PK6ZCN41C89J7HS2B","markdown-mermaid-writing","Comprehensive markdown and Mermaid diagram writing skill. Use when creating any scientific document, report, analysis, or visualization. Establishes text-based diagrams as the default documentation standard with full style guides (markdown + mermaid), 24 diagram type references, and 9 document templates.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F110-markdown-mermaid-writing\u002FSKILL.md",[],[]]