[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF4FCZTHHJ0RHAPNRGRKX3":3,"skill-same:01M6AF4FCZTHHJ0RHAPNRGRKX3":68},{"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":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6AF4FCZTHHJ0RHAPNRGRKX3","abc-xyz-segmentation",null,"Segment a SKU portfolio on value (ABC) and demand variability (XYZ), produce the 9-box with a planning policy per cell, and reallocate planner attention accordingly. Use when the user mentions ABC analysis, inventory segmentation, SKU rationalization, stok segmentasyonu, envanter sınıflandırma, or asks which items deserve forecasting effort. Differentiator - ABC alone is treated as half an answer; policy lives in the value x variability combination.","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\u002Foperations\u002Fabc-xyz-segmentation\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"abc xyz segmentation","segmentation","use","when","value","which","answer","with","segment","as","attention","portfolio","policy","forecasting","planner","box","inventory","analysis","produce","planning","2026-11-10 10:12:30",false,"---\nname: abc-xyz-segmentation\ndescription: Segment a SKU portfolio on value (ABC) and demand variability (XYZ), produce the 9-box with a planning policy per cell, and reallocate planner attention accordingly. Use when the user mentions ABC analysis, inventory segmentation, SKU rationalization, stok segmentasyonu, envanter sınıflandırma, or asks which items deserve forecasting effort. Differentiator - ABC alone is treated as half an answer; policy lives in the value x variability combination.\n---\n\n# ABC-XYZ Segmentation\n\nValue tells you where the money is. Variability tells you whether forecasting, buffering or restructuring can work. Never output a classification without the policy consequences.\n\n## Required data\n\nPer-SKU demand history (`sku`, `period`, `qty`) covering 12+ periods, plus unit value (`unit_price` or cost). Without unit value, ABC degrades to a volume ranking - say so and ask for prices before presenting conclusions about money.\n\n## Workflow\n\n1. **ABC on annual value.** Rank by annual consumption value; cumulative 80% = A, next 15% = B, rest = C. Report the actual concentration found (e.g. \"15 SKUs = 80%\"), not the folklore 20\u002F80.\n2. **XYZ on variability.** CV = std\u002Fmean of period demand per SKU. Defaults: X \u003C 0.5, Y 0.5-1.0, Z >= 1.0. These are conventions - check the CV histogram for natural breaks and state the thresholds used. SKUs with structural zero periods (intermittent) belong in Z regardless of CV arithmetic; mean-based CV understates their risk.\n3. **Build the 9-box** with SKU counts AND value share per cell. Value share is what makes managers act.\n4. **Attach the policy per cell** (adapt wording to context):\n   - A-X: tight forecasting pays; low buffer, frequent review, automate replenishment\n   - A-Y: forecast + healthy buffer; investigate variability drivers\n   - A-Z: do not chase forecasts - strategic buffer, lead-time negotiation, or make-to-order\n   - B-X \u002F C-X: min-max autopilot; withdraw planner attention\n   - B-Z: buffer or longer promise dates; check if variability is self-inflicted (promotions, batching)\n   - C-Z: rationalization shortlist - kill, consolidate, or on-demand sourcing\n5. **Name the reallocation.** The deliverable is planner-hours and buffer money moving between cells - state explicitly which cells gain and lose attention.\n6. **Validate.** Sum of cell value shares must equal 100%; spot-check two SKUs' classifications against their raw series before presenting.\n\n## Pitfalls to check explicitly\n\n- ABC computed on quantity while unit values vary 10x+ ranks the wrong items.\n- Self-inflicted variability (order batching, month-end pushes, promotions) shows up as Z; flag it as a process fix, not a demand fact.\n- Classifications rot - recommend re-running quarterly and tracking cell migrations.\n- A dominant \"C-Z is 60% of SKUs\" finding usually signals assortment bloat, not a planning problem.\n\n## Output format\n\n1. The 9-box (counts + value share per cell)\n2. Policy table per occupied cell\n3. Attention-reallocation paragraph (from where, to where)\n4. Rationalization shortlist (top C-Z items by holding cost or shelf age, if data allows)\n\nWorked example including a safety-stock stress test: https:\u002F\u002Fgithub.com\u002Fgulmezeren2-byte\u002Fabc-xyz-inventory\n\n---\n\nSource: [industrial-engineering-ai-skills](https:\u002F\u002Fgithub.com\u002Fgulmezeren2-byte\u002Findustrial-engineering-ai-skills) by Eren Gulmez (MIT). The full method pack - entry skill, role agents, data-hygiene rules and artifact templates - lives there.\n","# ABC-XYZ Segmentation\n\nValue tells you where the money is. Variability tells you whether forecasting, buffering or restructuring can work. Never output a classification without the policy consequences.\n\n## Required data\n\nPer-SKU demand history (`sku`, `period`, `qty`) covering 12+ periods, plus unit value (`unit_price` or cost). Without unit value, ABC degrades to a volume ranking - say so and ask for prices before presenting conclusions about money.\n\n## Workflow\n\n1. **ABC on annual value.** Rank by annual consumption value; cumulative 80% = A, next 15% = B, rest = C. Report the actual concentration found (e.g. \"15 SKUs = 80%\"), not the folklore 20\u002F80.\n2. **XYZ on variability.** CV = std\u002Fmean of period demand per SKU. Defaults: X \u003C 0.5, Y 0.5-1.0, Z >= 1.0. These are conventions - check the CV histogram for natural breaks and state the thresholds used. SKUs with structural zero periods (intermittent) belong in Z regardless of CV arithmetic; mean-based CV understates their risk.\n3. **Build the 9-box** with SKU counts AND value share per cell. Value share is what makes managers act.\n4. **Attach the policy per cell** (adapt wording to context):\n   - A-X: tight forecasting pays; low buffer, frequent review, automate replenishment\n   - A-Y: forecast + healthy buffer; investigate variability drivers\n   - A-Z: do not chase forecasts - strategic buffer, lead-time negotiation, or make-to-order\n   - B-X \u002F C-X: min-max autopilot; withdraw planner attention\n   - B-Z: buffer or longer promise dates; check if variability is self-inflicted (promotions, batching)\n   - C-Z: rationalization shortlist - kill, consolidate, or on-demand sourcing\n5. **Name the reallocation.** The deliverable is planner-hours and buffer money moving between cells - state explicitly which cells gain and lose attention.\n6. **Validate.** Sum of cell value shares must equal 100%; spot-check two SKUs' classifications against their raw series before presenting.\n\n## Pitfalls to check explicitly\n\n- ABC computed on quantity while unit values vary 10x+ ranks the wrong items.\n- Self-inflicted variability (order batching, month-end pushes, promotions) shows up as Z; flag it as a process fix, not a demand fact.\n- Classifications rot - recommend re-running quarterly and tracking cell migrations.\n- A dominant \"C-Z is 60% of SKUs\" finding usually signals assortment bloat, not a planning problem.\n\n## Output format\n\n1. The 9-box (counts + value share per cell)\n2. Policy table per occupied cell\n3. Attention-reallocation paragraph (from where, to where)\n4. Rationalization shortlist (top C-Z items by holding cost or shelf age, if data allows)\n\nWorked example including a safety-stock stress test: https:\u002F\u002Fgithub.com\u002Fgulmezeren2-byte\u002Fabc-xyz-inventory\n\n---\n\nSource: [industrial-engineering-ai-skills](https:\u002F\u002Fgithub.com\u002Fgulmezeren2-byte\u002Findustrial-engineering-ai-skills) by Eren Gulmez (MIT). The full method pack - entry skill, role agents, data-hygiene rules and artifact templates - lives there.\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Foperations\u002Fabc-xyz-segmentation",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":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add davila7\u002Fclaude-code-templates --skill abc-xyz-segmentation",{"tool":60,"command":61},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill abc-xyz-segmentation",{"tool":63,"command":64},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill abc-xyz-segmentation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Foperations\u002Fabc-xyz-segmentation\u002FSKILL.md",true,[],[69,97,124,157,192,216],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":80,"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",[75],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[81,82,83,84,24,85,86,87,21,22,88,26,89,90,91,92,93,94,95,96],"scoring","pool","wealthville pool scoring","liquidity","for","exit","now","reduce","record","track","verdict","evm","solana","how","public","look",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":104,"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",[103],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},[105,106,107,108,109,110,111,112,113,114,115,22,116,117,118,119,120,121,122,123],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":139,"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",[130,133,134],{"categoryNo":131,"categoryName":132,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},{"categoryNo":135,"categoryName":136,"taxonomyType":137,"taxonomyTypeDesc":138},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[140,141,142,143,144,145,146,85,147,148,149,150,151,152,153,21,154,155,22,156],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":161,"licenseFileUrl":162,"sourceHtmlUrl":163,"categories":164,"keywords":168,"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",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000009","前端开发",[169,170,171,172,173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,85,191],"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":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":161,"licenseFileUrl":196,"sourceHtmlUrl":197,"categories":198,"keywords":203,"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",[199,202],{"categoryNo":200,"categoryName":201,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":166,"categoryName":167,"taxonomyType":78,"taxonomyTypeDesc":79},[204,205,206,207,208,170,209,179,180,210,211,212,213,85,214,26,215],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":161,"licenseFileUrl":220,"sourceHtmlUrl":221,"categories":222,"keywords":230,"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",[223,226,227],{"categoryNo":224,"categoryName":225,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},{"categoryNo":228,"categoryName":229,"taxonomyType":137,"taxonomyTypeDesc":138},"01JBSEEDCAT000000000000036","内容创作者",[231,232,233,234,235,236,237,238,172,239,182,116,240,241,242,243,244,152,245,22,246,36,247,248,249,94,250],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","claims","argument","assemble","recommendations"]