[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72BBCRRF502147HANAQM4ST":3,"skill-same:01M72BBCRRF502147HANAQM4ST":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M72BBCRRF502147HANAQM4ST","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.","Sansar35\u002Fclaude-agent","Sansar35","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145020281?v=4","01M724CQ2SCC86MGNSD87D0D4K","01M724CQ3965G9WJ3QXE3AJ5YY",1,"MIT","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fdeadline-prep\u002FSKILL.md",[],[],"2026-11-10 18:39:20",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","d046d088ce5a79a083f0abc0fe1b7ded73bc5b1f","claude-config\u002Fskills\u002Fdeadline-prep","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent","https:\u002F\u002Fgithub.com\u002FSansar35","2026-05-10 16:04:53",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add Sansar35\u002Fclaude-agent --skill deadline-prep",{"tool":35,"command":36},"bunx","bunx skills add Sansar35\u002Fclaude-agent --skill deadline-prep",{"tool":38,"command":39},"pnpm","pnpm dlx skills add Sansar35\u002Fclaude-agent --skill deadline-prep","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fdeadline-prep\u002FSKILL.md",true,[43],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},".skill-source.json","REFERENCE","参考文档",465,"https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fdeadline-prep\u002F.skill-source.json",[50,57,64,71,78,86],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M72DVAN1JYEA302MT0C5MGD6","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M72DV8J5NBRRM4RPDFRV95N7","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M72DV5EMHW0BHP9BZ167MDCB","zinc-database","Access ZINC (230M+ purchasable compounds). Search by ZINC ID\u002FSMILES, similarity searches, 3D-ready structures for docking, analog discovery, for virtual screening and drug discovery.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzinc-database\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M72DV216QY0E693ZPEVQ0DBS","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M72DTXQREMCRKA8NHCVKHN4W","zapier-workflows","Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to \"run\" any process. Also handles Perplexity-based research and Google Sheets data tracking.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M72DTT17TBSJ0Y8J2XZ4C9TZ","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[]]