[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFW994N69QES3FM88AEJYV":3,"skill-same:01M6AFW994N69QES3FM88AEJYV":81},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6AFW994N69QES3FM88AEJYV","vulnerability-scanner",null,"Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","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\u002Fsecurity\u002Fvulnerability-scanner\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"vulnerability","vulnerability scanner","scanner","chain security","security","vulnerability analysis","supply","advanced","principles","2025","mapping","chain","supply chain","read","Bash","prioritization","analysis","risk","owasp","supply chain security","2026-11-10 10:12:30",false,"---\nname: vulnerability-scanner\ndescription: Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.\nallowed-tools: Read, Glob, Grep, Bash\n---\n\n# Vulnerability Scanner\n\n> Think like an attacker, defend like an expert. 2025 threat landscape awareness.\n\n## ? Runtime Scripts\n\n**Execute for automated validation:**\n\n| Script | Purpose | Usage |\n|--------|---------|-------|\n| `scripts\u002Fsecurity_scan.py` | Validate security principles applied | `python scripts\u002Fsecurity_scan.py \u003Cproject_path>` |\n\n## ? Reference Files\n\n| File | Purpose |\n|------|---------|\n| [checklists.md](checklists.md) | OWASP Top 10, Auth, API, Data protection checklists |\n\n---\n\n## 1. Security Expert Mindset\n\n### Core Principles\n\n| Principle | Application |\n|-----------|-------------|\n| **Assume Breach** | Design as if attacker already inside |\n| **Zero Trust** | Never trust, always verify |\n| **Defense in Depth** | Multiple layers, no single point |\n| **Least Privilege** | Minimum required access only |\n| **Fail Secure** | On error, deny access |\n\n### Threat Modeling Questions\n\nBefore scanning, ask:\n1. What are we protecting? (Assets)\n2. Who would attack? (Threat actors)\n3. How would they attack? (Attack vectors)\n4. What's the impact? (Business risk)\n\n---\n\n## 2. OWASP Top 10:2025\n\n### Risk Categories\n\n| Rank | Category | Think About |\n|------|----------|-------------|\n| **A01** | Broken Access Control | Who can access what? IDOR, SSRF |\n| **A02** | Security Misconfiguration | Defaults, headers, exposed services |\n| **A03** | Software Supply Chain ? | Dependencies, CI\u002FCD, build integrity |\n| **A04** | Cryptographic Failures | Weak crypto, exposed secrets |\n| **A05** | Injection | User input → system commands |\n| **A06** | Insecure Design | Flawed architecture |\n| **A07** | Authentication Failures | Session, credential management |\n| **A08** | Integrity Failures | Unsigned updates, tampered data |\n| **A09** | Logging & Alerting | Blind spots, no monitoring |\n| **A10** | Exceptional Conditions ? | Error handling, fail-open states |\n\n### 2025 Key Changes\n\n```\n2021 → 2025 Shifts:\n├── SSRF merged into A01 (Access Control)\n├── A02 elevated (Cloud\u002FContainer configs)\n├── A03 NEW: Supply Chain (major focus)\n├── A10 NEW: Exceptional Conditions\n└── Focus shift: Root causes > Symptoms\n```\n\n---\n\n## 3. Supply Chain Security (A03)\n\n### Attack Surface\n\n| Vector | Risk | Question to Ask |\n|--------|------|-----------------|\n| **Dependencies** | Malicious packages | Do we audit new deps? |\n| **Lock files** | Integrity attacks | Are they committed? |\n| **Build pipeline** | CI\u002FCD compromise | Who can modify? |\n| **Registry** | Typosquatting | Verified sources? |\n\n### Defense Principles\n\n- Verify package integrity (checksums)\n- Pin versions, audit updates\n- Use private registries for critical deps\n- Sign and verify artifacts\n\n---\n\n## 4. Attack Surface Mapping\n\n### What to Map\n\n| Category | Elements |\n|----------|----------|\n| **Entry Points** | APIs, forms, file uploads |\n| **Data Flows** | Input → Process → Output |\n| **Trust Boundaries** | Where auth\u002Fauthz checked |\n| **Assets** | Secrets, PII, business data |\n\n### Prioritization Matrix\n\n```\nRisk = Likelihood × Impact\n\nHigh Impact + High Likelihood → CRITICAL\nHigh Impact + Low Likelihood  → HIGH\nLow Impact + High Likelihood  → MEDIUM\nLow Impact + Low Likelihood   → LOW\n```\n\n---\n\n## 5. Risk Prioritization\n\n### CVSS + Context\n\n| Factor | Weight | Question |\n|--------|--------|----------|\n| **CVSS Score** | Base severity | How severe is the vuln? |\n| **EPSS Score** | Exploit likelihood | Is it being exploited? |\n| **Asset Value** | Business context | What's at risk? |\n| **Exposure** | Attack surface | Internet-facing? |\n\n### Prioritization Decision Tree\n\n```\nIs it actively exploited (EPSS >0.5)?\n├── YES → CRITICAL: Immediate action\n└── NO → Check CVSS\n         ├── CVSS ≥9.0 → HIGH\n         ├── CVSS 7.0-8.9 → Consider asset value\n         └── CVSS \u003C7.0 → Schedule for later\n```\n\n---\n\n## 6. Exceptional Conditions (A10 - New)\n\n### Fail-Open vs Fail-Closed\n\n| Scenario | Fail-Open (BAD) | Fail-Closed (GOOD) |\n|----------|-----------------|---------------------|\n| Auth error | Allow access | Deny access |\n| Parsing fails | Accept input | Reject input |\n| Timeout | Retry forever | Limit + abort |\n\n### What to Check\n\n- Exception handlers that catch-all and ignore\n- Missing error handling on security operations\n- Race conditions in auth\u002Fauthz\n- Resource exhaustion scenarios\n\n---\n\n## 7. Scanning Methodology\n\n### Phase-Based Approach\n\n```\n1. RECONNAISSANCE\n   └── Understand the target\n       ├── Technology stack\n       ├── Entry points\n       └── Data flows\n\n2. DISCOVERY\n   └── Identify potential issues\n       ├── Configuration review\n       ├── Dependency analysis\n       └── Code pattern search\n\n3. ANALYSIS\n   └── Validate and prioritize\n       ├── False positive elimination\n       ├── Risk scoring\n       └── Attack chain mapping\n\n4. REPORTING\n   └── Actionable findings\n       ├── Clear reproduction steps\n       ├── Business impact\n       └── Remediation guidance\n```\n\n---\n\n## 8. Code Pattern Analysis\n\n### High-Risk Patterns\n\n| Pattern | Risk | Look For |\n|---------|------|----------|\n| **String concat in queries** | Injection | `\"SELECT * FROM \" + user_input` |\n| **Dynamic code execution** | RCE | `eval()`, `exec()`, `Function()` |\n| **Unsafe deserialization** | RCE | `pickle.loads()`, `unserialize()` |\n| **Path manipulation** | Traversal | User input in file paths |\n| **Disabled security** | Various | `verify=False`, `--insecure` |\n\n### Secret Patterns\n\n| Type | Indicators |\n|------|-----------|\n| API Keys | `api_key`, `apikey`, high entropy |\n| Tokens | `token`, `bearer`, `jwt` |\n| Credentials | `password`, `secret`, `key` |\n| Cloud | `AWS_`, `AZURE_`, `GCP_` prefixes |\n\n---\n\n## 9. Cloud Security Considerations\n\n### Shared Responsibility\n\n| Layer | You Own | Provider Owns |\n|-------|---------|---------------|\n| Data | ✅ | ❌ |\n| Application | ✅ | ❌ |\n| OS\u002FRuntime | Depends | Depends |\n| Infrastructure | ❌ | ✅ |\n\n### Cloud-Specific Checks\n\n- IAM: Least privilege applied?\n- Storage: Public buckets?\n- Network: Security groups tightened?\n- Secrets: Using secrets manager?\n\n---\n\n## 10. Anti-Patterns\n\n| ❌ Don't | ✅ Do |\n|----------|-------|\n| Scan without understanding | Map attack surface first |\n| Alert on every CVE | Prioritize by exploitability + asset |\n| Ignore false positives | Maintain verified baseline |\n| Fix symptoms only | Address root causes |\n| Scan once before deploy | Continuous scanning |\n| Trust third-party deps blindly | Verify integrity, audit code |\n\n---\n\n## 11. Reporting Principles\n\n### Finding Structure\n\nEach finding should answer:\n1. **What?** - Clear vulnerability description\n2. **Where?** - Exact location (file, line, endpoint)\n3. **Why?** - Root cause explanation\n4. **Impact?** - Business consequence\n5. **How to fix?** - Specific remediation\n\n### Severity Classification\n\n| Severity | Criteria |\n|----------|----------|\n| **Critical** | RCE, auth bypass, mass data exposure |\n| **High** | Data exposure, privilege escalation |\n| **Medium** | Limited scope, requires conditions |\n| **Low** | Informational, best practice |\n\n---\n\n> **Remember:** Vulnerability scanning finds issues. Expert thinking prioritizes what matters. Always ask: \"What would an attacker do with this?\"\n","# Vulnerability Scanner\n\n> Think like an attacker, defend like an expert. 2025 threat landscape awareness.\n\n## ? Runtime Scripts\n\n**Execute for automated validation:**\n\n| Script | Purpose | Usage |\n|--------|---------|-------|\n| `scripts\u002Fsecurity_scan.py` | Validate security principles applied | `python scripts\u002Fsecurity_scan.py \u003Cproject_path>` |\n\n## ? Reference Files\n\n| File | Purpose |\n|------|---------|\n| [checklists.md](checklists.md) | OWASP Top 10, Auth, API, Data protection checklists |\n\n---\n\n## 1. Security Expert Mindset\n\n### Core Principles\n\n| Principle | Application |\n|-----------|-------------|\n| **Assume Breach** | Design as if attacker already inside |\n| **Zero Trust** | Never trust, always verify |\n| **Defense in Depth** | Multiple layers, no single point |\n| **Least Privilege** | Minimum required access only |\n| **Fail Secure** | On error, deny access |\n\n### Threat Modeling Questions\n\nBefore scanning, ask:\n1. What are we protecting? (Assets)\n2. Who would attack? (Threat actors)\n3. How would they attack? (Attack vectors)\n4. What's the impact? (Business risk)\n\n---\n\n## 2. OWASP Top 10:2025\n\n### Risk Categories\n\n| Rank | Category | Think About |\n|------|----------|-------------|\n| **A01** | Broken Access Control | Who can access what? IDOR, SSRF |\n| **A02** | Security Misconfiguration | Defaults, headers, exposed services |\n| **A03** | Software Supply Chain ? | Dependencies, CI\u002FCD, build integrity |\n| **A04** | Cryptographic Failures | Weak crypto, exposed secrets |\n| **A05** | Injection | User input → system commands |\n| **A06** | Insecure Design | Flawed architecture |\n| **A07** | Authentication Failures | Session, credential management |\n| **A08** | Integrity Failures | Unsigned updates, tampered data |\n| **A09** | Logging & Alerting | Blind spots, no monitoring |\n| **A10** | Exceptional Conditions ? | Error handling, fail-open states |\n\n### 2025 Key Changes\n\n```\n2021 → 2025 Shifts:\n├── SSRF merged into A01 (Access Control)\n├── A02 elevated (Cloud\u002FContainer configs)\n├── A03 NEW: Supply Chain (major focus)\n├── A10 NEW: Exceptional Conditions\n└── Focus shift: Root causes > Symptoms\n```\n\n---\n\n## 3. Supply Chain Security (A03)\n\n### Attack Surface\n\n| Vector | Risk | Question to Ask |\n|--------|------|-----------------|\n| **Dependencies** | Malicious packages | Do we audit new deps? |\n| **Lock files** | Integrity attacks | Are they committed? |\n| **Build pipeline** | CI\u002FCD compromise | Who can modify? |\n| **Registry** | Typosquatting | Verified sources? |\n\n### Defense Principles\n\n- Verify package integrity (checksums)\n- Pin versions, audit updates\n- Use private registries for critical deps\n- Sign and verify artifacts\n\n---\n\n## 4. Attack Surface Mapping\n\n### What to Map\n\n| Category | Elements |\n|----------|----------|\n| **Entry Points** | APIs, forms, file uploads |\n| **Data Flows** | Input → Process → Output |\n| **Trust Boundaries** | Where auth\u002Fauthz checked |\n| **Assets** | Secrets, PII, business data |\n\n### Prioritization Matrix\n\n```\nRisk = Likelihood × Impact\n\nHigh Impact + High Likelihood → CRITICAL\nHigh Impact + Low Likelihood  → HIGH\nLow Impact + High Likelihood  → MEDIUM\nLow Impact + Low Likelihood   → LOW\n```\n\n---\n\n## 5. Risk Prioritization\n\n### CVSS + Context\n\n| Factor | Weight | Question |\n|--------|--------|----------|\n| **CVSS Score** | Base severity | How severe is the vuln? |\n| **EPSS Score** | Exploit likelihood | Is it being exploited? |\n| **Asset Value** | Business context | What's at risk? |\n| **Exposure** | Attack surface | Internet-facing? |\n\n### Prioritization Decision Tree\n\n```\nIs it actively exploited (EPSS >0.5)?\n├── YES → CRITICAL: Immediate action\n└── NO → Check CVSS\n         ├── CVSS ≥9.0 → HIGH\n         ├── CVSS 7.0-8.9 → Consider asset value\n         └── CVSS \u003C7.0 → Schedule for later\n```\n\n---\n\n## 6. Exceptional Conditions (A10 - New)\n\n### Fail-Open vs Fail-Closed\n\n| Scenario | Fail-Open (BAD) | Fail-Closed (GOOD) |\n|----------|-----------------|---------------------|\n| Auth error | Allow access | Deny access |\n| Parsing fails | Accept input | Reject input |\n| Timeout | Retry forever | Limit + abort |\n\n### What to Check\n\n- Exception handlers that catch-all and ignore\n- Missing error handling on security operations\n- Race conditions in auth\u002Fauthz\n- Resource exhaustion scenarios\n\n---\n\n## 7. Scanning Methodology\n\n### Phase-Based Approach\n\n```\n1. RECONNAISSANCE\n   └── Understand the target\n       ├── Technology stack\n       ├── Entry points\n       └── Data flows\n\n2. DISCOVERY\n   └── Identify potential issues\n       ├── Configuration review\n       ├── Dependency analysis\n       └── Code pattern search\n\n3. ANALYSIS\n   └── Validate and prioritize\n       ├── False positive elimination\n       ├── Risk scoring\n       └── Attack chain mapping\n\n4. REPORTING\n   └── Actionable findings\n       ├── Clear reproduction steps\n       ├── Business impact\n       └── Remediation guidance\n```\n\n---\n\n## 8. Code Pattern Analysis\n\n### High-Risk Patterns\n\n| Pattern | Risk | Look For |\n|---------|------|----------|\n| **String concat in queries** | Injection | `\"SELECT * FROM \" + user_input` |\n| **Dynamic code execution** | RCE | `eval()`, `exec()`, `Function()` |\n| **Unsafe deserialization** | RCE | `pickle.loads()`, `unserialize()` |\n| **Path manipulation** | Traversal | User input in file paths |\n| **Disabled security** | Various | `verify=False`, `--insecure` |\n\n### Secret Patterns\n\n| Type | Indicators |\n|------|-----------|\n| API Keys | `api_key`, `apikey`, high entropy |\n| Tokens | `token`, `bearer`, `jwt` |\n| Credentials | `password`, `secret`, `key` |\n| Cloud | `AWS_`, `AZURE_`, `GCP_` prefixes |\n\n---\n\n## 9. Cloud Security Considerations\n\n### Shared Responsibility\n\n| Layer | You Own | Provider Owns |\n|-------|---------|---------------|\n| Data | ✅ | ❌ |\n| Application | ✅ | ❌ |\n| OS\u002FRuntime | Depends | Depends |\n| Infrastructure | ❌ | ✅ |\n\n### Cloud-Specific Checks\n\n- IAM: Least privilege applied?\n- Storage: Public buckets?\n- Network: Security groups tightened?\n- Secrets: Using secrets manager?\n\n---\n\n## 10. Anti-Patterns\n\n| ❌ Don't | ✅ Do |\n|----------|-------|\n| Scan without understanding | Map attack surface first |\n| Alert on every CVE | Prioritize by exploitability + asset |\n| Ignore false positives | Maintain verified baseline |\n| Fix symptoms only | Address root causes |\n| Scan once before deploy | Continuous scanning |\n| Trust third-party deps blindly | Verify integrity, audit code |\n\n---\n\n## 11. Reporting Principles\n\n### Finding Structure\n\nEach finding should answer:\n1. **What?** - Clear vulnerability description\n2. **Where?** - Exact location (file, line, endpoint)\n3. **Why?** - Root cause explanation\n4. **Impact?** - Business consequence\n5. **How to fix?** - Specific remediation\n\n### Severity Classification\n\n| Severity | Criteria |\n|----------|----------|\n| **Critical** | RCE, auth bypass, mass data exposure |\n| **High** | Data exposure, privilege escalation |\n| **Medium** | Limited scope, requires conditions |\n| **Low** | Informational, best practice |\n\n---\n\n> **Remember:** Vulnerability scanning finds issues. Expert thinking prioritizes what matters. Always ask: \"What would an attacker do with this?\"\n",{"name":5,"description":7,"allowed-tools":44},"Read, Glob, Grep, Bash","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner",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":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add davila7\u002Fclaude-code-templates --skill vulnerability-scanner",{"tool":61,"command":62},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill vulnerability-scanner",{"tool":64,"command":65},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill vulnerability-scanner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner\u002FSKILL.md",true,[69,75],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"checklists.md","REFERENCE","参考文档",2746,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner\u002Fchecklists.md",{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"scripts\u002Fsecurity_scan.py","SCRIPT","脚本",18170,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner\u002Fscripts\u002Fsecurity_scan.py",[82,114,141,174,209,233],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":93,"publishedAt":39},"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",[88],{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","use","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":121,"publishedAt":39},"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",[120],{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},[122,123,124,125,126,127,128,129,130,131,132,103,133,134,135,136,137,138,139,140],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":156,"publishedAt":39},"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",[147,150,151],{"categoryNo":148,"categoryName":149,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},{"categoryNo":152,"categoryName":153,"taxonomyType":154,"taxonomyTypeDesc":155},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[157,158,159,160,161,162,163,99,164,165,166,167,168,169,170,102,171,172,103,173],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":178,"licenseFileUrl":179,"sourceHtmlUrl":180,"categories":181,"keywords":185,"publishedAt":39},"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",[182],{"categoryNo":183,"categoryName":184,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000009","前端开发",[186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,99,208],"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":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":178,"licenseFileUrl":213,"sourceHtmlUrl":214,"categories":215,"keywords":220,"publishedAt":39},"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",[216,219],{"categoryNo":217,"categoryName":218,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":183,"categoryName":184,"taxonomyType":91,"taxonomyTypeDesc":92},[221,222,223,224,225,187,226,196,197,227,228,229,230,99,231,105,232],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":178,"licenseFileUrl":237,"sourceHtmlUrl":238,"categories":239,"keywords":247,"publishedAt":39},"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",[240,243,244],{"categoryNo":241,"categoryName":242,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},{"categoryNo":245,"categoryName":246,"taxonomyType":154,"taxonomyTypeDesc":155},"01JBSEEDCAT000000000000036","内容创作者",[248,249,250,251,252,253,254,255,189,256,199,133,257,258,259,260,261,169,262,103,263,35,264,265,266,111,267],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","claims","argument","assemble","recommendations"]