[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADY7RFV8CYPA3XEWE6FN9B":3,"skill-same:01M6ADY7RFV8CYPA3XEWE6FN9B":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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6ADY7RFV8CYPA3XEWE6FN9B","prompt-library",null,"Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-play prompts, or ready-to-use prompt examples for coding, writing, analysis, or creative tasks.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fai-research\u002Fprompt-library\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"prompt library","library","prompt","when","writing","for","techniques","high","Role-Based","task","ready","use","quality","coding","analysis","collection","examples","play","tasks","prompt templates","2026-11-10 10:12:30",false,"---\nname: prompt-library\ndescription: \"Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-play prompts, or ready-to-use prompt examples for coding, writing, analysis, or creative tasks.\"\n---\n\n# ? Prompt Library\n\n> A comprehensive collection of battle-tested prompts inspired by [awesome-chatgpt-prompts](https:\u002F\u002Fgithub.com\u002Ff\u002Fawesome-chatgpt-prompts) and community best practices.\n\n## When to Use This Skill\n\nUse this skill when the user:\n\n- Needs ready-to-use prompt templates\n- Wants role-based prompts (act as X)\n- Asks for prompt examples or inspiration\n- Needs task-specific prompt patterns\n- Wants to improve their prompting\n\n## Prompt Categories\n\n### ? Role-Based Prompts\n\n#### Expert Developer\n\n```\nAct as an expert software developer with 15+ years of experience. You specialize in clean code, SOLID principles, and pragmatic architecture. When reviewing code:\n1. Identify bugs and potential issues\n2. Suggest performance improvements\n3. Recommend better patterns\n4. Explain your reasoning clearly\nAlways prioritize readability and maintainability over cleverness.\n```\n\n#### Code Reviewer\n\n```\nAct as a senior code reviewer. Your role is to:\n1. Check for bugs, edge cases, and error handling\n2. Evaluate code structure and organization\n3. Assess naming conventions and readability\n4. Identify potential security issues\n5. Suggest improvements with specific examples\n\nFormat your review as:\n? Critical Issues (must fix)\n? Suggestions (should consider)\n? Praise (what's done well)\n```\n\n#### Technical Writer\n\n```\nAct as a technical documentation expert. Transform complex technical concepts into clear, accessible documentation. Follow these principles:\n- Use simple language, avoid jargon\n- Include practical examples\n- Structure with clear headings\n- Add code snippets where helpful\n- Consider the reader's experience level\n```\n\n#### System Architect\n\n```\nAct as a senior system architect designing for scale. Consider:\n- Scalability (horizontal and vertical)\n- Reliability (fault tolerance, redundancy)\n- Maintainability (modularity, clear boundaries)\n- Performance (latency, throughput)\n- Cost efficiency\n\nProvide architecture decisions with trade-off analysis.\n```\n\n### ?️ Task-Specific Prompts\n\n#### Debug This Code\n\n```\nDebug the following code. Your analysis should include:\n\n1. **Problem Identification**: What exactly is failing?\n2. **Root Cause**: Why is it failing?\n3. **Fix**: Provide corrected code\n4. **Prevention**: How to prevent similar bugs\n\nShow your debugging thought process step by step.\n```\n\n#### Explain Like I'm 5 (ELI5)\n\n```\nExplain [CONCEPT] as if I'm 5 years old. Use:\n- Simple everyday analogies\n- No technical jargon\n- Short sentences\n- Relatable examples from daily life\n- A fun, engaging tone\n```\n\n#### Code Refactoring\n\n```\nRefactor this code following these priorities:\n1. Readability first\n2. Remove duplication (DRY)\n3. Single responsibility per function\n4. Meaningful names\n5. Add comments only where necessary\n\nShow before\u002Fafter with explanation of changes.\n```\n\n#### Write Tests\n\n```\nWrite comprehensive tests for this code:\n1. Happy path scenarios\n2. Edge cases\n3. Error conditions\n4. Boundary values\n\nUse [FRAMEWORK] testing conventions. Include:\n- Descriptive test names\n- Arrange-Act-Assert pattern\n- Mocking where appropriate\n```\n\n#### API Documentation\n\n```\nGenerate API documentation for this endpoint including:\n- Endpoint URL and method\n- Request parameters (path, query, body)\n- Request\u002Fresponse examples\n- Error codes and meanings\n- Authentication requirements\n- Rate limits if applicable\n\nFormat as OpenAPI\u002FSwagger or Markdown.\n```\n\n### ? Analysis Prompts\n\n#### Code Complexity Analysis\n\n```\nAnalyze the complexity of this codebase:\n\n1. **Cyclomatic Complexity**: Identify complex functions\n2. **Coupling**: Find tightly coupled components\n3. **Cohesion**: Assess module cohesion\n4. **Dependencies**: Map critical dependencies\n5. **Technical Debt**: Highlight areas needing refactoring\n\nRate each area and provide actionable recommendations.\n```\n\n#### Performance Analysis\n\n```\nAnalyze this code for performance issues:\n\n1. **Time Complexity**: Big O analysis\n2. **Space Complexity**: Memory usage patterns\n3. **I\u002FO Bottlenecks**: Database, network, disk\n4. **Algorithmic Issues**: Inefficient patterns\n5. **Quick Wins**: Easy optimizations\n\nPrioritize findings by impact.\n```\n\n#### Security Review\n\n```\nPerform a security review of this code:\n\n1. **Input Validation**: Check all inputs\n2. **Authentication\u002FAuthorization**: Access control\n3. **Data Protection**: Sensitive data handling\n4. **Injection Vulnerabilities**: SQL, XSS, etc.\n5. **Dependencies**: Known vulnerabilities\n\nClassify issues by severity (Critical\u002FHigh\u002FMedium\u002FLow).\n```\n\n### ? Creative Prompts\n\n#### Brainstorm Features\n\n```\nBrainstorm features for [PRODUCT]:\n\nFor each feature, provide:\n- Name and one-line description\n- User value proposition\n- Implementation complexity (Low\u002FMed\u002FHigh)\n- Dependencies on other features\n\nGenerate 10 ideas, then rank top 3 by impact\u002Feffort ratio.\n```\n\n#### Name Generator\n\n```\nGenerate names for [PROJECT\u002FFEATURE]:\n\nProvide 10 options in these categories:\n- Descriptive (what it does)\n- Evocative (how it feels)\n- Acronyms (memorable abbreviations)\n- Metaphorical (analogies)\n\nFor each, explain the reasoning and check domain availability patterns.\n```\n\n### ? Transformation Prompts\n\n#### Migrate Code\n\n```\nMigrate this code from [SOURCE] to [TARGET]:\n\n1. Identify equivalent constructs\n2. Handle incompatible features\n3. Preserve functionality exactly\n4. Follow target language idioms\n5. Add necessary dependencies\n\nShow the migration step by step with explanations.\n```\n\n#### Convert Format\n\n```\nConvert this [SOURCE_FORMAT] to [TARGET_FORMAT]:\n\nRequirements:\n- Preserve all data\n- Use idiomatic target format\n- Handle edge cases\n- Validate the output\n- Provide sample verification\n```\n\n## Prompt Engineering Techniques\n\n### Chain of Thought (CoT)\n\n```\nLet's solve this step by step:\n1. First, I'll understand the problem\n2. Then, I'll identify the key components\n3. Next, I'll work through the logic\n4. Finally, I'll verify the solution\n\n[Your question here]\n```\n\n### Few-Shot Learning\n\n```\nHere are some examples of the task:\n\nExample 1:\nInput: [example input 1]\nOutput: [example output 1]\n\nExample 2:\nInput: [example input 2]\nOutput: [example output 2]\n\nNow complete this:\nInput: [actual input]\nOutput:\n```\n\n### Persona Pattern\n\n```\nYou are [PERSONA] with [TRAITS].\nYour communication style is [STYLE].\nYou prioritize [VALUES].\n\nWhen responding:\n- [Behavior 1]\n- [Behavior 2]\n- [Behavior 3]\n```\n\n### Structured Output\n\n```\nRespond in the following JSON format:\n{\n  \"analysis\": \"your analysis here\",\n  \"recommendations\": [\"rec1\", \"rec2\"],\n  \"confidence\": 0.0-1.0,\n  \"caveats\": [\"caveat1\"]\n}\n```\n\n## Prompt Improvement Checklist\n\nWhen crafting prompts, ensure:\n\n- [ ] **Clear objective**: What exactly do you want?\n- [ ] **Context provided**: Background information included?\n- [ ] **Format specified**: How should output be structured?\n- [ ] **Examples given**: Are there reference examples?\n- [ ] **Constraints defined**: Any limitations or requirements?\n- [ ] **Success criteria**: How do you measure good output?\n\n## Resources\n\n- [awesome-chatgpt-prompts](https:\u002F\u002Fgithub.com\u002Ff\u002Fawesome-chatgpt-prompts)\n- [prompts.chat](https:\u002F\u002Fprompts.chat)\n- [Learn Prompting](https:\u002F\u002Flearnprompting.org\u002F)\n\n---\n\n> ? **Tip**: The best prompts are specific, provide context, and include examples of desired output.\n","# ? Prompt Library\n\n> A comprehensive collection of battle-tested prompts inspired by [awesome-chatgpt-prompts](https:\u002F\u002Fgithub.com\u002Ff\u002Fawesome-chatgpt-prompts) and community best practices.\n\n## When to Use This Skill\n\nUse this skill when the user:\n\n- Needs ready-to-use prompt templates\n- Wants role-based prompts (act as X)\n- Asks for prompt examples or inspiration\n- Needs task-specific prompt patterns\n- Wants to improve their prompting\n\n## Prompt Categories\n\n### ? Role-Based Prompts\n\n#### Expert Developer\n\n```\nAct as an expert software developer with 15+ years of experience. You specialize in clean code, SOLID principles, and pragmatic architecture. When reviewing code:\n1. Identify bugs and potential issues\n2. Suggest performance improvements\n3. Recommend better patterns\n4. Explain your reasoning clearly\nAlways prioritize readability and maintainability over cleverness.\n```\n\n#### Code Reviewer\n\n```\nAct as a senior code reviewer. Your role is to:\n1. Check for bugs, edge cases, and error handling\n2. Evaluate code structure and organization\n3. Assess naming conventions and readability\n4. Identify potential security issues\n5. Suggest improvements with specific examples\n\nFormat your review as:\n? Critical Issues (must fix)\n? Suggestions (should consider)\n? Praise (what's done well)\n```\n\n#### Technical Writer\n\n```\nAct as a technical documentation expert. Transform complex technical concepts into clear, accessible documentation. Follow these principles:\n- Use simple language, avoid jargon\n- Include practical examples\n- Structure with clear headings\n- Add code snippets where helpful\n- Consider the reader's experience level\n```\n\n#### System Architect\n\n```\nAct as a senior system architect designing for scale. Consider:\n- Scalability (horizontal and vertical)\n- Reliability (fault tolerance, redundancy)\n- Maintainability (modularity, clear boundaries)\n- Performance (latency, throughput)\n- Cost efficiency\n\nProvide architecture decisions with trade-off analysis.\n```\n\n### ?️ Task-Specific Prompts\n\n#### Debug This Code\n\n```\nDebug the following code. Your analysis should include:\n\n1. **Problem Identification**: What exactly is failing?\n2. **Root Cause**: Why is it failing?\n3. **Fix**: Provide corrected code\n4. **Prevention**: How to prevent similar bugs\n\nShow your debugging thought process step by step.\n```\n\n#### Explain Like I'm 5 (ELI5)\n\n```\nExplain [CONCEPT] as if I'm 5 years old. Use:\n- Simple everyday analogies\n- No technical jargon\n- Short sentences\n- Relatable examples from daily life\n- A fun, engaging tone\n```\n\n#### Code Refactoring\n\n```\nRefactor this code following these priorities:\n1. Readability first\n2. Remove duplication (DRY)\n3. Single responsibility per function\n4. Meaningful names\n5. Add comments only where necessary\n\nShow before\u002Fafter with explanation of changes.\n```\n\n#### Write Tests\n\n```\nWrite comprehensive tests for this code:\n1. Happy path scenarios\n2. Edge cases\n3. Error conditions\n4. Boundary values\n\nUse [FRAMEWORK] testing conventions. Include:\n- Descriptive test names\n- Arrange-Act-Assert pattern\n- Mocking where appropriate\n```\n\n#### API Documentation\n\n```\nGenerate API documentation for this endpoint including:\n- Endpoint URL and method\n- Request parameters (path, query, body)\n- Request\u002Fresponse examples\n- Error codes and meanings\n- Authentication requirements\n- Rate limits if applicable\n\nFormat as OpenAPI\u002FSwagger or Markdown.\n```\n\n### ? Analysis Prompts\n\n#### Code Complexity Analysis\n\n```\nAnalyze the complexity of this codebase:\n\n1. **Cyclomatic Complexity**: Identify complex functions\n2. **Coupling**: Find tightly coupled components\n3. **Cohesion**: Assess module cohesion\n4. **Dependencies**: Map critical dependencies\n5. **Technical Debt**: Highlight areas needing refactoring\n\nRate each area and provide actionable recommendations.\n```\n\n#### Performance Analysis\n\n```\nAnalyze this code for performance issues:\n\n1. **Time Complexity**: Big O analysis\n2. **Space Complexity**: Memory usage patterns\n3. **I\u002FO Bottlenecks**: Database, network, disk\n4. **Algorithmic Issues**: Inefficient patterns\n5. **Quick Wins**: Easy optimizations\n\nPrioritize findings by impact.\n```\n\n#### Security Review\n\n```\nPerform a security review of this code:\n\n1. **Input Validation**: Check all inputs\n2. **Authentication\u002FAuthorization**: Access control\n3. **Data Protection**: Sensitive data handling\n4. **Injection Vulnerabilities**: SQL, XSS, etc.\n5. **Dependencies**: Known vulnerabilities\n\nClassify issues by severity (Critical\u002FHigh\u002FMedium\u002FLow).\n```\n\n### ? Creative Prompts\n\n#### Brainstorm Features\n\n```\nBrainstorm features for [PRODUCT]:\n\nFor each feature, provide:\n- Name and one-line description\n- User value proposition\n- Implementation complexity (Low\u002FMed\u002FHigh)\n- Dependencies on other features\n\nGenerate 10 ideas, then rank top 3 by impact\u002Feffort ratio.\n```\n\n#### Name Generator\n\n```\nGenerate names for [PROJECT\u002FFEATURE]:\n\nProvide 10 options in these categories:\n- Descriptive (what it does)\n- Evocative (how it feels)\n- Acronyms (memorable abbreviations)\n- Metaphorical (analogies)\n\nFor each, explain the reasoning and check domain availability patterns.\n```\n\n### ? Transformation Prompts\n\n#### Migrate Code\n\n```\nMigrate this code from [SOURCE] to [TARGET]:\n\n1. Identify equivalent constructs\n2. Handle incompatible features\n3. Preserve functionality exactly\n4. Follow target language idioms\n5. Add necessary dependencies\n\nShow the migration step by step with explanations.\n```\n\n#### Convert Format\n\n```\nConvert this [SOURCE_FORMAT] to [TARGET_FORMAT]:\n\nRequirements:\n- Preserve all data\n- Use idiomatic target format\n- Handle edge cases\n- Validate the output\n- Provide sample verification\n```\n\n## Prompt Engineering Techniques\n\n### Chain of Thought (CoT)\n\n```\nLet's solve this step by step:\n1. First, I'll understand the problem\n2. Then, I'll identify the key components\n3. Next, I'll work through the logic\n4. Finally, I'll verify the solution\n\n[Your question here]\n```\n\n### Few-Shot Learning\n\n```\nHere are some examples of the task:\n\nExample 1:\nInput: [example input 1]\nOutput: [example output 1]\n\nExample 2:\nInput: [example input 2]\nOutput: [example output 2]\n\nNow complete this:\nInput: [actual input]\nOutput:\n```\n\n### Persona Pattern\n\n```\nYou are [PERSONA] with [TRAITS].\nYour communication style is [STYLE].\nYou prioritize [VALUES].\n\nWhen responding:\n- [Behavior 1]\n- [Behavior 2]\n- [Behavior 3]\n```\n\n### Structured Output\n\n```\nRespond in the following JSON format:\n{\n  \"analysis\": \"your analysis here\",\n  \"recommendations\": [\"rec1\", \"rec2\"],\n  \"confidence\": 0.0-1.0,\n  \"caveats\": [\"caveat1\"]\n}\n```\n\n## Prompt Improvement Checklist\n\nWhen crafting prompts, ensure:\n\n- [ ] **Clear objective**: What exactly do you want?\n- [ ] **Context provided**: Background information included?\n- [ ] **Format specified**: How should output be structured?\n- [ ] **Examples given**: Are there reference examples?\n- [ ] **Constraints defined**: Any limitations or requirements?\n- [ ] **Success criteria**: How do you measure good output?\n\n## Resources\n\n- [awesome-chatgpt-prompts](https:\u002F\u002Fgithub.com\u002Ff\u002Fawesome-chatgpt-prompts)\n- [prompts.chat](https:\u002F\u002Fprompts.chat)\n- [Learn Prompting](https:\u002F\u002Flearnprompting.org\u002F)\n\n---\n\n> ? **Tip**: The best prompts are specific, provide context, and include examples of desired output.\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fai-research\u002Fprompt-library",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add davila7\u002Fclaude-code-templates --skill prompt-library",{"tool":70,"command":71},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill prompt-library",{"tool":73,"command":74},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill prompt-library","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fai-research\u002Fprompt-library\u002FSKILL.md",true,[],[79,104,131,162,197,221],{"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":49},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[85],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[87,88,89,90,91,34,92,93,40,32,94,95,96,97,98,99,100,101,102,103],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":111,"publishedAt":49},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[110],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[112,113,114,115,116,117,118,119,120,121,122,32,123,124,125,126,127,128,129,130],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":144,"publishedAt":49},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[137,140,141],{"categoryNo":138,"categoryName":139,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":142,"categoryName":143,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[145,146,147,148,149,150,151,34,152,153,154,155,156,157,158,40,159,160,32,161],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":166,"licenseFileUrl":167,"sourceHtmlUrl":168,"categories":169,"keywords":173,"publishedAt":49},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[170],{"categoryNo":171,"categoryName":172,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,34,196],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":166,"licenseFileUrl":201,"sourceHtmlUrl":202,"categories":203,"keywords":208,"publishedAt":49},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[204,207],{"categoryNo":205,"categoryName":206,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":171,"categoryName":172,"taxonomyType":21,"taxonomyTypeDesc":22},[209,210,211,212,213,175,214,184,185,215,216,217,218,34,219,95,220],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":166,"licenseFileUrl":225,"sourceHtmlUrl":226,"categories":227,"keywords":235,"publishedAt":49},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[228,231,232],{"categoryNo":229,"categoryName":230,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":233,"categoryName":234,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[236,237,238,239,240,241,242,33,177,243,187,123,244,245,246,247,248,157,249,32,250,43,251,252,253,101,254],"discernment nudge","nudge","interpretation","help","run","reasoning","data","lookup","content","review","conversation","short","up","invoke","you","claims","argument","assemble","recommendations"]