[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79X41VE8VCP1GQCK7SFSGSH":3,"skill-same:01M79X41VE8VCP1GQCK7SFSGSH":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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},"01M79X41VE8VCP1GQCK7SFSGSH","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.","KrismithReddy12\u002Fclaude-code-templates","KrismithReddy12","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F182916557?v=4","01M79T8DNGJRHG48G3H3Q02MK8","01M79TA8ZWV2PP7R4ARWVYWZFE",0,"MIT","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdeadline-prep\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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","e3744adb7654df443f12927f3e001252b3a26b6d","cli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdeadline-prep","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates","https:\u002F\u002Fgithub.com\u002FKrismithReddy12","2026-07-29 08:15:10",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add KrismithReddy12\u002Fclaude-code-templates --skill deadline-prep",{"tool":35,"command":36},"bunx","bunx skills add KrismithReddy12\u002Fclaude-code-templates --skill deadline-prep",{"tool":38,"command":39},"pnpm","pnpm dlx skills add KrismithReddy12\u002Fclaude-code-templates --skill deadline-prep","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdeadline-prep\u002FSKILL.md",true,[],[44,51,60,67,74,81],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M79YMXJ07S2BQVB7JAM3657Q","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\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":55,"licenseFileUrl":56,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M79YMVPMK3Y4JDP2KDJKQ2ZD","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M79YMMQ4XXMPJHDQHY8FR7ME","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M79YMHQY3CP1XXMQ00TGQFAW","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M79YME4Z3DRW0MT6BNYW1D7P","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M79YMAX7NFYDFXFZH2TJS7SS","planning-with-files","Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[],[]]