[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M715QZ8SHT6TTFKMFCW71HW8":3,"skill-same:01M715QZ8SHT6TTFKMFCW71HW8":57},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":14,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":42,"install":43,"resources":56},"01M715QZ8SHT6TTFKMFCW71HW8","conductor-revert",null,"Git-aware undo by logical work unit (track, phase, or task)","sapsapshen\u002Fai-memory-router","sapsapshen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20347959?v=4","01M6XDQEF1DP50DKF37H81J3J5","shenmian","01M6XDQEJPE41Y3DT2763X8ZJN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcursor\u002Fconductor-revert\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"conductor revert","conductor","revert","git","work","community","task","unit","unknown","track","phase","2026","2026-11-10 10:12:30",false,"---\nname: conductor-revert\ndescription: \"Git-aware undo by logical work unit (track, phase, or task)\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Revert Track\n\nRevert changes by logical work unit with full git awareness. Supports reverting entire tracks, specific phases, or individual tasks.\n\n## Use this skill when\n\n- Working on revert track tasks or workflows\n- Needing guidance, best practices, or checklists for revert track\n\n## Do not use this skill when\n\n- The task is unrelated to revert track\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\n## Pre-flight Checks\n\n1. Verify Conductor is initialized:\n   - Check `conductor\u002Ftracks.md` exists\n   - If missing: Display error and suggest running `\u002Fconductor:setup` first\n\n2. Verify git repository:\n   - Run `git status` to confirm git repo\n   - Check for uncommitted changes\n   - If uncommitted changes exist:\n\n     ```\n     WARNING: Uncommitted changes detected\n\n     Files with changes:\n     {list of files}\n\n     Options:\n     1. Stash changes and continue\n     2. Commit changes first\n     3. Cancel revert\n     ```\n\n3. Verify git is clean enough to revert:\n   - No merge in progress\n   - No rebase in progress\n   - If issues found: Halt and explain resolution steps\n\n## Target Selection\n\n### If argument provided:\n\nParse the argument format:\n\n**Full track:** `{trackId}`\n\n- Example: `auth_20250115`\n- Reverts all commits for the entire track\n\n**Specific phase:** `{trackId}:phase{N}`\n\n- Example: `auth_20250115:phase2`\n- Reverts commits for phase N and all subsequent phases\n\n**Specific task:** `{trackId}:task{X.Y}`\n\n- Example: `auth_20250115:task2.3`\n- Reverts commits for task X.Y only\n\n### If no argument:\n\nDisplay guided selection menu:\n\n```\nWhat would you like to revert?\n\nCurrently In Progress:\n1. [~] Task 2.3 in dashboard_20250112 (most recent)\n\nRecently Completed:\n2. [x] Task 2.2 in dashboard_20250112 (1 hour ago)\n3. [x] Phase 1 in dashboard_20250112 (3 hours ago)\n4. [x] Full track: auth_20250115 (yesterday)\n\nOptions:\n5. Enter specific reference (track:phase or track:task)\n6. Cancel\n\nSelect option:\n```\n\n## Commit Discovery\n\n### For Task Revert\n\n1. Search git log for task-specific commits:\n\n   ```bash\n   git log --oneline --grep=\"{trackId}\" --grep=\"Task {X.Y}\" --all-match\n   ```\n\n2. Also find the plan.md update commit:\n\n   ```bash\n   git log --oneline --grep=\"mark task {X.Y} complete\" --grep=\"{trackId}\" --all-match\n   ```\n\n3. Collect all matching commit SHAs\n\n### For Phase Revert\n\n1. Determine task range for the phase by reading plan.md\n2. Search for all task commits in that phase:\n\n   ```bash\n   git log --oneline --grep=\"{trackId}\" | grep -E \"Task {N}\\.[0-9]\"\n   ```\n\n3. Find phase verification commit if exists\n4. Find all plan.md update commits for phase tasks\n5. Collect all matching commit SHAs in chronological order\n\n### For Full Track Revert\n\n1. Find ALL commits mentioning the track:\n\n   ```bash\n   git log --oneline --grep=\"{trackId}\"\n   ```\n\n2. Find track creation commits:\n\n   ```bash\n   git log --oneline -- \"conductor\u002Ftracks\u002F{trackId}\u002F\"\n   ```\n\n3. Collect all matching commit SHAs in chronological order\n\n## Execution Plan Display\n\nBefore any revert operations, display full plan:\n\n```\n================================================================================\n                           REVERT EXECUTION PLAN\n================================================================================\n\nTarget: {description of what's being reverted}\n\nCommits to revert (in reverse chronological order):\n  1. abc1234 - feat: add chart rendering (dashboard_20250112)\n  2. def5678 - chore: mark task 2.3 complete (dashboard_20250112)\n  3. ghi9012 - feat: add data hooks (dashboard_20250112)\n  4. jkl3456 - chore: mark task 2.2 complete (dashboard_20250112)\n\nFiles that will be affected:\n  - src\u002Fcomponents\u002FDashboard.tsx (modified)\n  - src\u002Fhooks\u002FuseData.ts (will be deleted - was created in these commits)\n  - conductor\u002Ftracks\u002Fdashboard_20250112\u002Fplan.md (modified)\n\nPlan updates:\n  - Task 2.2: [x] -> [ ]\n  - Task 2.3: [~] -> [ ]\n\n================================================================================\n                              !! WARNING !!\n================================================================================\n\nThis operation will:\n- Create {N} revert commits\n- Modify {M} files\n- Reset {P} tasks to pending status\n\nThis CANNOT be easily undone without manual intervention.\n\n================================================================================\n\nType 'YES' to proceed, or anything else to cancel:\n```\n\n**CRITICAL: Require explicit 'YES' confirmation. Do not proceed on 'y', 'yes', or enter.**\n\n## Revert Execution\n\nExecute reverts in reverse chronological order (newest first):\n\n```\nExecuting revert plan...\n\n[1\u002F4] Reverting abc1234...\n      git revert --no-edit abc1234\n      ✓ Success\n\n[2\u002F4] Reverting def5678...\n      git revert --no-edit def5678\n      ✓ Success\n\n[3\u002F4] Reverting ghi9012...\n      git revert --no-edit ghi9012\n      ✓ Success\n\n[4\u002F4] Reverting jkl3456...\n      git revert --no-edit jkl3456\n      ✓ Success\n```\n\n### On Merge Conflict\n\nIf any revert produces a merge conflict:\n\n```\n================================================================================\n                           MERGE CONFLICT DETECTED\n================================================================================\n\nConflict occurred while reverting: {sha} - {message}\n\nConflicted files:\n  - src\u002Fcomponents\u002FDashboard.tsx\n\nOptions:\n1. Show conflict details\n2. Abort revert sequence (keeps completed reverts)\n3. Open manual resolution guide\n\nIMPORTANT: Reverts 1-{N} have been completed. You may need to manually\nresolve this conflict before continuing or fully undo the revert sequence.\n\nSelect option:\n```\n\n**HALT immediately on any conflict. Do not attempt automatic resolution.**\n\n## Plan.md Updates\n\nAfter successful git reverts, update plan.md:\n\n1. Read current plan.md\n2. For each reverted task, change marker:\n   - `[x]` -> `[ ]`\n   - `[~]` -> `[ ]`\n3. Write updated plan.md\n4. Update metadata.json:\n   - Decrement `tasks.completed`\n   - Update `status` if needed\n   - Update `updated` timestamp\n\n**Do NOT commit plan.md changes** - they are part of the revert operation\n\n## Track Status Updates\n\n### If reverting entire track:\n\n- In tracks.md: Change `[x]` or `[~]` to `[ ]`\n- Consider offering to delete the track directory entirely\n\n### If reverting to incomplete state:\n\n- In tracks.md: Ensure marked as `[~]` if partially complete, `[ ]` if fully reverted\n\n## Verification\n\nAfter revert completion:\n\n```\n================================================================================\n                           REVERT COMPLETE\n================================================================================\n\nSummary:\n  - Reverted {N} commits\n  - Reset {P} tasks to pending\n  - {M} files affected\n\nGit log now shows:\n  {recent commit history}\n\nPlan.md status:\n  - Task 2.2: [ ] Pending\n  - Task 2.3: [ ] Pending\n\n================================================================================\n\nVerify the revert was successful:\n  1. Run tests: {test command}\n  2. Check application: {relevant check}\n\nIf issues are found, you may need to:\n  - Fix conflicts manually\n  - Re-implement the reverted tasks\n  - Use 'git revert HEAD~{N}..HEAD' to undo the reverts\n\n================================================================================\n```\n\n## Safety Rules\n\n1. **NEVER use `git reset --hard`** - Only use `git revert`\n2. **NEVER use `git push --force`** - Only safe push operations\n3. **NEVER auto-resolve conflicts** - Always halt for human intervention\n4. **ALWAYS show full plan** - User must see exactly what will happen\n5. **REQUIRE explicit 'YES'** - Not 'y', not enter, only 'YES'\n6. **HALT on ANY error** - Do not attempt to continue past failures\n7. **PRESERVE history** - Revert commits are preferred over history rewriting\n\n## Edge Cases\n\n### Track Never Committed\n\n```\nNo commits found for track: {trackId}\n\nThe track exists but has no associated commits. This may mean:\n- Implementation never started\n- Commits used different format\n\nOptions:\n1. Delete track directory only\n2. Cancel\n```\n\n### Commits Already Reverted\n\n```\nSome commits appear to already be reverted:\n  - abc1234 was reverted by xyz9876\n\nOptions:\n1. Skip already-reverted commits\n2. Cancel and investigate\n```\n\n### Remote Already Pushed\n\n```\nWARNING: Some commits have been pushed to remote\n\nCommits on remote:\n  - abc1234 (origin\u002Fmain)\n  - def5678 (origin\u002Fmain)\n\nReverting will create new revert commits that you'll need to push.\nThis is the safe approach (no force push required).\n\nContinue with revert? (YES\u002Fno):\n```\n\n## Undo the Revert\n\nIf user needs to undo the revert itself:\n\n```\nTo undo this revert operation:\n\n  git revert HEAD~{N}..HEAD\n\nThis will create new commits that restore the reverted changes.\n\nAlternatively, if not yet pushed:\n  git reset --soft HEAD~{N}\n  git checkout -- .\n\n(Use with caution - this discards the revert commits)\n```\n","# Revert Track\n\nRevert changes by logical work unit with full git awareness. Supports reverting entire tracks, specific phases, or individual tasks.\n\n## Use this skill when\n\n- Working on revert track tasks or workflows\n- Needing guidance, best practices, or checklists for revert track\n\n## Do not use this skill when\n\n- The task is unrelated to revert track\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\n## Pre-flight Checks\n\n1. Verify Conductor is initialized:\n   - Check `conductor\u002Ftracks.md` exists\n   - If missing: Display error and suggest running `\u002Fconductor:setup` first\n\n2. Verify git repository:\n   - Run `git status` to confirm git repo\n   - Check for uncommitted changes\n   - If uncommitted changes exist:\n\n     ```\n     WARNING: Uncommitted changes detected\n\n     Files with changes:\n     {list of files}\n\n     Options:\n     1. Stash changes and continue\n     2. Commit changes first\n     3. Cancel revert\n     ```\n\n3. Verify git is clean enough to revert:\n   - No merge in progress\n   - No rebase in progress\n   - If issues found: Halt and explain resolution steps\n\n## Target Selection\n\n### If argument provided:\n\nParse the argument format:\n\n**Full track:** `{trackId}`\n\n- Example: `auth_20250115`\n- Reverts all commits for the entire track\n\n**Specific phase:** `{trackId}:phase{N}`\n\n- Example: `auth_20250115:phase2`\n- Reverts commits for phase N and all subsequent phases\n\n**Specific task:** `{trackId}:task{X.Y}`\n\n- Example: `auth_20250115:task2.3`\n- Reverts commits for task X.Y only\n\n### If no argument:\n\nDisplay guided selection menu:\n\n```\nWhat would you like to revert?\n\nCurrently In Progress:\n1. [~] Task 2.3 in dashboard_20250112 (most recent)\n\nRecently Completed:\n2. [x] Task 2.2 in dashboard_20250112 (1 hour ago)\n3. [x] Phase 1 in dashboard_20250112 (3 hours ago)\n4. [x] Full track: auth_20250115 (yesterday)\n\nOptions:\n5. Enter specific reference (track:phase or track:task)\n6. Cancel\n\nSelect option:\n```\n\n## Commit Discovery\n\n### For Task Revert\n\n1. Search git log for task-specific commits:\n\n   ```bash\n   git log --oneline --grep=\"{trackId}\" --grep=\"Task {X.Y}\" --all-match\n   ```\n\n2. Also find the plan.md update commit:\n\n   ```bash\n   git log --oneline --grep=\"mark task {X.Y} complete\" --grep=\"{trackId}\" --all-match\n   ```\n\n3. Collect all matching commit SHAs\n\n### For Phase Revert\n\n1. Determine task range for the phase by reading plan.md\n2. Search for all task commits in that phase:\n\n   ```bash\n   git log --oneline --grep=\"{trackId}\" | grep -E \"Task {N}\\.[0-9]\"\n   ```\n\n3. Find phase verification commit if exists\n4. Find all plan.md update commits for phase tasks\n5. Collect all matching commit SHAs in chronological order\n\n### For Full Track Revert\n\n1. Find ALL commits mentioning the track:\n\n   ```bash\n   git log --oneline --grep=\"{trackId}\"\n   ```\n\n2. Find track creation commits:\n\n   ```bash\n   git log --oneline -- \"conductor\u002Ftracks\u002F{trackId}\u002F\"\n   ```\n\n3. Collect all matching commit SHAs in chronological order\n\n## Execution Plan Display\n\nBefore any revert operations, display full plan:\n\n```\n================================================================================\n                           REVERT EXECUTION PLAN\n================================================================================\n\nTarget: {description of what's being reverted}\n\nCommits to revert (in reverse chronological order):\n  1. abc1234 - feat: add chart rendering (dashboard_20250112)\n  2. def5678 - chore: mark task 2.3 complete (dashboard_20250112)\n  3. ghi9012 - feat: add data hooks (dashboard_20250112)\n  4. jkl3456 - chore: mark task 2.2 complete (dashboard_20250112)\n\nFiles that will be affected:\n  - src\u002Fcomponents\u002FDashboard.tsx (modified)\n  - src\u002Fhooks\u002FuseData.ts (will be deleted - was created in these commits)\n  - conductor\u002Ftracks\u002Fdashboard_20250112\u002Fplan.md (modified)\n\nPlan updates:\n  - Task 2.2: [x] -> [ ]\n  - Task 2.3: [~] -> [ ]\n\n================================================================================\n                              !! WARNING !!\n================================================================================\n\nThis operation will:\n- Create {N} revert commits\n- Modify {M} files\n- Reset {P} tasks to pending status\n\nThis CANNOT be easily undone without manual intervention.\n\n================================================================================\n\nType 'YES' to proceed, or anything else to cancel:\n```\n\n**CRITICAL: Require explicit 'YES' confirmation. Do not proceed on 'y', 'yes', or enter.**\n\n## Revert Execution\n\nExecute reverts in reverse chronological order (newest first):\n\n```\nExecuting revert plan...\n\n[1\u002F4] Reverting abc1234...\n      git revert --no-edit abc1234\n      ✓ Success\n\n[2\u002F4] Reverting def5678...\n      git revert --no-edit def5678\n      ✓ Success\n\n[3\u002F4] Reverting ghi9012...\n      git revert --no-edit ghi9012\n      ✓ Success\n\n[4\u002F4] Reverting jkl3456...\n      git revert --no-edit jkl3456\n      ✓ Success\n```\n\n### On Merge Conflict\n\nIf any revert produces a merge conflict:\n\n```\n================================================================================\n                           MERGE CONFLICT DETECTED\n================================================================================\n\nConflict occurred while reverting: {sha} - {message}\n\nConflicted files:\n  - src\u002Fcomponents\u002FDashboard.tsx\n\nOptions:\n1. Show conflict details\n2. Abort revert sequence (keeps completed reverts)\n3. Open manual resolution guide\n\nIMPORTANT: Reverts 1-{N} have been completed. You may need to manually\nresolve this conflict before continuing or fully undo the revert sequence.\n\nSelect option:\n```\n\n**HALT immediately on any conflict. Do not attempt automatic resolution.**\n\n## Plan.md Updates\n\nAfter successful git reverts, update plan.md:\n\n1. Read current plan.md\n2. For each reverted task, change marker:\n   - `[x]` -> `[ ]`\n   - `[~]` -> `[ ]`\n3. Write updated plan.md\n4. Update metadata.json:\n   - Decrement `tasks.completed`\n   - Update `status` if needed\n   - Update `updated` timestamp\n\n**Do NOT commit plan.md changes** - they are part of the revert operation\n\n## Track Status Updates\n\n### If reverting entire track:\n\n- In tracks.md: Change `[x]` or `[~]` to `[ ]`\n- Consider offering to delete the track directory entirely\n\n### If reverting to incomplete state:\n\n- In tracks.md: Ensure marked as `[~]` if partially complete, `[ ]` if fully reverted\n\n## Verification\n\nAfter revert completion:\n\n```\n================================================================================\n                           REVERT COMPLETE\n================================================================================\n\nSummary:\n  - Reverted {N} commits\n  - Reset {P} tasks to pending\n  - {M} files affected\n\nGit log now shows:\n  {recent commit history}\n\nPlan.md status:\n  - Task 2.2: [ ] Pending\n  - Task 2.3: [ ] Pending\n\n================================================================================\n\nVerify the revert was successful:\n  1. Run tests: {test command}\n  2. Check application: {relevant check}\n\nIf issues are found, you may need to:\n  - Fix conflicts manually\n  - Re-implement the reverted tasks\n  - Use 'git revert HEAD~{N}..HEAD' to undo the reverts\n\n================================================================================\n```\n\n## Safety Rules\n\n1. **NEVER use `git reset --hard`** - Only use `git revert`\n2. **NEVER use `git push --force`** - Only safe push operations\n3. **NEVER auto-resolve conflicts** - Always halt for human intervention\n4. **ALWAYS show full plan** - User must see exactly what will happen\n5. **REQUIRE explicit 'YES'** - Not 'y', not enter, only 'YES'\n6. **HALT on ANY error** - Do not attempt to continue past failures\n7. **PRESERVE history** - Revert commits are preferred over history rewriting\n\n## Edge Cases\n\n### Track Never Committed\n\n```\nNo commits found for track: {trackId}\n\nThe track exists but has no associated commits. This may mean:\n- Implementation never started\n- Commits used different format\n\nOptions:\n1. Delete track directory only\n2. Cancel\n```\n\n### Commits Already Reverted\n\n```\nSome commits appear to already be reverted:\n  - abc1234 was reverted by xyz9876\n\nOptions:\n1. Skip already-reverted commits\n2. Cancel and investigate\n```\n\n### Remote Already Pushed\n\n```\nWARNING: Some commits have been pushed to remote\n\nCommits on remote:\n  - abc1234 (origin\u002Fmain)\n  - def5678 (origin\u002Fmain)\n\nReverting will create new revert commits that you'll need to push.\nThis is the safe approach (no force push required).\n\nContinue with revert? (YES\u002Fno):\n```\n\n## Undo the Revert\n\nIf user needs to undo the revert itself:\n\n```\nTo undo this revert operation:\n\n  git revert HEAD~{N}..HEAD\n\nThis will create new commits that restore the reverted changes.\n\nAlternatively, if not yet pushed:\n  git reset --soft HEAD~{N}\n  git checkout -- .\n\n(Use with caution - this discards the revert commits)\n```\n",{"name":5,"risk":27,"source":24,"date_added":36,"description":7},"2026-02-27","main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fcursor\u002Fconductor-revert","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill conductor-revert",{"tool":49,"command":50},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill conductor-revert",{"tool":52,"command":53},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill conductor-revert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcursor\u002Fconductor-revert\u002FSKILL.md",true,[],[58,82,108,118,131,150],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":69,"publishedAt":31},"01M71ATQRKG48SH06FQ697T5G9","wechat-search","Search WeChat Official Account articles using OpenClaw's web search and fetch capabilities with compliance-focused design.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fwechat-search-release\u002FSKILL.md",[64],{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[70,71,72,73,74,75,76,77,78,79,80,81],"wechat search","wechat","search","capabilities","openclaw","design","web search","compliance","web","official","fetch","with",{"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":31},"01M71ATNAVGZB35PFYM2GC5N00","trend-tap","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend tap', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-tap\u002FSKILL.md",[],[89,90,91,92,93,94,72,95,96,97,98,99,100,101,102,103,104,105,106,107],"trend","trend tap","tap","api keys","Bash","time","trending","hacker","aggregator","do","when","brew","live","data","google","install","read","across","api",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":31},"01M71ATJ9AM5KM15AA8PS302EB","trend-radar","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend pulse', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-radar\u002FSKILL.md",[],[115,116,89,100,101,102,103,93,72,105,117,106,107,99,97,96,95,104,94,92],"trend radar","radar","pulse",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":31},"01M71ATGF095N3EJM9G8SD0BB5","tech-news-daily","每日科技新闻汇——从全球多个 RSS 源抓取最新科技新闻，翻译（英→中）、去重、排版成每日简报。当用户询问科技新闻、科技新鲜事、每日科技、技术动态、Daily Tech News 或类似表达时触发此技能。","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftech-news-daily\u002FSKILL.md",[],[125,126,127,128,129,130],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":142,"publishedAt":31},"01M71ATFAEAMQ17M70NQNY7SR8","summarize","Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsummarize\u002FSKILL.md",[137],{"categoryNo":138,"categoryName":139,"taxonomyType":140,"taxonomyTypeDesc":141},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[133,78,143,144,145,81,100,146,147,148,91,149,104],"Audio","cli","youtube","images","https","files","pdfs",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":31},"01M71ATDNS3R0M4H936PACQAWZ","sonoscli","Control Sonos speakers (discover\u002Fstatus\u002Fplay\u002Fvolume\u002Fgroup).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsonoscli\u002FSKILL.md",[],[152,157,158,159,104,160,147,161,162,163,164,165],"status","play","go","latest","github","discover","control","cmd","volume"]