[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75NVPD2CK4NHW48BA85C1JB":3,"skill-same:01M75NVPD2CK4NHW48BA85C1JB":48},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M75NVPD2CK4NHW48BA85C1JB","todo",null,"Manage project todos in todos.md file.","Kushal9889\u002Fclaude-plugins","Kushal9889","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F234108364?v=4","01M75N3MJASY98ADCZ0RNAC66K","Kushal Gaddamwar","01M75N3MK1VKFXDPK7H6DV9Y2Z",2,"MIT","https:\u002F\u002Fgithub.com\u002FKushal9889\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Ftools\u002Fskills\u002Fawesome-claude-code\u002Ftodo\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: todo\ndescription: \"Manage project todos in todos.md file.\"\norigin: awesome-claude-code\n---\n\n---\nname: todo\ndescription: Manage project todos in todos.md file\n---\n\n# Project Todo Manager\n\nManage todos in a `todos.md` file at the root of your current project directory.\n\n## Usage Examples:\n- `\u002Fuser:todo add \"Fix navigation bug\"`\n- `\u002Fuser:todo add \"Fix navigation bug\" [date\u002Ftime\u002F\"tomorrow\"\u002F\"next week\"]` an optional 2nd parameter to set a due date\n- `\u002Fuser:todo complete 1` \n- `\u002Fuser:todo remove 2`\n- `\u002Fuser:todo list`\n- `\u002Fuser:todo undo 1`\n\n## Instructions:\n\nYou are a todo manager for the current project. When this command is invoked:\n\n1. **Determine the project root** by looking for common indicators (.git, package.json, etc.)\n2. **Locate or create** `todos.md` in the project root\n3. **Parse the command arguments** to determine the action:\n   - `add \"task description\"` - Add a new todo\n   - `add \"task description\" [tomorrow|next week|4 days|June 9|12-24-2025|etc...]` - Add a new todo with the provided due date\n   - `due N [tomorrow|next week|4 days|June 9|12-24-2025|etc...]` - Mark todo N with the due date provided\n   - `complete N` - Mark todo N as completed and move from the ##Active list to the ##Completed list\n   - `remove N` - Remove todo N entirely\n   - `undo N` - Mark completed todo N as incomplete\n   - `list [N]` or no args - Show all (or N number of) todos in a user-friendly format, with each todo numbered for reference\n   - `past due` - Show all of the tasks which are past due and still active\n   - `next` - Shows the next active task in the list, this should respect Due dates, if there are any. If not, just show the first todo in the Active list\n\n## Todo Format:\nUse this markdown format in todos.md:\n```markdown\n# Project Todos\n\n## Active\n- [ ] Task description here | Due: MM-DD-YYYY (conditionally include HH:MM AM\u002FPM, if specified)\n- [ ] Another task \n\n## Completed  \n- [x] Finished task | Done: MM-DD-YYYY (conditionally include HH:MM AM\u002FPM, if specified) \n- [x] Another completed task | Due: MM-DD-YYYY (conditionally include HH:MM AM\u002FPM, if specified) | Done: MM-DD-YYYY (conditionally include HH:MM AM\u002FPM, if specified) \n```\n\n## Behavior:\n- Number todos when displaying (1, 2, 3...)\n- Keep completed todos in a separate section\n- Todos do not need to have Due Dates\u002FTimes\n- Keep the Active list sorted descending by Due Date, if there are any; though in a list with mixed tasks with and without Due Dates, those with Due Dates should come before those without Due Dates\n- If todos.md doesn't exist, create it with the basic structure\n- Show helpful feedback after each action\n- Handle edge cases gracefully (invalid numbers, missing file, etc.)\n- All provided dates\u002Ftimes should be saved\u002Fformatted in a standardized format of MM\u002FDD\u002FYYYY (or DD\u002FMM\u002FYYYY depending on locale), unless the user specifies a different format\n- Times should not be included in the due date format unless requested (`due N in 2 hours` should be MM\u002FDD\u002FYYYY @ [+ 2 hours from now]) \n\nAlways be concise and helpful in your responses.\n\n","---\nname: todo\ndescription: Manage project todos in todos.md file\n---\n\n# Project Todo Manager\n\nManage todos in a `todos.md` file at the root of your current project directory.\n\n## Usage Examples:\n- `\u002Fuser:todo add \"Fix navigation bug\"`\n- `\u002Fuser:todo add \"Fix navigation bug\" [date\u002Ftime\u002F\"tomorrow\"\u002F\"next week\"]` an optional 2nd parameter to set a due date\n- `\u002Fuser:todo complete 1` \n- `\u002Fuser:todo remove 2`\n- `\u002Fuser:todo list`\n- `\u002Fuser:todo undo 1`\n\n## Instructions:\n\nYou are a todo manager for the current project. When this command is invoked:\n\n1. **Determine the project root** by looking for common indicators (.git, package.json, etc.)\n2. **Locate or create** `todos.md` in the project root\n3. **Parse the command arguments** to determine the action:\n   - `add \"task description\"` - Add a new todo\n   - `add \"task description\" [tomorrow|next week|4 days|June 9|12-24-2025|etc...]` - Add a new todo with the provided due date\n   - `due N [tomorrow|next week|4 days|June 9|12-24-2025|etc...]` - Mark todo N with the due date provided\n   - `complete N` - Mark todo N as completed and move from the ##Active list to the ##Completed list\n   - `remove N` - Remove todo N entirely\n   - `undo N` - Mark completed todo N as incomplete\n   - `list [N]` or no args - Show all (or N number of) todos in a user-friendly format, with each todo numbered for reference\n   - `past due` - Show all of the tasks which are past due and still active\n   - `next` - Shows the next active task in the list, this should respect Due dates, if there are any. If not, just show the first todo in the Active list\n\n## Todo Format:\nUse this markdown format in todos.md:\n```markdown\n# Project Todos\n\n## Active\n- [ ] Task description here | Due: MM-DD-YYYY (conditionally include HH:MM AM\u002FPM, if specified)\n- [ ] Another task \n\n## Completed  \n- [x] Finished task | Done: MM-DD-YYYY (conditionally include HH:MM AM\u002FPM, if specified) \n- [x] Another completed task | Due: MM-DD-YYYY (conditionally include HH:MM AM\u002FPM, if specified) | Done: MM-DD-YYYY (conditionally include HH:MM AM\u002FPM, if specified) \n```\n\n## Behavior:\n- Number todos when displaying (1, 2, 3...)\n- Keep completed todos in a separate section\n- Todos do not need to have Due Dates\u002FTimes\n- Keep the Active list sorted descending by Due Date, if there are any; though in a list with mixed tasks with and without Due Dates, those with Due Dates should come before those without Due Dates\n- If todos.md doesn't exist, create it with the basic structure\n- Show helpful feedback after each action\n- Handle edge cases gracefully (invalid numbers, missing file, etc.)\n- All provided dates\u002Ftimes should be saved\u002Fformatted in a standardized format of MM\u002FDD\u002FYYYY (or DD\u002FMM\u002FYYYY depending on locale), unless the user specifies a different format\n- Times should not be included in the due date format unless requested (`due N in 2 hours` should be MM\u002FDD\u002FYYYY @ [+ 2 hours from now]) \n\nAlways be concise and helpful in your responses.\n\n",{"name":5,"origin":24,"description":7},"awesome-claude-code","main","e49a897c0789a26d4e8cf16b3e0322b9032f584a","tools\u002Fskills\u002Fawesome-claude-code\u002Ftodo",0,"https:\u002F\u002Fgithub.com\u002FKushal9889\u002Fclaude-plugins","https:\u002F\u002Fgithub.com\u002FKushal9889","https:\u002F\u002Fkushal-portfolio-223.netlify.app","AI Engineer · MSCS @ BU · Open PRs: vLLM #56846, LlamaIndex #23053 · Reported deepagents #4846 (maintainer fix #4925)","2026-11-13 01:03:25",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Kushal9889\u002Fclaude-plugins --skill todo",{"tool":40,"command":41},"bunx","bunx skills add Kushal9889\u002Fclaude-plugins --skill todo",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Kushal9889\u002Fclaude-plugins --skill todo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKushal9889\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Ftools\u002Fskills\u002Fawesome-claude-code\u002Ftodo\u002FSKILL.md",true,[],[49,56,62,68,75,82],{"skillNo":50,"name":51,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M78TAEHR7PW92YHTBFTJRMYP","higgsfield-skills","https:\u002F\u002Fgithub.com\u002FKushal9889\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Finstalled\u002Fhiggsfield-skills\u002Fskills\u002Fhiggsfield-skills\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":57,"name":58,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":55},"01M78TAB9MCR7QH3NZJKH5PJFJ","cutaway","https:\u002F\u002Fgithub.com\u002FKushal9889\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Finstalled\u002Fcutaway\u002Fskills\u002Fcutaway\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":55},"01M78TA9YK7YE80960SFP5QJ6D","cracked","https:\u002F\u002Fgithub.com\u002FKushal9889\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Finstalled\u002Fcracked\u002Fskills\u002Fcracked\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M75NWKDRSD7GPTBD80S8P5KW","spec","Create, amend, or backprop bugs into SPEC.md at repo root. Sole mutator\nof the project spec. Triggers when the user asks to write a spec, start\na new spec, distill a spec from existing code, add invariants, amend\nsections (§G, §C, §I, §V, §T, §B), or record a bug via backprop.\nCommon phrasings: \"write the spec for...\", \"new spec\", \"bug: ...\",\n\"amend §V.3\", \"distill spec from code\", \"spec this idea\". Reads and\nfollows FORMAT.md for the caveman encoding rules and pipe-table shape\nof §T and §B.","https:\u002F\u002Fgithub.com\u002FKushal9889\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fworkflow\u002Fskills\u002Fspec\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M75NWFNN2NFMPZY5X9Q2DTBT","check","Read-only drift detector. Diffs SPEC.md against current code and reports\nviolations grouped by severity. Writes nothing — suggests remedies via\nthe spec or build skills but never invokes them. Triggers when the user\nasks to check drift, audit the spec, verify invariants, or ask whether\ncode still matches the spec. Phrasings: \"check drift\", \"audit the spec\",\n\"does the code still match §V\", \"check invariants\", \"spec vs code\".","https:\u002F\u002Fgithub.com\u002FKushal9889\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fworkflow\u002Fskills\u002Fcheck\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M75NWCP6RRA3PFBPN8B94FYE","backprop","Bug → spec protocol. When a bug is found or a test fails, trace the cause,\ndecide whether a new §V invariant would catch recurrence, append to §B.\nThis is the one non-obvious thing SDD does that plan-then-execute doesn't.\nTriggers on test failure, bug report, post-mortem, or explicit user ask.","https:\u002F\u002Fgithub.com\u002FKushal9889\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Fworkflow\u002Fskills\u002Fbackprop\u002FSKILL.md",[],[]]