[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFX0KVG33H3KHH2NMPNWAB":3,"skill-same:01M6AFX0KVG33H3KHH2NMPNWAB":83},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6AFX0KVG33H3KHH2NMPNWAB","commit",null,"Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33332,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsentry\u002Fcommit\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"when","writing","changes","with","formatting","create commit","conventions","references","conventional commits","issue","use","history","commit messages","commits","messages","sentry","git","code","create","2026-11-10 10:12:30",false,"---\nname: commit\ndescription: Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.\n---\n\n# Sentry Commit Messages\n\nFollow these conventions when creating commits for Sentry projects.\n\n## Format\n\n```\n\u003Ctype>(\u003Cscope>): \u003Csubject>\n\n\u003Cbody>\n\n\u003Cfooter>\n```\n\nThe header is required. Scope is optional. All lines must stay under 100 characters.\n\n## Commit Types\n\n| Type | Purpose |\n|------|---------|\n| `feat` | New feature |\n| `fix` | Bug fix |\n| `ref` | Refactoring (no behavior change) |\n| `perf` | Performance improvement |\n| `docs` | Documentation only |\n| `test` | Test additions or corrections |\n| `build` | Build system or dependencies |\n| `ci` | CI configuration |\n| `chore` | Maintenance tasks |\n| `style` | Code formatting (no logic change) |\n| `meta` | Repository metadata |\n| `license` | License changes |\n\n## Subject Line Rules\n\n- Use imperative, present tense: \"Add feature\" not \"Added feature\"\n- Capitalize the first letter\n- No period at the end\n- Maximum 70 characters\n\n## Body Guidelines\n\n- Explain **what** and **why**, not how\n- Use imperative mood and present tense\n- Include motivation for the change\n- Contrast with previous behavior when relevant\n\n## Footer: Issue References\n\nReference issues in the footer using these patterns:\n\n```\nFixes GH-1234\nFixes #1234\nFixes SENTRY-1234\nRefs LINEAR-ABC-123\n```\n\n- `Fixes` closes the issue when merged\n- `Refs` links without closing\n\n## Examples\n\n### Simple fix\n\n```\nfix(api): Handle null response in user endpoint\n\nThe user API could return null for deleted accounts, causing a crash\nin the dashboard. Add null check before accessing user properties.\n\nFixes SENTRY-5678\n```\n\n### Feature with scope\n\n```\nfeat(alerts): Add Slack thread replies for alert updates\n\nWhen an alert is updated or resolved, post a reply to the original\nSlack thread instead of creating a new message. This keeps related\nnotifications grouped together.\n\nRefs GH-1234\n```\n\n### Refactor\n\n```\nref: Extract common validation logic to shared module\n\nMove duplicate validation code from three endpoints into a shared\nvalidator class. No behavior change.\n```\n\n### Breaking change\n\n```\nfeat(api)!: Remove deprecated v1 endpoints\n\nRemove all v1 API endpoints that were deprecated in version 23.1.\nClients should migrate to v2 endpoints.\n\nBREAKING CHANGE: v1 endpoints no longer available\nFixes SENTRY-9999\n```\n\n## Revert Format\n\n```\nrevert: feat(api): Add new endpoint\n\nThis reverts commit abc123def456.\n\nReason: Caused performance regression in production.\n```\n\n## Principles\n\n- Each commit should be a single, stable change\n- Commits should be independently reviewable\n- The repository should be in a working state after each commit\n\n## References\n\n- [Sentry Commit Messages](https:\u002F\u002Fdevelop.sentry.dev\u002Fengineering-practices\u002Fcommit-messages\u002F)\n","# Sentry Commit Messages\n\nFollow these conventions when creating commits for Sentry projects.\n\n## Format\n\n```\n\u003Ctype>(\u003Cscope>): \u003Csubject>\n\n\u003Cbody>\n\n\u003Cfooter>\n```\n\nThe header is required. Scope is optional. All lines must stay under 100 characters.\n\n## Commit Types\n\n| Type | Purpose |\n|------|---------|\n| `feat` | New feature |\n| `fix` | Bug fix |\n| `ref` | Refactoring (no behavior change) |\n| `perf` | Performance improvement |\n| `docs` | Documentation only |\n| `test` | Test additions or corrections |\n| `build` | Build system or dependencies |\n| `ci` | CI configuration |\n| `chore` | Maintenance tasks |\n| `style` | Code formatting (no logic change) |\n| `meta` | Repository metadata |\n| `license` | License changes |\n\n## Subject Line Rules\n\n- Use imperative, present tense: \"Add feature\" not \"Added feature\"\n- Capitalize the first letter\n- No period at the end\n- Maximum 70 characters\n\n## Body Guidelines\n\n- Explain **what** and **why**, not how\n- Use imperative mood and present tense\n- Include motivation for the change\n- Contrast with previous behavior when relevant\n\n## Footer: Issue References\n\nReference issues in the footer using these patterns:\n\n```\nFixes GH-1234\nFixes #1234\nFixes SENTRY-1234\nRefs LINEAR-ABC-123\n```\n\n- `Fixes` closes the issue when merged\n- `Refs` links without closing\n\n## Examples\n\n### Simple fix\n\n```\nfix(api): Handle null response in user endpoint\n\nThe user API could return null for deleted accounts, causing a crash\nin the dashboard. Add null check before accessing user properties.\n\nFixes SENTRY-5678\n```\n\n### Feature with scope\n\n```\nfeat(alerts): Add Slack thread replies for alert updates\n\nWhen an alert is updated or resolved, post a reply to the original\nSlack thread instead of creating a new message. This keeps related\nnotifications grouped together.\n\nRefs GH-1234\n```\n\n### Refactor\n\n```\nref: Extract common validation logic to shared module\n\nMove duplicate validation code from three endpoints into a shared\nvalidator class. No behavior change.\n```\n\n### Breaking change\n\n```\nfeat(api)!: Remove deprecated v1 endpoints\n\nRemove all v1 API endpoints that were deprecated in version 23.1.\nClients should migrate to v2 endpoints.\n\nBREAKING CHANGE: v1 endpoints no longer available\nFixes SENTRY-9999\n```\n\n## Revert Format\n\n```\nrevert: feat(api): Add new endpoint\n\nThis reverts commit abc123def456.\n\nReason: Caused performance regression in production.\n```\n\n## Principles\n\n- Each commit should be a single, stable change\n- Commits should be independently reviewable\n- The repository should be in a working state after each commit\n\n## References\n\n- [Sentry Commit Messages](https:\u002F\u002Fdevelop.sentry.dev\u002Fengineering-practices\u002Fcommit-messages\u002F)\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fsentry\u002Fcommit",3911,"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-11 21:38:31",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add davila7\u002Fclaude-code-templates --skill commit",{"tool":59,"command":60},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill commit",{"tool":62,"command":63},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsentry\u002Fcommit\u002FSKILL.md",true,[67,73,77],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"scripts\u002Fskill_manager.py","SCRIPT","脚本",13116,"https:\u002F\u002Fgithub.com\u002Finernoro\u002Fprd_agent\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmap-agent\u002Fscripts\u002Fskill_manager.py",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"scripts\u002Ftest_skill_manager.py",11074,"https:\u002F\u002Fgithub.com\u002Finernoro\u002Fprd_agent\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmap-agent\u002Fscripts\u002Ftest_skill_manager.py",{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"workbuddy.metadata.json","REFERENCE","参考文档",342,"https:\u002F\u002Fgithub.com\u002Finernoro\u002Fprd_agent\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmap-agent\u002Fworkbuddy.metadata.json",[84,113,139,172,207,231],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":95,"publishedAt":38},"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",[90],{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[96,97,98,99,100,101,102,103,29,19,104,22,105,106,107,108,109,110,111,112],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","reduce","record","track","verdict","evm","solana","how","public","look",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":120,"publishedAt":38},"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",[119],{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},[121,122,123,124,125,126,127,128,129,130,131,19,36,132,133,134,135,136,137,138],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","todo","work","plan","focus","signals","audit","dependency",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":154,"publishedAt":38},"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",[145,148,149],{"categoryNo":146,"categoryName":147,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},{"categoryNo":150,"categoryName":151,"taxonomyType":152,"taxonomyTypeDesc":153},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[155,156,157,158,159,160,161,101,162,163,164,165,166,167,168,29,169,170,19,171],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":176,"licenseFileUrl":177,"sourceHtmlUrl":178,"categories":179,"keywords":183,"publishedAt":38},"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",[180],{"categoryNo":181,"categoryName":182,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000009","前端开发",[184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,101,206],"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":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":176,"licenseFileUrl":211,"sourceHtmlUrl":212,"categories":213,"keywords":218,"publishedAt":38},"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",[214,217],{"categoryNo":215,"categoryName":216,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":181,"categoryName":182,"taxonomyType":93,"taxonomyTypeDesc":94},[219,220,221,222,223,185,224,194,195,225,226,227,228,101,229,22,230],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":232,"name":233,"nameZh":6,"description":234,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":176,"licenseFileUrl":235,"sourceHtmlUrl":236,"categories":237,"keywords":245,"publishedAt":38},"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",[238,241,242],{"categoryNo":239,"categoryName":240,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},{"categoryNo":243,"categoryName":244,"taxonomyType":152,"taxonomyTypeDesc":153},"01JBSEEDCAT000000000000036","内容创作者",[246,247,248,249,250,251,252,20,187,253,197,36,254,255,256,257,258,167,259,19,260,261,262,263,264,110,265],"discernment nudge","nudge","interpretation","help","run","reasoning","data","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]