[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70P0F19QJYCV9YY458YYGRF":3,"skill-same:01M70P0F19QJYCV9YY458YYGRF":78},{"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":34,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M70P0F19QJYCV9YY458YYGRF","writing-agents",null,"How to write Claude Code agents that trigger reliably, use the right model, and produce consistent output. Use when creating, improving, or reviewing agent definitions.","shengdabai\u002FTony-Claude-Code-Skills","shengdabai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116417419?v=4","01M70F6D2WY5PQV5A92BKYJQEW","Tony Sheng","01M70F6D3GAAAYZ5H4CC1G8VXM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-agents\u002FSKILL.md",[18,23,26,31],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者",[35,36,37,38,39,40,41,42,43,44,45,46,47],"writing","writing agents","model","how to","when","code","how","write","code agents","trigger","produce","use","output","2026-11-10 10:12:30",false,"---\nname: writing-agents\ndescription: \"How to write Claude Code agents that trigger reliably, use the right model, and produce consistent output. Use when creating, improving, or reviewing agent definitions.\"\nversion: 0.1.0\n---\n\n# Writing Agents\n\n> Scope: covers agent `.md` file authoring. For multi-agent orchestration, see [[orchestration]]. For plugin architecture, see [[writing-plugins]].\n\n## 1. Example Blocks Make or Break Triggering\n\nWithout `\u003Cexample>` blocks, Claude guesses when to dispatch your agent. With them, it pattern-matches against real scenarios.\n\n**Minimum**: 2 examples. **Ideal**: 3 -- one obvious trigger, one edge case, one non-obvious.\n\n### Example Block Anatomy\n\n```xml\n\u003Cexample>\nContext: [what the user is doing -- not just \"user needs help\"]\nuser: \"[realistic user message that should trigger this agent]\"\nassistant: \"[what Claude says when dispatching -- shows the decision logic]\"\n\u003C\u002Fexample>\n```\n\n### Bad Example (too vague -- 40% trigger accuracy)\n\n```xml\n\u003Cexample>\nContext: User needs code review\nuser: \"review my code\"\nassistant: \"I'll use the reviewer agent.\"\n\u003C\u002Fexample>\n```\n\n**Problems**: generic context, generic query, no decision logic shown.\n\n### Good Example (specific scenario -- 92% trigger accuracy)\n\n```xml\n\u003Cexample>\nContext: User just pushed changes to the authentication module and wants feedback before merging\nuser: \"Can you check if the auth changes look good before I create the PR?\"\nassistant: \"I'll dispatch the security-reviewer agent to check the auth changes for vulnerabilities, token handling, and session management best practices.\"\n\u003C\u002Fexample>\n```\n\n**Why it works**: specific context (auth module, pre-PR), realistic query (how users actually talk), decision logic visible (what the agent will check).\n\n### The Three-Example Pattern\n\n| Example | Purpose | What it demonstrates |\n|---------|---------|---------------------|\n| 1. Obvious trigger | Baseline dispatch | User explicitly asks for what the agent does |\n| 2. Edge case | Boundary behavior | User asks something adjacent -- agent should still trigger |\n| 3. Non-obvious | Discovery | User doesn't know the agent exists but their need matches |\n\nExample for a \"performance-profiler\" agent:\n\n```xml\n\u003C!-- Example 1: Obvious -->\n\u003Cexample>\nContext: User wants to profile their API\nuser: \"Profile the \u002Fapi\u002Fusers endpoint, it's slow\"\nassistant: \"I'll dispatch the performance-profiler to trace the \u002Fapi\u002Fusers endpoint...\"\n\u003C\u002Fexample>\n\n\u003C!-- Example 2: Edge case -->\n\u003Cexample>\nContext: User notices high memory usage but doesn't mention profiling\nuser: \"The app uses 2GB of RAM after running for an hour, is there a leak?\"\nassistant: \"I'll dispatch the performance-profiler to analyze memory allocation patterns...\"\n\u003C\u002Fexample>\n\n\u003C!-- Example 3: Non-obvious -->\n\u003Cexample>\nContext: User is comparing two implementation approaches\nuser: \"Should I use a JOIN here or two separate queries?\"\nassistant: \"I'll dispatch the performance-profiler to benchmark both approaches...\"\n\u003C\u002Fexample>\n```\n\n## 2. Model Selection\n\n| Task type | Model | Signal words in body | Examples |\n|-----------|-------|---------------------|----------|\n| Mechanical \u002F parsing \u002F formatting \u002F counting | haiku | count, list, extract, format, parse, scan | scanner, parser, formatter, counter, lister |\n| Analysis \u002F reasoning \u002F moderate judgment | sonnet | analyze, review, evaluate, summarize, compare | linter, reviewer, extractor, summarizer |\n| Complex judgment \u002F orchestration \u002F multi-agent | opus | coordinate, decide, assess, synthesize, architect | QC coordinator, architect, strategy planner |\n\n### Quick Heuristic\n\nCount the instruction lines in your agent body. Then check for judgment words.\n\n```\n\u003C 20 instruction lines AND no judgment words → haiku\n20-50 instruction lines OR judgment words → sonnet\n> 50 instruction lines OR coordination logic → opus\n```\n\nJudgment words: evaluate, decide, assess, determine, weigh, prioritize, recommend, judge, infer, synthesize.\n\n### Cost Impact\n\n| Model | Relative cost | When to upgrade |\n|-------|--------------|-----------------|\n| haiku | 1x | Agent produces wrong output on edge cases |\n| sonnet | 10x | Agent produces wrong output on easy cases |\n| opus | 30x | Agent coordinates other agents or makes architectural decisions |\n\n**Rule**: start with haiku, upgrade only when output quality requires it.\n\n## 3. Tool Least-Privilege\n\nOnly list tools the agent body actually references. Every extra tool is a potential misuse vector.\n\n### Common Mistakes\n\n| Agent type | Common over-grant | Correct tools |\n|-----------|-------------------|---------------|\n| Audit\u002Freview agent | Write, Edit, Bash | Read, Glob, Grep |\n| Code generator | Read, Grep (unused) | Write, Edit, Bash |\n| Orchestrator | Read, Write (does no IO) | Task |\n| Scanner | Bash (uses grep) | Grep, Glob, Read |\n\n### Tool Reference\n\n| Tool | When to include |\n|------|----------------|\n| Read | Agent reads file contents |\n| Write | Agent creates new files |\n| Edit | Agent modifies existing files |\n| Glob | Agent searches for files by pattern |\n| Grep | Agent searches file contents |\n| Bash | Agent runs shell commands (linters, tests, builds) |\n| Task | Agent dispatches sub-agents |\n| Fetch | Agent makes HTTP requests |\n\n## 4. Output Format\n\nEvery agent MUST define its output format in the body. Without it, output varies between invocations -- making results unparseable by parent agents.\n\n### Pattern: Structured Report\n\n```markdown\n## Output Format\n\n### {Section Title}\n| Column1 | Column2 | Column3 |\n|---------|---------|---------|\n| ...     | ...     | ...     |\n\n### Summary\n- Total items: {N}\n- Issues found: {N}\n- Pass\u002FFail: {verdict}\n```\n\n### Pattern: Severity-Tagged Findings\n\n```markdown\n## Output Format\n\nFor each finding, output:\n\n**[SEVERITY] Finding title**\n- File: `path\u002Fto\u002Ffile`\n- Line: {N}\n- Issue: {description}\n- Fix: {concrete suggestion}\n\nSeverity levels: CRITICAL > HIGH > MEDIUM > LOW > INFO\n```\n\n### Pattern: Pass\u002FFail Gate\n\n```markdown\n## Output Format\n\nFinal line must be exactly one of:\n- `PASS: All checks passed`\n- `WARN: {N} warnings found (see above)`\n- `FAIL: {N} errors found (see above)`\n```\n\n## 5. System Prompt Structure\n\nOrder matters. Claude reads top-to-bottom and front-loads early instructions.\n\n### The Five Sections\n\n```markdown\n## Mission\n[1-2 sentences: what this agent does and WHY it exists]\n\n## Instructions\n1. [First step]\n2. [Second step]\n3. [Third step]\n...\n\n## Boundaries\n- Do NOT [thing that would be harmful]\n- Do NOT [thing that's out of scope]\n- If [ambiguous situation], then [explicit resolution]\n\n## Output Format\n[Exact template -- see section 4 above]\n\n## Error Handling\n- If no files found: report \"No matching files\" and exit\n- If tool fails: report the error and continue with remaining work\n- If scope is unclear: analyze the narrower interpretation\n```\n\n### Section Sizing\n\n| Section | Target lines | Over-budget signal |\n|---------|-------------|-------------------|\n| Mission | 2-3 | More than one paragraph |\n| Instructions | 5-15 | More than 20 numbered steps |\n| Boundaries | 3-7 | More than 10 \"Do NOT\" items |\n| Output Format | 5-15 | Defining more than 3 output sections |\n| Error Handling | 3-5 | More than 5 error cases |\n\nTotal agent body: aim for 25-45 lines. Over 60 lines means the agent is doing too much -- split it.\n\n## 6. Worked Example\n\n### Before (score 52\u002F100)\n\n```yaml\n---\nname: code-checker\ndescription: Check code\nmodel: opus\ntools: [Read, Write, Edit, Bash, Grep, Glob, Task]\n---\n```\n\n```markdown\nYou are a code checker. Check the user's code for issues.\nLook at the files and find problems. Report what you find.\n```\n\n**Problems:**\n- Description: 0 trigger phrases, no \"Use when...\" (-30)\n- Model: opus for a simple review task (-10)\n- Tools: 7 tools granted, body uses maybe 3 (-10)\n- No examples: unreliable triggering (-15)\n- No output format: inconsistent results (-15)\n- No boundaries: scope creep (-10)\n- No error handling: silent failures (-10)\n\n### After (score 95\u002F100)\n\n```yaml\n---\nname: code-checker\ndescription: \"Static analysis agent — checks code for bugs, type errors, and anti-patterns. Use when reviewing code quality, running pre-commit checks, or validating changes before PR.\"\nmodel: sonnet\ntools: [Read, Glob, Grep]\n---\n```\n\n```markdown\n## Mission\nAnalyze source code files for bugs, type errors, and anti-patterns.\nProduce a structured report with severity-tagged findings.\n\n## Instructions\n1. Use Glob to discover files matching the target pattern\n2. Use Read to examine each file\n3. Use Grep to cross-reference imports and usage patterns\n4. For each issue found, classify severity and provide a concrete fix\n5. Produce the output report\n\n## Boundaries\n- Do NOT modify any files (read-only analysis)\n- Do NOT run shell commands\n- Do NOT report style issues (defer to linter)\n- If no target pattern specified, analyze all files in src\u002F\n\n## Output Format\n\nFor each finding:\n\n**[SEVERITY] Issue title**\n- File: `path\u002Fto\u002Ffile`\n- Line: {N}\n- Issue: {description}\n- Fix: {concrete fix}\n\nFinal line:\n- `PASS: No issues found`\n- `WARN: {N} warnings found`\n- `FAIL: {N} errors found`\n\n## Error Handling\n- If no files match the pattern: report \"No matching files for pattern: {X}\"\n- If a file cannot be read: skip it and note in the report\n```\n\n```xml\n\u003Cexample>\nContext: User just finished implementing a new feature and wants a quality check\nuser: \"Check the auth module for any bugs before I push\"\nassistant: \"I'll dispatch the code-checker agent to analyze src\u002Fauth\u002F for bugs, type errors, and anti-patterns.\"\n\u003C\u002Fexample>\n\n\u003Cexample>\nContext: User is debugging a production issue and suspects a code defect\nuser: \"Something's wrong with the payment flow, can you scan it?\"\nassistant: \"I'll dispatch the code-checker to analyze the payment module for potential bugs and logic errors.\"\n\u003C\u002Fexample>\n```\n\n**Changes made:**\n1. Description: 0 -> 6 trigger phrases (+30)\n2. Model: opus -> sonnet (appropriate for analysis, -20x cost) (+10)\n3. Tools: 7 -> 3 (read-only analysis needs read-only tools) (+10)\n4. Added 2 examples (+15)\n5. Defined output format (+15)\n6. Added boundaries (+10)\n7. Added error handling (+5)\n\n## 7. Common Mistakes\n\n| Mistake | Impact | Fix |\n|---------|--------|-----|\n| No examples | 40% trigger accuracy | Add 2-3 specific scenario examples |\n| Opus for mechanical work | 30x cost for same result | Use haiku for parsing, sonnet for analysis |\n| All tools granted | Agent writes when it should only read | List only tools the body references |\n| No output format | Different format each run | Define exact output template |\n| Body over 60 lines | Agent is doing too much | Split into focused sub-agents |\n| \"Be thorough\" in body | Meaningless filler | Replace with specific instructions |\n| No error handling | Silent failures | Add 3-5 error cases with resolution |\n","# Writing Agents\n\n> Scope: covers agent `.md` file authoring. For multi-agent orchestration, see [[orchestration]]. For plugin architecture, see [[writing-plugins]].\n\n## 1. Example Blocks Make or Break Triggering\n\nWithout `\u003Cexample>` blocks, Claude guesses when to dispatch your agent. With them, it pattern-matches against real scenarios.\n\n**Minimum**: 2 examples. **Ideal**: 3 -- one obvious trigger, one edge case, one non-obvious.\n\n### Example Block Anatomy\n\n```xml\n\u003Cexample>\nContext: [what the user is doing -- not just \"user needs help\"]\nuser: \"[realistic user message that should trigger this agent]\"\nassistant: \"[what Claude says when dispatching -- shows the decision logic]\"\n\u003C\u002Fexample>\n```\n\n### Bad Example (too vague -- 40% trigger accuracy)\n\n```xml\n\u003Cexample>\nContext: User needs code review\nuser: \"review my code\"\nassistant: \"I'll use the reviewer agent.\"\n\u003C\u002Fexample>\n```\n\n**Problems**: generic context, generic query, no decision logic shown.\n\n### Good Example (specific scenario -- 92% trigger accuracy)\n\n```xml\n\u003Cexample>\nContext: User just pushed changes to the authentication module and wants feedback before merging\nuser: \"Can you check if the auth changes look good before I create the PR?\"\nassistant: \"I'll dispatch the security-reviewer agent to check the auth changes for vulnerabilities, token handling, and session management best practices.\"\n\u003C\u002Fexample>\n```\n\n**Why it works**: specific context (auth module, pre-PR), realistic query (how users actually talk), decision logic visible (what the agent will check).\n\n### The Three-Example Pattern\n\n| Example | Purpose | What it demonstrates |\n|---------|---------|---------------------|\n| 1. Obvious trigger | Baseline dispatch | User explicitly asks for what the agent does |\n| 2. Edge case | Boundary behavior | User asks something adjacent -- agent should still trigger |\n| 3. Non-obvious | Discovery | User doesn't know the agent exists but their need matches |\n\nExample for a \"performance-profiler\" agent:\n\n```xml\n\u003C!-- Example 1: Obvious -->\n\u003Cexample>\nContext: User wants to profile their API\nuser: \"Profile the \u002Fapi\u002Fusers endpoint, it's slow\"\nassistant: \"I'll dispatch the performance-profiler to trace the \u002Fapi\u002Fusers endpoint...\"\n\u003C\u002Fexample>\n\n\u003C!-- Example 2: Edge case -->\n\u003Cexample>\nContext: User notices high memory usage but doesn't mention profiling\nuser: \"The app uses 2GB of RAM after running for an hour, is there a leak?\"\nassistant: \"I'll dispatch the performance-profiler to analyze memory allocation patterns...\"\n\u003C\u002Fexample>\n\n\u003C!-- Example 3: Non-obvious -->\n\u003Cexample>\nContext: User is comparing two implementation approaches\nuser: \"Should I use a JOIN here or two separate queries?\"\nassistant: \"I'll dispatch the performance-profiler to benchmark both approaches...\"\n\u003C\u002Fexample>\n```\n\n## 2. Model Selection\n\n| Task type | Model | Signal words in body | Examples |\n|-----------|-------|---------------------|----------|\n| Mechanical \u002F parsing \u002F formatting \u002F counting | haiku | count, list, extract, format, parse, scan | scanner, parser, formatter, counter, lister |\n| Analysis \u002F reasoning \u002F moderate judgment | sonnet | analyze, review, evaluate, summarize, compare | linter, reviewer, extractor, summarizer |\n| Complex judgment \u002F orchestration \u002F multi-agent | opus | coordinate, decide, assess, synthesize, architect | QC coordinator, architect, strategy planner |\n\n### Quick Heuristic\n\nCount the instruction lines in your agent body. Then check for judgment words.\n\n```\n\u003C 20 instruction lines AND no judgment words → haiku\n20-50 instruction lines OR judgment words → sonnet\n> 50 instruction lines OR coordination logic → opus\n```\n\nJudgment words: evaluate, decide, assess, determine, weigh, prioritize, recommend, judge, infer, synthesize.\n\n### Cost Impact\n\n| Model | Relative cost | When to upgrade |\n|-------|--------------|-----------------|\n| haiku | 1x | Agent produces wrong output on edge cases |\n| sonnet | 10x | Agent produces wrong output on easy cases |\n| opus | 30x | Agent coordinates other agents or makes architectural decisions |\n\n**Rule**: start with haiku, upgrade only when output quality requires it.\n\n## 3. Tool Least-Privilege\n\nOnly list tools the agent body actually references. Every extra tool is a potential misuse vector.\n\n### Common Mistakes\n\n| Agent type | Common over-grant | Correct tools |\n|-----------|-------------------|---------------|\n| Audit\u002Freview agent | Write, Edit, Bash | Read, Glob, Grep |\n| Code generator | Read, Grep (unused) | Write, Edit, Bash |\n| Orchestrator | Read, Write (does no IO) | Task |\n| Scanner | Bash (uses grep) | Grep, Glob, Read |\n\n### Tool Reference\n\n| Tool | When to include |\n|------|----------------|\n| Read | Agent reads file contents |\n| Write | Agent creates new files |\n| Edit | Agent modifies existing files |\n| Glob | Agent searches for files by pattern |\n| Grep | Agent searches file contents |\n| Bash | Agent runs shell commands (linters, tests, builds) |\n| Task | Agent dispatches sub-agents |\n| Fetch | Agent makes HTTP requests |\n\n## 4. Output Format\n\nEvery agent MUST define its output format in the body. Without it, output varies between invocations -- making results unparseable by parent agents.\n\n### Pattern: Structured Report\n\n```markdown\n## Output Format\n\n### {Section Title}\n| Column1 | Column2 | Column3 |\n|---------|---------|---------|\n| ...     | ...     | ...     |\n\n### Summary\n- Total items: {N}\n- Issues found: {N}\n- Pass\u002FFail: {verdict}\n```\n\n### Pattern: Severity-Tagged Findings\n\n```markdown\n## Output Format\n\nFor each finding, output:\n\n**[SEVERITY] Finding title**\n- File: `path\u002Fto\u002Ffile`\n- Line: {N}\n- Issue: {description}\n- Fix: {concrete suggestion}\n\nSeverity levels: CRITICAL > HIGH > MEDIUM > LOW > INFO\n```\n\n### Pattern: Pass\u002FFail Gate\n\n```markdown\n## Output Format\n\nFinal line must be exactly one of:\n- `PASS: All checks passed`\n- `WARN: {N} warnings found (see above)`\n- `FAIL: {N} errors found (see above)`\n```\n\n## 5. System Prompt Structure\n\nOrder matters. Claude reads top-to-bottom and front-loads early instructions.\n\n### The Five Sections\n\n```markdown\n## Mission\n[1-2 sentences: what this agent does and WHY it exists]\n\n## Instructions\n1. [First step]\n2. [Second step]\n3. [Third step]\n...\n\n## Boundaries\n- Do NOT [thing that would be harmful]\n- Do NOT [thing that's out of scope]\n- If [ambiguous situation], then [explicit resolution]\n\n## Output Format\n[Exact template -- see section 4 above]\n\n## Error Handling\n- If no files found: report \"No matching files\" and exit\n- If tool fails: report the error and continue with remaining work\n- If scope is unclear: analyze the narrower interpretation\n```\n\n### Section Sizing\n\n| Section | Target lines | Over-budget signal |\n|---------|-------------|-------------------|\n| Mission | 2-3 | More than one paragraph |\n| Instructions | 5-15 | More than 20 numbered steps |\n| Boundaries | 3-7 | More than 10 \"Do NOT\" items |\n| Output Format | 5-15 | Defining more than 3 output sections |\n| Error Handling | 3-5 | More than 5 error cases |\n\nTotal agent body: aim for 25-45 lines. Over 60 lines means the agent is doing too much -- split it.\n\n## 6. Worked Example\n\n### Before (score 52\u002F100)\n\n```yaml\n---\nname: code-checker\ndescription: Check code\nmodel: opus\ntools: [Read, Write, Edit, Bash, Grep, Glob, Task]\n---\n```\n\n```markdown\nYou are a code checker. Check the user's code for issues.\nLook at the files and find problems. Report what you find.\n```\n\n**Problems:**\n- Description: 0 trigger phrases, no \"Use when...\" (-30)\n- Model: opus for a simple review task (-10)\n- Tools: 7 tools granted, body uses maybe 3 (-10)\n- No examples: unreliable triggering (-15)\n- No output format: inconsistent results (-15)\n- No boundaries: scope creep (-10)\n- No error handling: silent failures (-10)\n\n### After (score 95\u002F100)\n\n```yaml\n---\nname: code-checker\ndescription: \"Static analysis agent — checks code for bugs, type errors, and anti-patterns. Use when reviewing code quality, running pre-commit checks, or validating changes before PR.\"\nmodel: sonnet\ntools: [Read, Glob, Grep]\n---\n```\n\n```markdown\n## Mission\nAnalyze source code files for bugs, type errors, and anti-patterns.\nProduce a structured report with severity-tagged findings.\n\n## Instructions\n1. Use Glob to discover files matching the target pattern\n2. Use Read to examine each file\n3. Use Grep to cross-reference imports and usage patterns\n4. For each issue found, classify severity and provide a concrete fix\n5. Produce the output report\n\n## Boundaries\n- Do NOT modify any files (read-only analysis)\n- Do NOT run shell commands\n- Do NOT report style issues (defer to linter)\n- If no target pattern specified, analyze all files in src\u002F\n\n## Output Format\n\nFor each finding:\n\n**[SEVERITY] Issue title**\n- File: `path\u002Fto\u002Ffile`\n- Line: {N}\n- Issue: {description}\n- Fix: {concrete fix}\n\nFinal line:\n- `PASS: No issues found`\n- `WARN: {N} warnings found`\n- `FAIL: {N} errors found`\n\n## Error Handling\n- If no files match the pattern: report \"No matching files for pattern: {X}\"\n- If a file cannot be read: skip it and note in the report\n```\n\n```xml\n\u003Cexample>\nContext: User just finished implementing a new feature and wants a quality check\nuser: \"Check the auth module for any bugs before I push\"\nassistant: \"I'll dispatch the code-checker agent to analyze src\u002Fauth\u002F for bugs, type errors, and anti-patterns.\"\n\u003C\u002Fexample>\n\n\u003Cexample>\nContext: User is debugging a production issue and suspects a code defect\nuser: \"Something's wrong with the payment flow, can you scan it?\"\nassistant: \"I'll dispatch the code-checker to analyze the payment module for potential bugs and logic errors.\"\n\u003C\u002Fexample>\n```\n\n**Changes made:**\n1. Description: 0 -> 6 trigger phrases (+30)\n2. Model: opus -> sonnet (appropriate for analysis, -20x cost) (+10)\n3. Tools: 7 -> 3 (read-only analysis needs read-only tools) (+10)\n4. Added 2 examples (+15)\n5. Defined output format (+15)\n6. Added boundaries (+10)\n7. Added error handling (+5)\n\n## 7. Common Mistakes\n\n| Mistake | Impact | Fix |\n|---------|--------|-----|\n| No examples | 40% trigger accuracy | Add 2-3 specific scenario examples |\n| Opus for mechanical work | 30x cost for same result | Use haiku for parsing, sonnet for analysis |\n| All tools granted | Agent writes when it should only read | List only tools the body references |\n| No output format | Different format each run | Define exact output template |\n| Body over 60 lines | Agent is doing too much | Split into focused sub-agents |\n| \"Be thorough\" in body | Meaningless filler | Replace with specific instructions |\n| No error handling | Silent failures | Add 3-5 error cases with resolution |\n",{"name":5,"version":53,"description":7},"0.1.0","main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-agents",1,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills","https:\u002F\u002Fzturnsgo.com","https:\u002F\u002Fgithub.com\u002Fshengdabai","https:\u002F\u002Fzturnsgo.com\u002F","AI × education creator — producer, not consumer. Taught 6,000+ learners; shipping learning tools & daily essays with Claude Code, practicing @xiaolai's way 🥋","2026-11-01 21:28:23",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill writing-agents",{"tool":70,"command":71},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill writing-agents",{"tool":73,"command":74},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill writing-agents","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-agents\u002FSKILL.md",true,[],[79,93,120,143,165,181],{"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":86,"publishedAt":48},"01M70P17DAD4C1C47NPH6A96EM","xiaolai-methodology","以李笑来(Li Xiaolai)的思考方式、方法论与表达风格,为用户做全方位 1-on-1 教练指导,覆盖创业、赚钱、投资、学习、自学、读书写作、用 AI、以及人生心态与自我管理。当用户提到 \"李笑来\"、\"笑来\"、\"笑来老师\"、\"扮演李笑来\"、\"找笑来聊聊\"、\"笑来怎么看\"、\"xiaolai\"、\"把时间当作朋友\"、\"通往财富自由之路\"、\"定投改变命运\"、\"韭菜的自我修养\"、\"自学是门手艺\"、\"让时间陪你慢慢变富\"、\"七年就是一辈子\"、\"元认知\"、\"活在未来\"、\"复利\u002F长期主义\"、\"践行\"、\"痴迷改进\"、\"个人商业模式\u002F出售时间\"、\"睡后收入\"、\"定投\"、\"财富自由\"、\"操作系统升级\"、\"最少必要知识\"、\"北极星提示词\"、\"用 AI 该怎么学\u002F思考\" 等任一触发词,或当用户带着关于创业\u002F赚钱\u002F投资\u002F学习\u002F职业\u002F重大人生决策的困惑、希望被人用笑来式的「逻辑 + 大白话 + 类比 + 重新定义 + 践行导向」来点醒和指导时,自动进入李笑来教练模式。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fxiaolai-methodology\u002FSKILL.md",[85],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[87,88,89,90,91,35,92],"methodology","xiaolai","xiaolai methodology","朋友","投资","收入",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":101,"publishedAt":48},"01M70P13NB9YP7ACJR1S861CDS","zread","Produce and consume a wiki-style knowledge base for a code repository via the `zread` CLI and its on-disk output under `.\u002F.zread\u002Fwiki\u002F`. Use this skill whenever the user wants to understand, onboard onto, explore, summarize, map, or get an overview of an unfamiliar codebase; asks for architecture docs, a project wiki, a repo walkthrough, module\u002Fpackage explanations, or \"what does this repo do\"; wants to generate, regenerate, resume, browse, or serve code documentation locally; or mentions zread \u002F zread.ai directly. Also use it proactively before diving into a large unknown repo — if `.\u002F.zread\u002Fwiki\u002Fcurrent` exists, read the generated pages instead of crawling source file-by-file; if it doesn't, consider offering to run `zread generate`. The trigger is the intent (understand a codebase through generated docs), not the literal word \"zread\".","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fzread\u002FSKILL.md",[99,100],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[95,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,40,118,119],"knowledge","wiki","explore","walkthrough","project","get","knowledge base","run","generate","intent","cli","map","documentation","project wiki","disk","architecture","unknown","generated",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":128,"publishedAt":48},"01M70P10S4SWMZQ8BJAFBFDRW3","youtube","Launch the YouTube Creator Agent to auto-generate videos.\nUse when: user types \u002Fyoutube, wants to create YouTube videos,\ngenerate video content, or upload to YouTube.\nKeywords: youtube, video, 视频, 创作视频, 发布视频","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[126,127],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},[122,129,130,131,132,133,134,135,110,136,137,138,39,46,139,140,141,142],"user","content","视频","creator","generate video","videos","launch","video content","create","upload","auto","types","Video","创作",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":150,"publishedAt":48},"01M70P0YE95D8BACZCGV8BK90K","youtube-script-sync","Sync, update, or optimize Tony's GetNote knowledge base `Youtube视频逐字稿` by turning each parent recording or first-person idea note into an idempotent child note containing a directly recordable YouTube long-video or Shorts script. Use when the user says “更新\u002F同步\u002F优化 Youtube视频逐字稿知识库”, or says “更新\u002F同步\u002F优化该知识库” while this knowledge base is the active context.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-script-sync\u002FSKILL.md",[149],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[151,152,122,153,154,141,155,156,157,158,159,160,161,162,108,163,39,46,102,164],"sync","script","youtube script sync","recording","shorts","first","base","person","update","active","child","optimize","idempotent","long",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":175,"publishedAt":48},"01M70P0WMV5XT0EEC0N445PW07","writing-skills","How to write SKILL.md files that trigger reliably and teach effectively. Use when creating, improving, or reviewing Claude Code skills.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-skills\u002FSKILL.md",[171,172,173,174],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},[176,35,41,177,178,42,40,39,46,179,180,38,44],"writing skills","teach","write skill","claude code skills","files",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":189,"publishedAt":48},"01M70P0SJFR4YVJQBGMHKGSKXT","writing-rules","How to write .claude\u002Frules\u002F files that Claude actually follows. Use when creating, improving, or reviewing project rules.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-rules\u002FSKILL.md",[187,188],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},[190,35,191,106,192,180,39,41,42,46,38],"Rules","writing rules","project rules"]