[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF5Z2Z2HD4ME5T2KDR640E":3,"skill-same:01M6AF5Z2Z2HD4ME5T2KDR640E":69},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6AF5Z2Z2HD4ME5T2KDR640E","deadline-prep",null,"Generate a structured demo outline from your session's change log and git history. Reads .claude\u002Fcritical_log_changes.csv and git log to produce presentation-ready talking points for end-of-day demos, standups, or delivery deadlines.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33286,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdeadline-prep\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"prep","deadline prep","ready","demo outline","changes","for","critical","end","outline","delivery","git log","log","change","session","history","csv","demo","produce","git","generate","change log","2026-11-10 10:12:30",false,"---\nname: deadline-prep\ndescription: Generate a structured demo outline from your session's change log and git history. Reads .claude\u002Fcritical_log_changes.csv and git log to produce presentation-ready talking points for end-of-day demos, standups, or delivery deadlines.\n---\n\n# Deadline Prep\n\nGenerate a structured demo outline from your work session. Combines the change log CSV (from the change-logger hook) with git history to create presentation-ready talking points.\n\n## Workflow\n\n### Step 1: Gather data sources\n\n**Change log** (primary source if available):\n- Read `.claude\u002Fcritical_log_changes.csv` if it exists\n- Parse columns: timestamp, tool, file_path, action, details\n- Group by: files created, files modified, commands executed\n\n**Git history** (always available):\n```bash\ngit log --oneline --since=\"today 00:00\"\ngit diff --stat HEAD~10 2>\u002Fdev\u002Fnull || git diff --stat\n```\n\nIf the CSV doesn't exist, fall back to git-only mode and note this in the output.\n\n### Step 2: Analyze and categorize changes\n\nGroup all changes into categories:\n\n| Category | Signals |\n|----------|---------|\n| **Features shipped** | New files, new routes, new components, `feat` commits |\n| **Bug fixes** | Modified files with `fix` commits, error handling changes |\n| **Refactors** | Renamed files, structural changes, `refactor` commits |\n| **Config\u002FSetup** | package.json, tsconfig, CI\u002FCD, Docker changes |\n| **Tests** | Test files created or modified |\n| **Documentation** | README, docs, comments |\n\n### Step 3: Generate the demo outline\n\nCreate a structured markdown document:\n\n```markdown\n# Demo Outline — [Date]\n\n## What I Shipped\n- **[Feature\u002FFix name]**: One sentence explaining what it does and why it matters\n- **[Feature\u002FFix name]**: One sentence explaining what it does and why it matters\n- **[Feature\u002FFix name]**: One sentence explaining what it does and why it matters\n\n## Architecture Decisions\n- **[Decision]**: Why I chose this approach over alternatives\n- **[Decision]**: Tradeoff I made and the reasoning\n\n## What I Would Do Next\n1. **[Priority 1]**: Why this is the most important next step\n2. **[Priority 2]**: What this would unlock\n3. **[Priority 3]**: Nice-to-have improvement\n\n## Session Metrics\n- Files changed: X\n- Lines: +Y \u002F -Z\n- Commits: N\n- Key files: `path\u002Fto\u002Fimportant\u002Ffile.ts`, `path\u002Fto\u002Fother.ts`\n- Time window: HH:MM - HH:MM\n```\n\n### Step 4: Save and present\n\nSave the outline to `.claude\u002Fdemo-outline.md`.\n\nPrint the full outline to the terminal so the user can review it immediately.\n\n## Tips\n\n- Run this 30 minutes before your deadline to have time to review and add personal context\n- The \"Architecture Decisions\" section is what reviewers care about most — add context about tradeoffs\n- \"What I Would Do Next\" shows you think beyond the immediate task\n- Edit the generated outline to add your own voice and any context the log missed\n- Works best with the `change-logger` hook installed, but functions with git history alone\n","# Deadline Prep\n\nGenerate a structured demo outline from your work session. Combines the change log CSV (from the change-logger hook) with git history to create presentation-ready talking points.\n\n## Workflow\n\n### Step 1: Gather data sources\n\n**Change log** (primary source if available):\n- Read `.claude\u002Fcritical_log_changes.csv` if it exists\n- Parse columns: timestamp, tool, file_path, action, details\n- Group by: files created, files modified, commands executed\n\n**Git history** (always available):\n```bash\ngit log --oneline --since=\"today 00:00\"\ngit diff --stat HEAD~10 2>\u002Fdev\u002Fnull || git diff --stat\n```\n\nIf the CSV doesn't exist, fall back to git-only mode and note this in the output.\n\n### Step 2: Analyze and categorize changes\n\nGroup all changes into categories:\n\n| Category | Signals |\n|----------|---------|\n| **Features shipped** | New files, new routes, new components, `feat` commits |\n| **Bug fixes** | Modified files with `fix` commits, error handling changes |\n| **Refactors** | Renamed files, structural changes, `refactor` commits |\n| **Config\u002FSetup** | package.json, tsconfig, CI\u002FCD, Docker changes |\n| **Tests** | Test files created or modified |\n| **Documentation** | README, docs, comments |\n\n### Step 3: Generate the demo outline\n\nCreate a structured markdown document:\n\n```markdown\n# Demo Outline — [Date]\n\n## What I Shipped\n- **[Feature\u002FFix name]**: One sentence explaining what it does and why it matters\n- **[Feature\u002FFix name]**: One sentence explaining what it does and why it matters\n- **[Feature\u002FFix name]**: One sentence explaining what it does and why it matters\n\n## Architecture Decisions\n- **[Decision]**: Why I chose this approach over alternatives\n- **[Decision]**: Tradeoff I made and the reasoning\n\n## What I Would Do Next\n1. **[Priority 1]**: Why this is the most important next step\n2. **[Priority 2]**: What this would unlock\n3. **[Priority 3]**: Nice-to-have improvement\n\n## Session Metrics\n- Files changed: X\n- Lines: +Y \u002F -Z\n- Commits: N\n- Key files: `path\u002Fto\u002Fimportant\u002Ffile.ts`, `path\u002Fto\u002Fother.ts`\n- Time window: HH:MM - HH:MM\n```\n\n### Step 4: Save and present\n\nSave the outline to `.claude\u002Fdemo-outline.md`.\n\nPrint the full outline to the terminal so the user can review it immediately.\n\n## Tips\n\n- Run this 30 minutes before your deadline to have time to review and add personal context\n- The \"Architecture Decisions\" section is what reviewers care about most — add context about tradeoffs\n- \"What I Would Do Next\" shows you think beyond the immediate task\n- Edit the generated outline to add your own voice and any context the log missed\n- Works best with the `change-logger` hook installed, but functions with git history alone\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdeadline-prep",3909,"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 11:53:30",{"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 deadline-prep",{"tool":61,"command":62},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill deadline-prep",{"tool":64,"command":65},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill deadline-prep","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdeadline-prep\u002FSKILL.md",true,[],[70,101,128,161,196,220],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":81,"publishedAt":40},"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",[76],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[82,83,84,85,86,24,87,88,89,90,91,92,93,94,95,96,97,98,99,100],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","use","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":108,"publishedAt":40},"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",[107],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[109,110,111,112,113,114,115,116,117,118,119,90,120,121,122,123,124,125,126,127],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","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":40},"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":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[144,145,146,147,148,149,150,24,151,152,153,154,155,156,157,89,158,159,90,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":40},"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":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000009","前端开发",[173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,24,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":40},"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":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":170,"categoryName":171,"taxonomyType":79,"taxonomyTypeDesc":80},[208,209,210,211,212,174,213,183,184,214,215,216,217,24,218,92,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":40},"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":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},{"categoryNo":232,"categoryName":233,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000036","内容创作者",[235,236,237,238,239,240,241,242,176,243,186,120,244,245,246,247,248,156,249,90,250,251,252,253,254,98,255],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]