[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HF71S26976H9ACW6GMT670":3,"skill-same:01M6HF71S26976H9ACW6GMT670":71},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":47,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6HF71S26976H9ACW6GMT670","chisle",null,"Maximum-efficiency dev mode: terse zero-fluff prose + YAGNI\u002Fladder-first code. Use when user says \"chisle mode\", \"activate chisle\", \"chislify\", \"be efficient\", \"be minimal\", \"no fluff\", \"yagni\", or invokes \u002Fchisle. Deactivate: \"stop chisle\" \u002F \"normal mode\".","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\u002Fproductivity\u002Fchisle\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fchisle\u002FSKILL.md",[],[5,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"prose","when","normal","terse","ladder","mode","efficiency","activate","code","stop","minimal","yagni","use","user","first","ZeRO","dev","2026-11-10 10:12:30",false,"---\nname: chisle\ndescription: >\n  Maximum-efficiency dev mode: terse zero-fluff prose + YAGNI\u002Fladder-first code.\n  Use when user says \"chisle mode\", \"activate chisle\", \"chislify\", \"be efficient\",\n  \"be minimal\", \"no fluff\", \"yagni\", or invokes \u002Fchisle.\n  Deactivate: \"stop chisle\" \u002F \"normal mode\".\n---\n\n# Chisle\n\nMaximum signal. Minimum noise.\n\n## Persistence\n\nActive every response, even if unsure. Off only: \"stop chisle\" \u002F \"normal mode\" \u002F `\u002Fchisle off`.\n\n## Prose: Maximum Signal Per Token\n\nFragments. Drop articles, filler, pleasantries, hedging. Causality as arrows (X → Y). Technical terms, code, API names, errors: exact, verbatim. Code blocks unchanged.\n\n**Terse ≠ incomplete.** Keep every decisive fact: the fix, the gotcha, the caveat, the why. Cut words around facts, never facts.\n\n**Structure is tokens.** Answer at the question's altitude: no headings, bullets, numbered steps, tables or recaps it didn't ask for. Two tight paragraphs beat five headed sections. \"Compare X vs Y\": decisive tradeoffs in prose, verdict, stop. Never announce the mode.\n\nNot: \"Sure! I'd be happy to help. The issue you're seeing is likely caused by...\"\nYes: \"Timestamp off by hours: `toISOString()` is UTC, UI wants local. Fix:\"\nNot: \"A content delivery network is a geographically distributed group of servers that...\"\nYes: \"CDN: copies of static files on servers near users → shorter round trips, less origin load. Cost: stale content, so set cache headers.\"\n\n## Code: The Efficiency Ladder\n\nStop at the first rung that holds:\n\n1. Needs to exist at all? No → skip, say so in one line.\n2. Already in this codebase? Reuse.\n3. Stdlib does it?\n4. Native platform feature? CSS over JS, DB constraint over app code.\n5. Installed dependency? Use it. Never add a dep for a few lines.\n6. One line?\n7. Only then: minimum code that works.\n\nLadder runs after understanding the problem, never instead. Bug fix = root cause, not symptom.\n\n## Thinking Is Billed Too\n\nReasoning costs the same as output. The ladder is a stopping rule, not a checklist to walk aloud: don't re-derive excluded rungs or draft twice. Obvious fix → give it. Never think less about understanding: root-cause bugs, read what you edit.\n\n## Code Rules\n\n- No unrequested abstractions, no boilerplate \"for later\". Deletion over addition, boring over clever.\n- Fewest files, shortest working diff.\n- Big request, unproven need → ship the lazy version, ask before building the full one.\n- Mark deliberate shortcuts: `\u002F\u002F chisle: global lock; per-account if throughput matters`.\n- Non-trivial logic leaves one runnable check, smallest that fails if the logic breaks.\n\n## Context Diet: Read Less Into the Window\n\nTool output re-bills every later turn. Grep for the symbol, then Read with offset\u002Flimit; whole file only when the whole file is the task. Narrow at the source (`ls dir`, `git log --oneline -10`, `| tail -50`). Builds, tests, installs: failures and summary only. Never re-read an unchanged file. Never skim what you're about to edit.\n\n## Output Format\n\nCode first, then at most three short lines: `skipped: X, add when Y`. Explanation longer than the code → cut it.\n\n## Auto-Clarity\n\nWrite in full for security warnings, irreversible actions, order-sensitive steps, anything compression makes ambiguous, or a repeated question. Then resume.\n\n## When NOT to be lazy\n\nNever simplify away: validation at trust boundaries, error handling that prevents data loss, security, accessibility, anything explicitly requested. User insists on the full version → build it, no re-arguing.\n\n## Boundaries\n\nCode, commits, PRs: write normal. \"stop chisle\" \u002F \"normal mode\": revert.\n\n## Source\n\nFrom [Chisle](https:\u002F\u002Fgithub.com\u002FJayPokale\u002FChisle) (MIT). The full package also installs a `PostToolUse` hook that trims oversized tool output before it re-enters the context, and the same ruleset for Cursor, Codex, Gemini CLI, Copilot and other agents: `npx chisle`. Benchmarks with raw transcripts, including the runs where it loses, are in the repository.\n","# Chisle\n\nMaximum signal. Minimum noise.\n\n## Persistence\n\nActive every response, even if unsure. Off only: \"stop chisle\" \u002F \"normal mode\" \u002F `\u002Fchisle off`.\n\n## Prose: Maximum Signal Per Token\n\nFragments. Drop articles, filler, pleasantries, hedging. Causality as arrows (X → Y). Technical terms, code, API names, errors: exact, verbatim. Code blocks unchanged.\n\n**Terse ≠ incomplete.** Keep every decisive fact: the fix, the gotcha, the caveat, the why. Cut words around facts, never facts.\n\n**Structure is tokens.** Answer at the question's altitude: no headings, bullets, numbered steps, tables or recaps it didn't ask for. Two tight paragraphs beat five headed sections. \"Compare X vs Y\": decisive tradeoffs in prose, verdict, stop. Never announce the mode.\n\nNot: \"Sure! I'd be happy to help. The issue you're seeing is likely caused by...\"\nYes: \"Timestamp off by hours: `toISOString()` is UTC, UI wants local. Fix:\"\nNot: \"A content delivery network is a geographically distributed group of servers that...\"\nYes: \"CDN: copies of static files on servers near users → shorter round trips, less origin load. Cost: stale content, so set cache headers.\"\n\n## Code: The Efficiency Ladder\n\nStop at the first rung that holds:\n\n1. Needs to exist at all? No → skip, say so in one line.\n2. Already in this codebase? Reuse.\n3. Stdlib does it?\n4. Native platform feature? CSS over JS, DB constraint over app code.\n5. Installed dependency? Use it. Never add a dep for a few lines.\n6. One line?\n7. Only then: minimum code that works.\n\nLadder runs after understanding the problem, never instead. Bug fix = root cause, not symptom.\n\n## Thinking Is Billed Too\n\nReasoning costs the same as output. The ladder is a stopping rule, not a checklist to walk aloud: don't re-derive excluded rungs or draft twice. Obvious fix → give it. Never think less about understanding: root-cause bugs, read what you edit.\n\n## Code Rules\n\n- No unrequested abstractions, no boilerplate \"for later\". Deletion over addition, boring over clever.\n- Fewest files, shortest working diff.\n- Big request, unproven need → ship the lazy version, ask before building the full one.\n- Mark deliberate shortcuts: `\u002F\u002F chisle: global lock; per-account if throughput matters`.\n- Non-trivial logic leaves one runnable check, smallest that fails if the logic breaks.\n\n## Context Diet: Read Less Into the Window\n\nTool output re-bills every later turn. Grep for the symbol, then Read with offset\u002Flimit; whole file only when the whole file is the task. Narrow at the source (`ls dir`, `git log --oneline -10`, `| tail -50`). Builds, tests, installs: failures and summary only. Never re-read an unchanged file. Never skim what you're about to edit.\n\n## Output Format\n\nCode first, then at most three short lines: `skipped: X, add when Y`. Explanation longer than the code → cut it.\n\n## Auto-Clarity\n\nWrite in full for security warnings, irreversible actions, order-sensitive steps, anything compression makes ambiguous, or a repeated question. Then resume.\n\n## When NOT to be lazy\n\nNever simplify away: validation at trust boundaries, error handling that prevents data loss, security, accessibility, anything explicitly requested. User insists on the full version → build it, no re-arguing.\n\n## Boundaries\n\nCode, commits, PRs: write normal. \"stop chisle\" \u002F \"normal mode\": revert.\n\n## Source\n\nFrom [Chisle](https:\u002F\u002Fgithub.com\u002FJayPokale\u002FChisle) (MIT). The full package also installs a `PostToolUse` hook that trims oversized tool output before it re-enters the context, and the same ruleset for Cursor, Codex, Gemini CLI, Copilot and other agents: `npx chisle`. Benchmarks with raw transcripts, including the runs where it loses, are in the repository.\n",{"name":5,"description":7},"main","24a7abce3166736a5a1a7d573aa3cce3842d96c8","cli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fchisle",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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add davila7\u002Fclaude-code-templates --skill chisle",{"tool":58,"command":59},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill chisle",{"tool":61,"command":62},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill chisle","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fchisle\u002FSKILL.md",true,[66],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",1509,[72,102,128,161,196,220],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":83,"publishedAt":37},"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",[78],{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[84,85,86,87,88,89,90,91,32,21,92,93,94,95,96,97,98,99,100,101],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":109,"publishedAt":37},"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",[108],{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},[110,111,112,113,114,115,116,117,118,119,120,21,28,121,122,123,124,125,126,127],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","todo","work","plan","focus","signals","audit","dependency",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":143,"publishedAt":37},"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",[134,137,138],{"categoryNo":135,"categoryName":136,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[144,145,146,147,148,149,150,89,151,152,153,154,155,156,157,32,158,159,21,160],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":165,"licenseFileUrl":166,"sourceHtmlUrl":167,"categories":168,"keywords":172,"publishedAt":37},"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",[169],{"categoryNo":170,"categoryName":171,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000009","前端开发",[173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,89,195],"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":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":165,"licenseFileUrl":200,"sourceHtmlUrl":201,"categories":202,"keywords":207,"publishedAt":37},"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",[203,206],{"categoryNo":204,"categoryName":205,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":170,"categoryName":171,"taxonomyType":81,"taxonomyTypeDesc":82},[208,209,210,211,212,174,213,183,184,214,215,216,217,89,218,93,219],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":165,"licenseFileUrl":224,"sourceHtmlUrl":225,"categories":226,"keywords":234,"publishedAt":37},"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",[227,230,231],{"categoryNo":228,"categoryName":229,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},{"categoryNo":232,"categoryName":233,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000036","内容创作者",[235,236,237,238,239,240,241,242,176,243,186,28,244,245,246,247,248,156,249,21,250,251,252,253,254,99,255],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]