[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEWVQYJ8TSQBV4PFR5FVPT":3,"skill-same:01M6AEWVQYJ8TSQBV4PFR5FVPT":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":23,"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},"01M6AEWVQYJ8TSQBV4PFR5FVPT","test-detect",null,"Auto-detect testing framework and run relevant tests. Identifies Jest, Vitest, Playwright, Cypress, pytest, Go test, and others. Can run all tests, specific file tests, or generate basic tests for new code. Usage - \u002Ftest-detect, \u002Ftest-detect src\u002Fauth\u002Flogin.ts, \u002Ftest-detect generate src\u002Futils.ts","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\u002Fdevelopment\u002Ftest-detect\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"test","detect","test detect","vitest","new","auto-detect","for","utils","can","usage","relevant","basic","tests","jest","auto","testing","file","testing framework","framework","code","run","generate","auth","playwright","go","2026-11-10 10:12:30",false,"---\nname: test-detect\ndescription: Auto-detect testing framework and run relevant tests. Identifies Jest, Vitest, Playwright, Cypress, pytest, Go test, and others. Can run all tests, specific file tests, or generate basic tests for new code. Usage - \u002Ftest-detect, \u002Ftest-detect src\u002Fauth\u002Flogin.ts, \u002Ftest-detect generate src\u002Futils.ts\n---\n\n# Test Detect\n\nAutomatically detect the testing framework in the current project and run the right tests.\n\n## Workflow\n\n### Step 1: Detect the testing framework\n\nCheck for these files in order (first match wins):\n\n| Check | Framework | Run Command |\n|-------|-----------|-------------|\n| `vitest.config.*` exists OR `vitest` in devDeps | **Vitest** | `npx vitest run` |\n| `jest.config.*` exists OR `jest` in devDeps | **Jest** | `npx jest` |\n| `playwright.config.*` exists | **Playwright** | `npx playwright test` |\n| `cypress.config.*` exists | **Cypress** | `npx cypress run` |\n| `pytest.ini` or `conftest.py` or `pyproject.toml` with `[tool.pytest]` | **pytest** | `python -m pytest` |\n| `go.mod` exists | **Go test** | `go test .\u002F...` |\n| `Cargo.toml` exists | **Rust\u002Fcargo** | `cargo test` |\n| `mix.exs` exists | **ExUnit** | `mix test` |\n| `Gemfile` with `rspec` | **RSpec** | `bundle exec rspec` |\n| `package.json` has `scripts.test` | **npm test** | `npm test` |\n\nReport the detected framework before proceeding.\n\n### Step 2: Parse arguments\n\nCheck `$ARGUMENTS` for the mode:\n\n- **No arguments** or **\"all\"**: Run the full test suite (Step 3)\n- **File path** (e.g., `src\u002Fauth\u002Flogin.ts`): Run tests for that file (Step 4)\n- **\"generate\" + file path** (e.g., `generate src\u002Futils.ts`): Generate tests (Step 5)\n\n### Step 3: Run full test suite\n\nRun the detected test command. After completion:\n\n- Report total tests, passed, failed, skipped\n- If tests fail, show the first 3 failure messages with file:line references\n- Suggest: \"Run `\u002Ftest-detect \u003Cfailing-file>` to investigate a specific failure\"\n\n### Step 4: Run tests for a specific file\n\nGiven a source file path, find its test file:\n\n**Search strategy** (try in order):\n1. `__tests__\u002F\u003Cfilename>.test.\u003Cext>` (Jest convention)\n2. `\u003Cfilename>.test.\u003Cext>` (co-located)\n3. `\u003Cfilename>.spec.\u003Cext>` (alternative convention)\n4. `test\u002F\u003Cfilename>_test.\u003Cext>` (Go\u002FPython convention)\n5. `tests\u002Ftest_\u003Cfilename>.\u003Cext>` (pytest convention)\n6. `\u003Cfilename>_test.go` (Go convention)\n\nUse Glob to find matches. If found, run only that test file:\n\n| Framework | Command |\n|-----------|---------|\n| Vitest | `npx vitest run \u003Ctest-file>` |\n| Jest | `npx jest \u003Ctest-file>` |\n| Playwright | `npx playwright test \u003Ctest-file>` |\n| pytest | `python -m pytest \u003Ctest-file>` |\n| Go | `go test -run \u003CTestName> .\u002F\u003Cpackage>\u002F` |\n| Cargo | `cargo test \u003Ctest_name>` |\n\nIf no test file found, ask: \"No tests found for this file. Want me to generate them? Run `\u002Ftest-detect generate \u003Cfile>`\"\n\n### Step 5: Generate tests\n\nRead the source file and analyze:\n1. Identify all exported functions\u002Fclasses\u002Fcomponents\n2. Determine the appropriate test patterns for the framework\n3. Generate a test file with:\n   - Import statements\n   - `describe` block per function\u002Fclass\n   - `it`\u002F`test` blocks covering: happy path, edge cases, error cases\n   - Framework-appropriate assertions and mocking\n\n**Save to the conventional location** for the detected framework:\n- Jest\u002FVitest: `__tests__\u002F\u003Cfilename>.test.\u003Cext>` or `\u003Cfilename>.test.\u003Cext>` (match existing convention)\n- pytest: `tests\u002Ftest_\u003Cfilename>.py`\n- Go: `\u003Cfilename>_test.go` (same directory)\n- RSpec: `spec\u002F\u003Cfilename>_spec.rb`\n\nShow the generated file path and ask if the user wants to run the new tests.\n\n## Tips\n\n- If multiple frameworks are detected (e.g., Vitest for unit tests + Playwright for e2e), mention both and default to the unit test framework\n- For monorepos, detect from the closest config file to the current directory\n- If `package.json` has both `test` and `test:unit`\u002F`test:e2e` scripts, prefer the specific one when context is clear\n","# Test Detect\n\nAutomatically detect the testing framework in the current project and run the right tests.\n\n## Workflow\n\n### Step 1: Detect the testing framework\n\nCheck for these files in order (first match wins):\n\n| Check | Framework | Run Command |\n|-------|-----------|-------------|\n| `vitest.config.*` exists OR `vitest` in devDeps | **Vitest** | `npx vitest run` |\n| `jest.config.*` exists OR `jest` in devDeps | **Jest** | `npx jest` |\n| `playwright.config.*` exists | **Playwright** | `npx playwright test` |\n| `cypress.config.*` exists | **Cypress** | `npx cypress run` |\n| `pytest.ini` or `conftest.py` or `pyproject.toml` with `[tool.pytest]` | **pytest** | `python -m pytest` |\n| `go.mod` exists | **Go test** | `go test .\u002F...` |\n| `Cargo.toml` exists | **Rust\u002Fcargo** | `cargo test` |\n| `mix.exs` exists | **ExUnit** | `mix test` |\n| `Gemfile` with `rspec` | **RSpec** | `bundle exec rspec` |\n| `package.json` has `scripts.test` | **npm test** | `npm test` |\n\nReport the detected framework before proceeding.\n\n### Step 2: Parse arguments\n\nCheck `$ARGUMENTS` for the mode:\n\n- **No arguments** or **\"all\"**: Run the full test suite (Step 3)\n- **File path** (e.g., `src\u002Fauth\u002Flogin.ts`): Run tests for that file (Step 4)\n- **\"generate\" + file path** (e.g., `generate src\u002Futils.ts`): Generate tests (Step 5)\n\n### Step 3: Run full test suite\n\nRun the detected test command. After completion:\n\n- Report total tests, passed, failed, skipped\n- If tests fail, show the first 3 failure messages with file:line references\n- Suggest: \"Run `\u002Ftest-detect \u003Cfailing-file>` to investigate a specific failure\"\n\n### Step 4: Run tests for a specific file\n\nGiven a source file path, find its test file:\n\n**Search strategy** (try in order):\n1. `__tests__\u002F\u003Cfilename>.test.\u003Cext>` (Jest convention)\n2. `\u003Cfilename>.test.\u003Cext>` (co-located)\n3. `\u003Cfilename>.spec.\u003Cext>` (alternative convention)\n4. `test\u002F\u003Cfilename>_test.\u003Cext>` (Go\u002FPython convention)\n5. `tests\u002Ftest_\u003Cfilename>.\u003Cext>` (pytest convention)\n6. `\u003Cfilename>_test.go` (Go convention)\n\nUse Glob to find matches. If found, run only that test file:\n\n| Framework | Command |\n|-----------|---------|\n| Vitest | `npx vitest run \u003Ctest-file>` |\n| Jest | `npx jest \u003Ctest-file>` |\n| Playwright | `npx playwright test \u003Ctest-file>` |\n| pytest | `python -m pytest \u003Ctest-file>` |\n| Go | `go test -run \u003CTestName> .\u002F\u003Cpackage>\u002F` |\n| Cargo | `cargo test \u003Ctest_name>` |\n\nIf no test file found, ask: \"No tests found for this file. Want me to generate them? Run `\u002Ftest-detect generate \u003Cfile>`\"\n\n### Step 5: Generate tests\n\nRead the source file and analyze:\n1. Identify all exported functions\u002Fclasses\u002Fcomponents\n2. Determine the appropriate test patterns for the framework\n3. Generate a test file with:\n   - Import statements\n   - `describe` block per function\u002Fclass\n   - `it`\u002F`test` blocks covering: happy path, edge cases, error cases\n   - Framework-appropriate assertions and mocking\n\n**Save to the conventional location** for the detected framework:\n- Jest\u002FVitest: `__tests__\u002F\u003Cfilename>.test.\u003Cext>` or `\u003Cfilename>.test.\u003Cext>` (match existing convention)\n- pytest: `tests\u002Ftest_\u003Cfilename>.py`\n- Go: `\u003Cfilename>_test.go` (same directory)\n- RSpec: `spec\u002F\u003Cfilename>_spec.rb`\n\nShow the generated file path and ask if the user wants to run the new tests.\n\n## Tips\n\n- If multiple frameworks are detected (e.g., Vitest for unit tests + Playwright for e2e), mention both and default to the unit test framework\n- For monorepos, detect from the closest config file to the current directory\n- If `package.json` has both `test` and `test:unit`\u002F`test:e2e` scripts, prefer the specific one when context is clear\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftest-detect",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 test-detect",{"tool":70,"command":71},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill test-detect",{"tool":73,"command":74},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill test-detect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftest-detect\u002FSKILL.md",true,[],[79,108,134,167,201,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":88,"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":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[89,90,91,92,93,30,94,95,96,97,98,99,100,101,102,103,104,105,106,107],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","use","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":115,"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",[114],{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},[116,117,118,119,120,121,122,123,124,125,126,97,43,127,128,129,130,131,132,133],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","todo","work","plan","focus","signals","audit","dependency",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":149,"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",[140,143,144],{"categoryNo":141,"categoryName":142,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":145,"categoryName":146,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[150,151,152,153,154,155,156,30,157,158,159,160,161,162,163,96,164,165,97,166],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":171,"licenseFileUrl":172,"sourceHtmlUrl":173,"categories":174,"keywords":178,"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",[175],{"categoryNo":176,"categoryName":177,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[179,180,181,182,183,184,185,186,187,188,189,190,191,40,192,193,194,195,196,197,198,199,30,200],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":171,"licenseFileUrl":205,"sourceHtmlUrl":206,"categories":207,"keywords":210,"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",[208,209],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":176,"categoryName":177,"taxonomyType":21,"taxonomyTypeDesc":22},[211,39,212,213,47,180,214,189,190,215,216,217,218,30,219,99,220],"webapp testing","webapp","browser","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":171,"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":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":233,"categoryName":234,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000036","内容创作者",[236,237,238,239,44,240,241,242,182,243,40,43,244,245,246,247,248,162,249,97,250,251,252,253,254,105,255],"discernment nudge","nudge","interpretation","help","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]