[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77WF7B9HTVVABDX1DT664DY":3,"skill-same:01M77WF7B9HTVVABDX1DT664DY":56},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":38,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M77WF7B9HTVVABDX1DT664DY","to-do",null,"Give your AI the power to act in the future. Schedule delayed prompts and one-off reminders that automatically wake the agent up at an exact moment to execute workflows, check systems, or send notifications.","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Ft\u002Fto-do\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: to-do\ndescription: Give your AI the power to act in the future. Schedule delayed prompts and one-off reminders that automatically wake the agent up at an exact moment to execute workflows, check systems, or send notifications.\nmetadata: {\"clawdbot\":{\"emoji\":\"⏰\",\"requires\":{\"bins\":[\"node\"],\"env\":[\"OPENCLAW_BIN\",\"OPENCLAW_TZ\"]}}}\n---\n\n# SKILL: To-Do (Ephemeral Tasks)\n\n\u003Cidentity>\n\nCross-platform task scheduler that programs one-off delayed actions using the OS native scheduler (`at` on Linux\u002FmacOS · `schtasks` on Windows). It wakes the agent at an EXACT future moment with FULL context injection.\n\n\u003C\u002Fidentity>\n\n\u003Cgoal>\n\nSchedule, LIST, and MANAGE ephemeral tasks that fire at a PRECISE time in the user's timezone — ENSURE the future agent wakes up with a FULLY self-contained instruction, correct routing, and ZERO ambiguity.\n\n\u003C\u002Fgoal>\n\n---\n\n## Required Environment Variables\n\n- `OPENCLAW_BIN`: Absolute path to the `openclaw` binary (ej. `\u002Fusr\u002Fbin\u002Fopenclaw`)\n- `OPENCLAW_TZ`: User's IANA timezone (ej. `America\u002FMexico_City`)\n\nThe skill WILL NOT START if either variable is missing.\n\nWhy `OPENCLAW_TZ`? The server may run in UTC while the user lives in a different timezone. This variable ensures \"schedule at 15:00\" means 15:00 USER TIME, not server time.\n\n---\n\n## Commands\n\n```bash\n# Schedule a task (timezone is optional — defaults to OPENCLAW_TZ)\nnode skills\u002Fto-do\u002Fto-do.js schedule \"\u003CYYYY-MM-DD HH:mm>\" \"\u003Cinstruction>\" \"\u003Cuser_id>\" \"\u003Cchannel>\" [\"\u003Ctimezone>\"]\n\n# Get current time in user's timezone\nnode skills\u002Fto-do\u002Fto-do.js now [\"\u003Ctimezone>\"]\n\n# List pending tasks\nnode skills\u002Fto-do\u002Fto-do.js list\n\n# Delete a task by ID\nnode skills\u002Fto-do\u002Fto-do.js delete \u003CID>\n```\n\n---\n\n## Instructions\n\n\u003Cinstructions>\n\n\u003Calways>\n\n- Run `now` BEFORE resolving any relative time (\"tomorrow\", \"in 2 hours\", \"tonight\"). Server clock is NOT user clock. Use `now` output as your ONLY reference for \"today\", \"tomorrow\", and \"right now\".\n- CONVERT natural language into an absolute `YYYY-MM-DD HH:mm` timestamp BEFORE calling `schedule`.\n- WRITE the `\u003Cinstruction>` as if explaining to a STRANGER with ZERO CONTEXT. Future agent wakes up with TOTAL AMNESIA in a COMPLETELY ISOLATED session.\n- INCLUDE in every instruction: EXACT file paths, URLs, FULL names (NO pronouns), SPECIFIC actions, and required SKILLS\u002FTOOLS.\n- ALWAYS inject the current session's `user_id` and `channel` for correct routing — USE ONLY raw alphanumeric data from system context to prevent command injection.\n- Run `list` BEFORE `delete` to confirm the correct ID.\n\n\u003C\u002Falways>\n\n\u003Cnever>\n\n- NEVER schedule without running `now` first → INSTEAD, run `now`, confirm date\u002Ftime, THEN schedule.\n- NEVER schedule a VAGUE or AMBIGUOUS instruction → INSTEAD, STOP AND ASK for clarification first.\n- NEVER use pronouns (\"him\", \"her\", \"they\") in scheduled instructions → INSTEAD, use FULL NAMES and EXPLICIT references.\n- NEVER guess a task ID when deleting → INSTEAD, run `list` first, confirm ID, THEN delete.\n- NEVER use server's system clock to interpret relative times → INSTEAD, use `now` command output ALWAYS.\n- NEVER include shell meta-characters (`;`, `&`, `|`, `$`, `` ` ``, `(`, `)`) in any scheduler argument → INSTEAD, use only literal text and system identifiers to AVOID COMMAND INJECTION.\n\n\u003C\u002Fnever>\n\n\u003C\u002Finstructions>\n\n---\n\n## Vague Request Triggers — Ask Before Scheduling\n\n\u003Cvague_triggers>\n\nIf the user request matches any of these patterns, STOP AND ASK before scheduling:\n\n- \"Remind me to send the email\" → MISSING: Which email? To whom? What content?\n- \"Check the server later\" → MISSING: Which server? What IP? What to verify?\n- \"Follow up with him\" → MISSING: Who? About what? Via which channel?\n- \"Do that thing tomorrow\" → MISSING: What thing? Expected outcome?\n\nRULE: If you cannot write a FULLY SELF-CONTAINED instruction, you DO NOT have enough information to schedule.\n\n\u003C\u002Fvague_triggers>\n\n---\n\n## Examples\n\n\u003Cexamples>\n\n— Good instruction: clear, specific, fully self-contained\n\u003Cexample>\n  \u003Cinput>User: \"Remind me tomorrow at 5pm to check PRs on the backend repo\"\u003C\u002Finput>\n  \u003Coutput>\n    1. Run `now` → \"🕒 Current Time (America\u002FMexico_City): 2\u002F26\u002F2026, 2:45 PM\" → tomorrow = 2026-02-27\n    2. Ask: \"Which backend repo? What should I check specifically?\"\n    3. User clarifies: \"backend-api on GitHub, check if there are pending PRs for the auth module\"\n    4. Schedule:\n    ```bash\n    node skills\u002Fto-do\u002Fto-do.js schedule \"2026-02-27 17:00\" \\\n      \"Check the 'backend-api' repo on GitHub. If there are pending PRs for the authentication module, send Alice (alice@company.com) a Slack reminder to review them before the 5 PM deployment freeze. Reference deployment logs at \u002Fvar\u002Flog\u002Fdeploy.log.\" \\\n      \"7684875449\" \"telegram\"\n    ```\n    5. Confirm with the output format below.\n  \u003C\u002Foutput>\n\u003C\u002Fexample>\n\n— Bad instruction: vague, missing details\n\u003Cexample>\n  \u003Cinput>\"Remind him to push the code later.\"\u003C\u002Finput>\n  \u003Coutput>\n    ❌ DO NOT schedule this. Missing: who is \"him\"? Which repo? Which branch? What time is \"later\"?\n    → Ask the user to clarify all missing details first.\n  \u003C\u002Foutput>\n\u003C\u002Fexample>\n\n— Relative time resolution\n\u003Cexample>\n  \u003Cinput>User: \"Set a reminder for in 2 hours\"\u003C\u002Finput>\n  \u003Coutput>\n    1. Run `now` → \"🕒 Current Time (America\u002FMexico_City): 2\u002F26\u002F2026, 2:45 PM\"\n    2. Calculate: 2:45 PM + 2h = 4:45 PM → \"2026-02-26 16:45\"\n    3. Ask what the reminder should say (if not specified)\n    4. Schedule with the absolute timestamp\n  \u003C\u002Foutput>\n\u003C\u002Fexample>\n\n\u003C\u002Fexamples>\n\n---\n\n## Output Format\n\nAfter scheduling, respond with EXACTLY THREE PARTS in this order:\n\n1. NATURAL RESPONSE:\nBrief, casual confirmation. Match user tone\u002Fenergy. NEVER just say \"Done\". Acknowledge WHAT was scheduled conversationally.\n\n2. CONFIRMATION BLOCK:\nTemplate for the user to see exact details:\n```\n> `Day, Month DD · HH:MM TZ`\n> EXACT INSTRUCTION LEFT FOR THE FUTURE AGENT\n```\n\n3. PROACTIVE CLOSING:\nShort suggestion or question (1-2 sentences).\n- Propose a RELATED TASK (pre-reminder, follow-up, etc).\n- Ask if they want to SCHEDULE SOMETHING ELSE.\n- Offer to ADJUST THE TIME or add details.\n\nDO NOT BE PUSHY. JUST BE HELPFUL.\n\n---\n\n— CASUAL \u002F PERSONAL TASK\n\u003Cexample>\nAll set! Your gym session is locked in for tomorrow at noon 🏋️\n\n> `Friday, February 27 · 12:00 PM CST`\n> SEND A TELEGRAM REMINDER TO DANIEL: \"TIME TO HIT THE GYM FOR A BIT.\"\n\nWant me to add another reminder 30 min before so you can get ready? 💪\n\u003C\u002Fexample>\n\n— WORK \u002F PROFESSIONAL TASK\n\u003Cexample>\nDone! Got that scheduled for 5 PM sharp 📋\n\n> `Thursday, February 27 · 5:00 PM CST`\n> CHECK THE 'BACKEND-API' REPOSITORY ON GITHUB. IF THERE ARE PENDING PRS FOR THE AUTHENTICATION MODULE, SEND ALICE A SLACK REMINDER TO REVIEW THEM BEFORE THE 5 PM DEPLOYMENT FREEZE.\n\nNeed to schedule anything else for today, or a follow-up after reviewing those PRs?\n\u003C\u002Fexample>\n\n---\n\n## Common Errors\n\n- ERROR: `Missing required environment variable(s)`\n  - CAUSE: `OPENCLAW_BIN` or `OPENCLAW_TZ` not set\n  - FIX: Add to `.env` or shell profile\n\n- ERROR: `at` not found\n  - CAUSE: Linux\u002FmacOS `atd` daemon not running\n  - FIX: `sudo systemctl enable atd && sudo systemctl start atd`\n\n- ERROR: Task fires but agent has NO CONTEXT\n  - CAUSE: Vague instruction scheduled\n  - FIX: Re-schedule with FULLY SELF-CONTAINED instruction\n\n- ERROR: WRONG TIME (fired early\u002Flate)\n  - CAUSE: Used server clock instead of `now`\n  - FIX: ALWAYS run `now` first; NEVER trust server clock\n\n- ERROR: Deleting WRONG task\n  - CAUSE: Guessed ID\n  - FIX: Run `list` first, confirm ID, THEN `delete`","# SKILL: To-Do (Ephemeral Tasks)\n\n\u003Cidentity>\n\nCross-platform task scheduler that programs one-off delayed actions using the OS native scheduler (`at` on Linux\u002FmacOS · `schtasks` on Windows). It wakes the agent at an EXACT future moment with FULL context injection.\n\n\u003C\u002Fidentity>\n\n\u003Cgoal>\n\nSchedule, LIST, and MANAGE ephemeral tasks that fire at a PRECISE time in the user's timezone — ENSURE the future agent wakes up with a FULLY self-contained instruction, correct routing, and ZERO ambiguity.\n\n\u003C\u002Fgoal>\n\n---\n\n## Required Environment Variables\n\n- `OPENCLAW_BIN`: Absolute path to the `openclaw` binary (ej. `\u002Fusr\u002Fbin\u002Fopenclaw`)\n- `OPENCLAW_TZ`: User's IANA timezone (ej. `America\u002FMexico_City`)\n\nThe skill WILL NOT START if either variable is missing.\n\nWhy `OPENCLAW_TZ`? The server may run in UTC while the user lives in a different timezone. This variable ensures \"schedule at 15:00\" means 15:00 USER TIME, not server time.\n\n---\n\n## Commands\n\n```bash\n# Schedule a task (timezone is optional — defaults to OPENCLAW_TZ)\nnode skills\u002Fto-do\u002Fto-do.js schedule \"\u003CYYYY-MM-DD HH:mm>\" \"\u003Cinstruction>\" \"\u003Cuser_id>\" \"\u003Cchannel>\" [\"\u003Ctimezone>\"]\n\n# Get current time in user's timezone\nnode skills\u002Fto-do\u002Fto-do.js now [\"\u003Ctimezone>\"]\n\n# List pending tasks\nnode skills\u002Fto-do\u002Fto-do.js list\n\n# Delete a task by ID\nnode skills\u002Fto-do\u002Fto-do.js delete \u003CID>\n```\n\n---\n\n## Instructions\n\n\u003Cinstructions>\n\n\u003Calways>\n\n- Run `now` BEFORE resolving any relative time (\"tomorrow\", \"in 2 hours\", \"tonight\"). Server clock is NOT user clock. Use `now` output as your ONLY reference for \"today\", \"tomorrow\", and \"right now\".\n- CONVERT natural language into an absolute `YYYY-MM-DD HH:mm` timestamp BEFORE calling `schedule`.\n- WRITE the `\u003Cinstruction>` as if explaining to a STRANGER with ZERO CONTEXT. Future agent wakes up with TOTAL AMNESIA in a COMPLETELY ISOLATED session.\n- INCLUDE in every instruction: EXACT file paths, URLs, FULL names (NO pronouns), SPECIFIC actions, and required SKILLS\u002FTOOLS.\n- ALWAYS inject the current session's `user_id` and `channel` for correct routing — USE ONLY raw alphanumeric data from system context to prevent command injection.\n- Run `list` BEFORE `delete` to confirm the correct ID.\n\n\u003C\u002Falways>\n\n\u003Cnever>\n\n- NEVER schedule without running `now` first → INSTEAD, run `now`, confirm date\u002Ftime, THEN schedule.\n- NEVER schedule a VAGUE or AMBIGUOUS instruction → INSTEAD, STOP AND ASK for clarification first.\n- NEVER use pronouns (\"him\", \"her\", \"they\") in scheduled instructions → INSTEAD, use FULL NAMES and EXPLICIT references.\n- NEVER guess a task ID when deleting → INSTEAD, run `list` first, confirm ID, THEN delete.\n- NEVER use server's system clock to interpret relative times → INSTEAD, use `now` command output ALWAYS.\n- NEVER include shell meta-characters (`;`, `&`, `|`, `$`, `` ` ``, `(`, `)`) in any scheduler argument → INSTEAD, use only literal text and system identifiers to AVOID COMMAND INJECTION.\n\n\u003C\u002Fnever>\n\n\u003C\u002Finstructions>\n\n---\n\n## Vague Request Triggers — Ask Before Scheduling\n\n\u003Cvague_triggers>\n\nIf the user request matches any of these patterns, STOP AND ASK before scheduling:\n\n- \"Remind me to send the email\" → MISSING: Which email? To whom? What content?\n- \"Check the server later\" → MISSING: Which server? What IP? What to verify?\n- \"Follow up with him\" → MISSING: Who? About what? Via which channel?\n- \"Do that thing tomorrow\" → MISSING: What thing? Expected outcome?\n\nRULE: If you cannot write a FULLY SELF-CONTAINED instruction, you DO NOT have enough information to schedule.\n\n\u003C\u002Fvague_triggers>\n\n---\n\n## Examples\n\n\u003Cexamples>\n\n— Good instruction: clear, specific, fully self-contained\n\u003Cexample>\n  \u003Cinput>User: \"Remind me tomorrow at 5pm to check PRs on the backend repo\"\u003C\u002Finput>\n  \u003Coutput>\n    1. Run `now` → \"🕒 Current Time (America\u002FMexico_City): 2\u002F26\u002F2026, 2:45 PM\" → tomorrow = 2026-02-27\n    2. Ask: \"Which backend repo? What should I check specifically?\"\n    3. User clarifies: \"backend-api on GitHub, check if there are pending PRs for the auth module\"\n    4. Schedule:\n    ```bash\n    node skills\u002Fto-do\u002Fto-do.js schedule \"2026-02-27 17:00\" \\\n      \"Check the 'backend-api' repo on GitHub. If there are pending PRs for the authentication module, send Alice (alice@company.com) a Slack reminder to review them before the 5 PM deployment freeze. Reference deployment logs at \u002Fvar\u002Flog\u002Fdeploy.log.\" \\\n      \"7684875449\" \"telegram\"\n    ```\n    5. Confirm with the output format below.\n  \u003C\u002Foutput>\n\u003C\u002Fexample>\n\n— Bad instruction: vague, missing details\n\u003Cexample>\n  \u003Cinput>\"Remind him to push the code later.\"\u003C\u002Finput>\n  \u003Coutput>\n    ❌ DO NOT schedule this. Missing: who is \"him\"? Which repo? Which branch? What time is \"later\"?\n    → Ask the user to clarify all missing details first.\n  \u003C\u002Foutput>\n\u003C\u002Fexample>\n\n— Relative time resolution\n\u003Cexample>\n  \u003Cinput>User: \"Set a reminder for in 2 hours\"\u003C\u002Finput>\n  \u003Coutput>\n    1. Run `now` → \"🕒 Current Time (America\u002FMexico_City): 2\u002F26\u002F2026, 2:45 PM\"\n    2. Calculate: 2:45 PM + 2h = 4:45 PM → \"2026-02-26 16:45\"\n    3. Ask what the reminder should say (if not specified)\n    4. Schedule with the absolute timestamp\n  \u003C\u002Foutput>\n\u003C\u002Fexample>\n\n\u003C\u002Fexamples>\n\n---\n\n## Output Format\n\nAfter scheduling, respond with EXACTLY THREE PARTS in this order:\n\n1. NATURAL RESPONSE:\nBrief, casual confirmation. Match user tone\u002Fenergy. NEVER just say \"Done\". Acknowledge WHAT was scheduled conversationally.\n\n2. CONFIRMATION BLOCK:\nTemplate for the user to see exact details:\n```\n> `Day, Month DD · HH:MM TZ`\n> EXACT INSTRUCTION LEFT FOR THE FUTURE AGENT\n```\n\n3. PROACTIVE CLOSING:\nShort suggestion or question (1-2 sentences).\n- Propose a RELATED TASK (pre-reminder, follow-up, etc).\n- Ask if they want to SCHEDULE SOMETHING ELSE.\n- Offer to ADJUST THE TIME or add details.\n\nDO NOT BE PUSHY. JUST BE HELPFUL.\n\n---\n\n— CASUAL \u002F PERSONAL TASK\n\u003Cexample>\nAll set! Your gym session is locked in for tomorrow at noon 🏋️\n\n> `Friday, February 27 · 12:00 PM CST`\n> SEND A TELEGRAM REMINDER TO DANIEL: \"TIME TO HIT THE GYM FOR A BIT.\"\n\nWant me to add another reminder 30 min before so you can get ready? 💪\n\u003C\u002Fexample>\n\n— WORK \u002F PROFESSIONAL TASK\n\u003Cexample>\nDone! Got that scheduled for 5 PM sharp 📋\n\n> `Thursday, February 27 · 5:00 PM CST`\n> CHECK THE 'BACKEND-API' REPOSITORY ON GITHUB. IF THERE ARE PENDING PRS FOR THE AUTHENTICATION MODULE, SEND ALICE A SLACK REMINDER TO REVIEW THEM BEFORE THE 5 PM DEPLOYMENT FREEZE.\n\nNeed to schedule anything else for today, or a follow-up after reviewing those PRs?\n\u003C\u002Fexample>\n\n---\n\n## Common Errors\n\n- ERROR: `Missing required environment variable(s)`\n  - CAUSE: `OPENCLAW_BIN` or `OPENCLAW_TZ` not set\n  - FIX: Add to `.env` or shell profile\n\n- ERROR: `at` not found\n  - CAUSE: Linux\u002FmacOS `atd` daemon not running\n  - FIX: `sudo systemctl enable atd && sudo systemctl start atd`\n\n- ERROR: Task fires but agent has NO CONTEXT\n  - CAUSE: Vague instruction scheduled\n  - FIX: Re-schedule with FULLY SELF-CONTAINED instruction\n\n- ERROR: WRONG TIME (fired early\u002Flate)\n  - CAUSE: Used server clock instead of `now`\n  - FIX: ALWAYS run `now` first; NEVER trust server clock\n\n- ERROR: Deleting WRONG task\n  - CAUSE: Guessed ID\n  - FIX: Run `list` first, confirm ID, THEN `delete`",{"name":5,"metadata":24,"description":7},{"clawdbot":25},{"emoji":26,"requires":27},"⏰",{"env":28,"bins":31},[29,30],"OPENCLAW_BIN","OPENCLAW_TZ",[32],"node","master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Ft\u002Fto-do",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill to-do",{"tool":48,"command":49},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill to-do",{"tool":51,"command":52},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill to-do","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Ft\u002Fto-do\u002FSKILL.md",true,[],[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]