[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75CC3P2TJSB7ND4Z1XXDTKP":3,"skill-same:01M75CC3P2TJSB7ND4Z1XXDTKP":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75CC3P2TJSB7ND4Z1XXDTKP","code-tour",null,"Use when the user asks to create a CodeTour .tour file — persona-targeted, step-by-step walkthroughs that link to real files and line numbers. Trigger for: create a tour, onboarding tour, architecture tour, PR review tour, explain how X works, vibe check, RCA tour, contributor guide, or any structured code walkthrough request.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fcode-tour\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"code-tour\"\ndescription: \"Use when the user asks to create a CodeTour .tour file — persona-targeted, step-by-step walkthroughs that link to real files and line numbers. Trigger for: create a tour, onboarding tour, architecture tour, PR review tour, explain how X works, vibe check, RCA tour, contributor guide, or any structured code walkthrough request.\"\n---\n\n# Code Tour\n\nCreate **CodeTour** files — persona-targeted, step-by-step walkthroughs of a codebase that link directly to files and line numbers. CodeTour files live in `.tours\u002F` and work with the [VS Code CodeTour extension](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcodetour).\n\n## Overview\n\nA great tour is a **narrative** — a story told to a specific person about what matters, why it matters, and what to do next. Only create `.tour` JSON files. Never modify source code.\n\n## When to Use This Skill\n\n- User asks to create a code tour, onboarding tour, or architecture walkthrough\n- User says \"tour for this PR\", \"explain how X works\", \"vibe check\", \"RCA tour\"\n- User wants a contributor guide, security review, or bug investigation walkthrough\n- Any request for a structured walkthrough with file\u002Fline anchors\n\n## Core Workflow\n\n### 1. Discover the repo\n\nBefore asking anything, explore the codebase:\n\nIn parallel: list root directory, read README, check config files.\nThen: identify language(s), framework(s), project purpose. Map folder structure 1-2 levels deep. Find entry points — every path in the tour must be real.\n\nIf the repo has fewer than 5 source files, create a quick-depth tour regardless of persona — there's not enough to warrant a deep one.\n\n### 2. Infer the intent\n\nOne message should be enough. Infer persona, depth, and focus silently.\n\n| User says | Persona | Depth |\n|-----------|---------|-------|\n| \"tour for this PR\" | pr-reviewer | standard |\n| \"why did X break\" \u002F \"RCA\" | rca-investigator | standard |\n| \"onboarding\" \u002F \"new joiner\" | new-joiner | standard |\n| \"quick tour\" \u002F \"vibe check\" | vibecoder | quick |\n| \"architecture\" | architect | deep |\n| \"security\" \u002F \"auth review\" | security-reviewer | standard |\n| (no qualifier) | new-joiner | standard |\n\nWhen intent is ambiguous, default to **new-joiner** persona at **standard** depth — it's the most generally useful.\n\n### 3. Read actual files\n\n**Every file path and line number must be verified.** A tour pointing to the wrong line is worse than no tour.\n\n### 4. Write the tour\n\nSave to `.tours\u002F\u003Cpersona>-\u003Cfocus>.tour`.\n\n```json\n{\n  \"$schema\": \"https:\u002F\u002Faka.ms\u002Fcodetour-schema\",\n  \"title\": \"Descriptive Title — Persona \u002F Goal\",\n  \"description\": \"Who this is for and what they'll understand after.\",\n  \"ref\": \"\u003Ccurrent-branch-or-commit>\",\n  \"steps\": []\n}\n```\n\n### Step types\n\n| Type | When to use | Example |\n|------|-------------|---------|\n| **Content** | Intro\u002Fclosing only (max 2) | `{ \"title\": \"Welcome\", \"description\": \"...\" }` |\n| **Directory** | Orient to a module | `{ \"directory\": \"src\u002Fservices\", \"title\": \"...\" }` |\n| **File + line** | The workhorse | `{ \"file\": \"src\u002Fauth.ts\", \"line\": 42, \"title\": \"...\" }` |\n| **Selection** | Highlight a code block | `{ \"file\": \"...\", \"selection\": {...}, \"title\": \"...\" }` |\n| **Pattern** | Regex match (volatile files) | `{ \"file\": \"...\", \"pattern\": \"class App\", \"title\": \"...\" }` |\n| **URI** | Link to PR, issue, doc | `{ \"uri\": \"https:\u002F\u002F...\", \"title\": \"...\" }` |\n\n### Step count\n\n| Depth | Steps | Use for |\n|-------|-------|---------|\n| Quick | 5-8 | Vibecoder, fast exploration |\n| Standard | 9-13 | Most personas |\n| Deep | 14-18 | Architect, RCA |\n\n### Writing descriptions — SMIG formula\n\n- **S — Situation**: What is the reader looking at?\n- **M — Mechanism**: How does this code work?\n- **I — Implication**: Why does this matter for this persona?\n- **G — Gotcha**: What would a smart person get wrong?\n\n### 5. Validate\n\n- [ ] Every `file` path relative to repo root (no leading `\u002F` or `.\u002F`)\n- [ ] Every `file` confirmed to exist\n- [ ] Every `line` verified by reading the file\n- [ ] First step has `file` or `directory` anchor\n- [ ] At most 2 content-only steps\n- [ ] `nextTour` matches another tour's `title` exactly if set\n\n## Personas\n\n| Persona | Goal | Must cover |\n|---------|------|------------|\n| **Vibecoder** | Get the vibe fast | Entry point, main modules. Max 8 steps. |\n| **New joiner** | Structured ramp-up | Directories, setup, business context |\n| **Bug fixer** | Root cause fast | Trigger -> fault points -> tests |\n| **RCA investigator** | Why did it fail | Causality chain, observability anchors |\n| **Feature explainer** | End-to-end | UI -> API -> backend -> storage |\n| **PR reviewer** | Review correctly | Change story, invariants, risky areas |\n| **Architect** | Shape and rationale | Boundaries, tradeoffs, extension points |\n| **Security reviewer** | Trust boundaries | Auth flow, validation, secret handling |\n| **Refactorer** | Safe restructuring | Seams, hidden deps, extraction order |\n| **External contributor** | Contribute safely | Safe areas, conventions, landmines |\n\n## Narrative Arc\n\n1. **Orientation** — `file` or `directory` step (never content-only first step — blank in VS Code)\n2. **High-level map** — 1-3 directory steps showing major modules\n3. **Core path** — file\u002Fline steps, the heart of the tour\n4. **Closing** — what the reader can now do, suggested follow-ups\n\n## Anti-Patterns\n\n| Anti-pattern | Fix |\n|---|---|\n| **File listing** — \"this file contains the models\" | Tell a story. Each step depends on the previous. |\n| **Generic descriptions** | Name the specific pattern unique to this codebase. |\n| **Line number guessing** | Never write a line you didn't verify by reading. |\n| **Too many steps** for quick depth | Actually cut steps. |\n| **Hallucinated files** | If it doesn't exist, skip the step. |\n| **Recap closing** — \"we covered X, Y, Z\" | Tell the reader what they can now *do*. |\n| **Content-only first step** | Anchor step 1 to a file or directory. |\n\n## Cross-References\n\n- Related: `engineering\u002Fcodebase-onboarding` — for broader onboarding beyond tours\n- Related: `engineering\u002Fpr-review-expert` — for automated PR review workflows\n- CodeTour extension: [microsoft\u002Fcodetour](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcodetour)\n- Real-world tours: [coder\u002Fcode-server](https:\u002F\u002Fgithub.com\u002Fcoder\u002Fcode-server\u002Fblob\u002Fmain\u002F.tours\u002Fcontributing.tour)\n","# Code Tour\n\nCreate **CodeTour** files — persona-targeted, step-by-step walkthroughs of a codebase that link directly to files and line numbers. CodeTour files live in `.tours\u002F` and work with the [VS Code CodeTour extension](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcodetour).\n\n## Overview\n\nA great tour is a **narrative** — a story told to a specific person about what matters, why it matters, and what to do next. Only create `.tour` JSON files. Never modify source code.\n\n## When to Use This Skill\n\n- User asks to create a code tour, onboarding tour, or architecture walkthrough\n- User says \"tour for this PR\", \"explain how X works\", \"vibe check\", \"RCA tour\"\n- User wants a contributor guide, security review, or bug investigation walkthrough\n- Any request for a structured walkthrough with file\u002Fline anchors\n\n## Core Workflow\n\n### 1. Discover the repo\n\nBefore asking anything, explore the codebase:\n\nIn parallel: list root directory, read README, check config files.\nThen: identify language(s), framework(s), project purpose. Map folder structure 1-2 levels deep. Find entry points — every path in the tour must be real.\n\nIf the repo has fewer than 5 source files, create a quick-depth tour regardless of persona — there's not enough to warrant a deep one.\n\n### 2. Infer the intent\n\nOne message should be enough. Infer persona, depth, and focus silently.\n\n| User says | Persona | Depth |\n|-----------|---------|-------|\n| \"tour for this PR\" | pr-reviewer | standard |\n| \"why did X break\" \u002F \"RCA\" | rca-investigator | standard |\n| \"onboarding\" \u002F \"new joiner\" | new-joiner | standard |\n| \"quick tour\" \u002F \"vibe check\" | vibecoder | quick |\n| \"architecture\" | architect | deep |\n| \"security\" \u002F \"auth review\" | security-reviewer | standard |\n| (no qualifier) | new-joiner | standard |\n\nWhen intent is ambiguous, default to **new-joiner** persona at **standard** depth — it's the most generally useful.\n\n### 3. Read actual files\n\n**Every file path and line number must be verified.** A tour pointing to the wrong line is worse than no tour.\n\n### 4. Write the tour\n\nSave to `.tours\u002F\u003Cpersona>-\u003Cfocus>.tour`.\n\n```json\n{\n  \"$schema\": \"https:\u002F\u002Faka.ms\u002Fcodetour-schema\",\n  \"title\": \"Descriptive Title — Persona \u002F Goal\",\n  \"description\": \"Who this is for and what they'll understand after.\",\n  \"ref\": \"\u003Ccurrent-branch-or-commit>\",\n  \"steps\": []\n}\n```\n\n### Step types\n\n| Type | When to use | Example |\n|------|-------------|---------|\n| **Content** | Intro\u002Fclosing only (max 2) | `{ \"title\": \"Welcome\", \"description\": \"...\" }` |\n| **Directory** | Orient to a module | `{ \"directory\": \"src\u002Fservices\", \"title\": \"...\" }` |\n| **File + line** | The workhorse | `{ \"file\": \"src\u002Fauth.ts\", \"line\": 42, \"title\": \"...\" }` |\n| **Selection** | Highlight a code block | `{ \"file\": \"...\", \"selection\": {...}, \"title\": \"...\" }` |\n| **Pattern** | Regex match (volatile files) | `{ \"file\": \"...\", \"pattern\": \"class App\", \"title\": \"...\" }` |\n| **URI** | Link to PR, issue, doc | `{ \"uri\": \"https:\u002F\u002F...\", \"title\": \"...\" }` |\n\n### Step count\n\n| Depth | Steps | Use for |\n|-------|-------|---------|\n| Quick | 5-8 | Vibecoder, fast exploration |\n| Standard | 9-13 | Most personas |\n| Deep | 14-18 | Architect, RCA |\n\n### Writing descriptions — SMIG formula\n\n- **S — Situation**: What is the reader looking at?\n- **M — Mechanism**: How does this code work?\n- **I — Implication**: Why does this matter for this persona?\n- **G — Gotcha**: What would a smart person get wrong?\n\n### 5. Validate\n\n- [ ] Every `file` path relative to repo root (no leading `\u002F` or `.\u002F`)\n- [ ] Every `file` confirmed to exist\n- [ ] Every `line` verified by reading the file\n- [ ] First step has `file` or `directory` anchor\n- [ ] At most 2 content-only steps\n- [ ] `nextTour` matches another tour's `title` exactly if set\n\n## Personas\n\n| Persona | Goal | Must cover |\n|---------|------|------------|\n| **Vibecoder** | Get the vibe fast | Entry point, main modules. Max 8 steps. |\n| **New joiner** | Structured ramp-up | Directories, setup, business context |\n| **Bug fixer** | Root cause fast | Trigger -> fault points -> tests |\n| **RCA investigator** | Why did it fail | Causality chain, observability anchors |\n| **Feature explainer** | End-to-end | UI -> API -> backend -> storage |\n| **PR reviewer** | Review correctly | Change story, invariants, risky areas |\n| **Architect** | Shape and rationale | Boundaries, tradeoffs, extension points |\n| **Security reviewer** | Trust boundaries | Auth flow, validation, secret handling |\n| **Refactorer** | Safe restructuring | Seams, hidden deps, extraction order |\n| **External contributor** | Contribute safely | Safe areas, conventions, landmines |\n\n## Narrative Arc\n\n1. **Orientation** — `file` or `directory` step (never content-only first step — blank in VS Code)\n2. **High-level map** — 1-3 directory steps showing major modules\n3. **Core path** — file\u002Fline steps, the heart of the tour\n4. **Closing** — what the reader can now do, suggested follow-ups\n\n## Anti-Patterns\n\n| Anti-pattern | Fix |\n|---|---|\n| **File listing** — \"this file contains the models\" | Tell a story. Each step depends on the previous. |\n| **Generic descriptions** | Name the specific pattern unique to this codebase. |\n| **Line number guessing** | Never write a line you didn't verify by reading. |\n| **Too many steps** for quick depth | Actually cut steps. |\n| **Hallucinated files** | If it doesn't exist, skip the step. |\n| **Recap closing** — \"we covered X, Y, Z\" | Tell the reader what they can now *do*. |\n| **Content-only first step** | Anchor step 1 to a file or directory. |\n\n## Cross-References\n\n- Related: `engineering\u002Fcodebase-onboarding` — for broader onboarding beyond tours\n- Related: `engineering\u002Fpr-review-expert` — for automated PR review workflows\n- CodeTour extension: [microsoft\u002Fcodetour](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcodetour)\n- Real-world tours: [coder\u002Fcode-server](https:\u002F\u002Fgithub.com\u002Fcoder\u002Fcode-server\u002Fblob\u002Fmain\u002F.tours\u002Fcontributing.tour)\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fcode-tour",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill code-tour",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill code-tour",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill code-tour","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fcode-tour\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]