[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73F3A5KF2TQMSW249C0NMSZ":3,"skill-same:01M73F3A5KF2TQMSW249C0NMSZ":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},"01M73F3A5KF2TQMSW249C0NMSZ","wiki-llms-txt",null,"Generates llms.txt and llms-full.txt files for LLM-friendly project documentation following the llms.txt specification. Use when the user wants to create LLM-readable summaries, llms.txt files, or make their wiki accessible to language models.","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-llms-txt\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: wiki-llms-txt\ndescription: Generates llms.txt and llms-full.txt files for LLM-friendly project documentation following the llms.txt specification. Use when the user wants to create LLM-readable summaries, llms.txt files, or make their wiki accessible to language models.\nlicense: MIT\nmetadata:\n  author: Microsoft\n  version: \"1.0.0\"\n---\n\n# llms.txt Generator\n\nGenerate `llms.txt` and `llms-full.txt` files that provide LLM-friendly access to wiki documentation, following the [llms.txt specification](https:\u002F\u002Fllmstxt.org\u002F).\n\n## When This Skill Activates\n\n- User asks to generate `llms.txt` or mentions the llms.txt standard\n- User wants to make documentation \"LLM-friendly\" or \"LLM-readable\"\n- User asks for a project summary file for language models\n- User mentions `llms-full.txt` or context-expanded documentation\n\n## Source Repository Resolution (MUST DO FIRST)\n\nBefore generating, resolve the source repository context:\n\n1. **Check for git remote**: Run `git remote get-url origin`\n2. **Ask the user**: _\"Is this a local-only repository, or do you have a source repository URL?\"_\n   - Remote URL → store as `REPO_URL`\n   - Local → use relative paths only\n3. **Determine default branch**: Run `git rev-parse --abbrev-ref HEAD`\n4. **Do NOT proceed** until resolved\n\n## llms.txt Format (Spec-Compliant)\n\nThe file follows the [llms.txt specification](https:\u002F\u002Fllmstxt.org\u002F):\n\n```markdown\n# {Project Name}\n\n> {Dense one-paragraph summary — what it does, who it's for, key technologies}\n\n{Important context paragraphs — constraints, architectural philosophy, non-obvious things}\n\n## {Section Name}\n\n- [{Page Title}]({relative-path-to-md}): {One-sentence description of what the reader will learn}\n\n## Optional\n\n- [{Page Title}]({relative-path-to-md}): {Description — these can be skipped for shorter context}\n```\n\n### Key Rules\n\n1. **H1** — Project name (exactly one, required)\n2. **Blockquote** — Dense, specific summary (required). Must be unique to THIS project.\n3. **Context paragraphs** — Non-obvious constraints, things LLMs would get wrong without being told\n4. **H2 sections** — Organized by topic, each with a list of `[Title](url): Description` entries\n5. **\"Optional\" H2** — Special meaning: links here can be skipped for shorter context\n6. **Relative links** — All paths relative to wiki directory\n7. **Dynamic** — ALL content derived from actual wiki pages, not templates\n8. **Section order** — Most important first: Onboarding → Architecture → Getting Started → Deep Dive → Optional\n\n### Description Quality\n\n| ❌ Bad | ✅ Good |\n|--------|---------|\n| \"Architecture overview\" | \"System architecture showing how Orleans grains communicate via message passing with at-least-once delivery\" |\n| \"Getting started guide\" | \"Prerequisites, local dev setup with Docker Compose, and first API call walkthrough\" |\n| \"The API reference\" | \"REST endpoints with auth requirements, rate limits, and request\u002Fresponse schemas\" |\n\n## llms-full.txt Format\n\nSame structure as `llms.txt` but with full content inlined:\n\n```markdown\n# {Project Name}\n\n> {Same summary}\n\n{Same context}\n\n## {Section Name}\n\n\u003Cdoc title=\"{Page Title}\" path=\"{relative-path}\">\n{Full markdown content — frontmatter stripped, citations and diagrams preserved}\n\u003C\u002Fdoc>\n```\n\n### Inlining Rules\n\n- **Strip YAML frontmatter** (`---` blocks) from each page\n- **Preserve Mermaid diagrams** — keep `` ```mermaid `` fences intact\n- **Preserve citations** — all `[file:line](URL)` links stay as-is\n- **Preserve tables** — all markdown tables stay intact\n- **Preserve `\u003C!-- Sources: -->` comments** — these provide diagram provenance\n\n## Prerequisites\n\nThis skill works best when wiki pages already exist (via `\u002Fdeep-wiki:generate` or `\u002Fdeep-wiki:page`). If no wiki exists yet:\n\n1. Suggest running `\u002Fdeep-wiki:generate` first\n2. OR generate a minimal `llms.txt` from README + source code scan (without wiki page links)\n\n## Output Files\n\nGenerate three files:\n\n| File | Purpose | Discoverability |\n|------|---------|-----------------|\n| `.\u002Fllms.txt` | Root discovery file | Standard path per llms.txt spec. GitHub MCP `get_file_contents` and `search_code` find this first. |\n| `wiki\u002Fllms.txt` | Wiki-relative links | For VitePress deployment and wiki-internal navigation. |\n| `wiki\u002Fllms-full.txt` | Full inlined content | Comprehensive reference for agents needing all docs in one file. |\n\nThe root `.\u002Fllms.txt` links into `wiki\u002F` (e.g., `[Guide](.\u002Fwiki\u002Fonboarding\u002Fcontributor-guide.md)`). The `wiki\u002Fllms.txt` uses wiki-relative paths (e.g., `[Guide](.\u002Fonboarding\u002Fcontributor-guide.md)`).\n\nIf a root `llms.txt` already exists and was NOT generated by deep-wiki, do NOT overwrite it.\n\n## Validation Checklist\n\nBefore finalizing:\n\n- [ ] All linked files in `llms.txt` actually exist\n- [ ] All `\u003Cdoc>` blocks in `llms-full.txt` have real content (not empty)\n- [ ] Blockquote is specific to this project (not generic boilerplate)\n- [ ] Sections ordered by importance\n- [ ] No duplicate page entries across sections\n- [ ] \"Optional\" section only contains truly optional content\n- [ ] `llms.txt` is concise (1-5 KB)\n- [ ] `llms-full.txt` contains all wiki pages\n","# llms.txt Generator\n\nGenerate `llms.txt` and `llms-full.txt` files that provide LLM-friendly access to wiki documentation, following the [llms.txt specification](https:\u002F\u002Fllmstxt.org\u002F).\n\n## When This Skill Activates\n\n- User asks to generate `llms.txt` or mentions the llms.txt standard\n- User wants to make documentation \"LLM-friendly\" or \"LLM-readable\"\n- User asks for a project summary file for language models\n- User mentions `llms-full.txt` or context-expanded documentation\n\n## Source Repository Resolution (MUST DO FIRST)\n\nBefore generating, resolve the source repository context:\n\n1. **Check for git remote**: Run `git remote get-url origin`\n2. **Ask the user**: _\"Is this a local-only repository, or do you have a source repository URL?\"_\n   - Remote URL → store as `REPO_URL`\n   - Local → use relative paths only\n3. **Determine default branch**: Run `git rev-parse --abbrev-ref HEAD`\n4. **Do NOT proceed** until resolved\n\n## llms.txt Format (Spec-Compliant)\n\nThe file follows the [llms.txt specification](https:\u002F\u002Fllmstxt.org\u002F):\n\n```markdown\n# {Project Name}\n\n> {Dense one-paragraph summary — what it does, who it's for, key technologies}\n\n{Important context paragraphs — constraints, architectural philosophy, non-obvious things}\n\n## {Section Name}\n\n- [{Page Title}]({relative-path-to-md}): {One-sentence description of what the reader will learn}\n\n## Optional\n\n- [{Page Title}]({relative-path-to-md}): {Description — these can be skipped for shorter context}\n```\n\n### Key Rules\n\n1. **H1** — Project name (exactly one, required)\n2. **Blockquote** — Dense, specific summary (required). Must be unique to THIS project.\n3. **Context paragraphs** — Non-obvious constraints, things LLMs would get wrong without being told\n4. **H2 sections** — Organized by topic, each with a list of `[Title](url): Description` entries\n5. **\"Optional\" H2** — Special meaning: links here can be skipped for shorter context\n6. **Relative links** — All paths relative to wiki directory\n7. **Dynamic** — ALL content derived from actual wiki pages, not templates\n8. **Section order** — Most important first: Onboarding → Architecture → Getting Started → Deep Dive → Optional\n\n### Description Quality\n\n| ❌ Bad | ✅ Good |\n|--------|---------|\n| \"Architecture overview\" | \"System architecture showing how Orleans grains communicate via message passing with at-least-once delivery\" |\n| \"Getting started guide\" | \"Prerequisites, local dev setup with Docker Compose, and first API call walkthrough\" |\n| \"The API reference\" | \"REST endpoints with auth requirements, rate limits, and request\u002Fresponse schemas\" |\n\n## llms-full.txt Format\n\nSame structure as `llms.txt` but with full content inlined:\n\n```markdown\n# {Project Name}\n\n> {Same summary}\n\n{Same context}\n\n## {Section Name}\n\n\u003Cdoc title=\"{Page Title}\" path=\"{relative-path}\">\n{Full markdown content — frontmatter stripped, citations and diagrams preserved}\n\u003C\u002Fdoc>\n```\n\n### Inlining Rules\n\n- **Strip YAML frontmatter** (`---` blocks) from each page\n- **Preserve Mermaid diagrams** — keep `` ```mermaid `` fences intact\n- **Preserve citations** — all `[file:line](URL)` links stay as-is\n- **Preserve tables** — all markdown tables stay intact\n- **Preserve `\u003C!-- Sources: -->` comments** — these provide diagram provenance\n\n## Prerequisites\n\nThis skill works best when wiki pages already exist (via `\u002Fdeep-wiki:generate` or `\u002Fdeep-wiki:page`). If no wiki exists yet:\n\n1. Suggest running `\u002Fdeep-wiki:generate` first\n2. OR generate a minimal `llms.txt` from README + source code scan (without wiki page links)\n\n## Output Files\n\nGenerate three files:\n\n| File | Purpose | Discoverability |\n|------|---------|-----------------|\n| `.\u002Fllms.txt` | Root discovery file | Standard path per llms.txt spec. GitHub MCP `get_file_contents` and `search_code` find this first. |\n| `wiki\u002Fllms.txt` | Wiki-relative links | For VitePress deployment and wiki-internal navigation. |\n| `wiki\u002Fllms-full.txt` | Full inlined content | Comprehensive reference for agents needing all docs in one file. |\n\nThe root `.\u002Fllms.txt` links into `wiki\u002F` (e.g., `[Guide](.\u002Fwiki\u002Fonboarding\u002Fcontributor-guide.md)`). The `wiki\u002Fllms.txt` uses wiki-relative paths (e.g., `[Guide](.\u002Fonboarding\u002Fcontributor-guide.md)`).\n\nIf a root `llms.txt` already exists and was NOT generated by deep-wiki, do NOT overwrite it.\n\n## Validation Checklist\n\nBefore finalizing:\n\n- [ ] All linked files in `llms.txt` actually exist\n- [ ] All `\u003Cdoc>` blocks in `llms-full.txt` have real content (not empty)\n- [ ] Blockquote is specific to this project (not generic boilerplate)\n- [ ] Sections ordered by importance\n- [ ] No duplicate page entries across sections\n- [ ] \"Optional\" section only contains truly optional content\n- [ ] `llms.txt` is concise (1-5 KB)\n- [ ] `llms-full.txt` contains all wiki pages\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-llms-txt",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-llms-txt",{"tool":41,"command":42},"bunx","bunx skills add qhjqhj00\u002Fresearch-skills-pool --skill wiki-llms-txt",{"tool":44,"command":45},"pnpm","pnpm dlx skills add qhjqhj00\u002Fresearch-skills-pool --skill wiki-llms-txt","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fmicrosoft--skills--.github__plugins__deep-wiki__skills__wiki-llms-txt\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",[],[]]