[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7189NPAM8QSJGRTWH05Z281":3,"skill-same:01M7189NPAM8QSJGRTWH05Z281":59},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":14,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M7189NPAM8QSJGRTWH05Z281","conductor-new-track",null,"Create a new track with specification and phased implementation plan","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\u002Fglobal\u002Fconductor-new-track\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32],"conductor new track","conductor","track","new","create","plan","phased implementation","implementation","specification","community","with","unknown","implementation plan","2026","2026-11-10 10:12:30",false,"---\nname: conductor-new-track\ndescription: \"Create a new track with specification and phased implementation plan\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# New Track\n\nCreate a new track (feature, bug fix, chore, or refactor) with a detailed specification and phased implementation plan.\n\n## Use this skill when\n\n- Working on new track tasks or workflows\n- Needing guidance, best practices, or checklists for new track\n\n## Do not use this skill when\n\n- The task is unrelated to new 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\u002Fproduct.md` exists\n   - Check `conductor\u002Ftech-stack.md` exists\n   - Check `conductor\u002Fworkflow.md` exists\n   - If missing: Display error and suggest running `\u002Fconductor:setup` first\n\n2. Load context files:\n   - Read `conductor\u002Fproduct.md` for product context\n   - Read `conductor\u002Ftech-stack.md` for technical context\n   - Read `conductor\u002Fworkflow.md` for TDD\u002Fcommit preferences\n\n## Track Classification\n\nDetermine track type based on description or ask user:\n\n```\nWhat type of track is this?\n\n1. Feature - New functionality\n2. Bug - Fix for existing issue\n3. Chore - Maintenance, dependencies, config\n4. Refactor - Code improvement without behavior change\n```\n\n## Interactive Specification Gathering\n\n**CRITICAL RULES:**\n\n- Ask ONE question per turn\n- Wait for user response before proceeding\n- Tailor questions based on track type\n- Maximum 6 questions total\n\n### For Feature Tracks\n\n**Q1: Feature Summary**\n\n```\nDescribe the feature in 1-2 sentences.\n[If argument provided, confirm: \"You want to: {argument}. Is this correct?\"]\n```\n\n**Q2: User Story**\n\n```\nWho benefits and how?\n\nFormat: As a [user type], I want to [action] so that [benefit].\n```\n\n**Q3: Acceptance Criteria**\n\n```\nWhat must be true for this feature to be complete?\n\nList 3-5 acceptance criteria (one per line):\n```\n\n**Q4: Dependencies**\n\n```\nDoes this depend on any existing code, APIs, or other tracks?\n\n1. No dependencies\n2. Depends on existing code (specify)\n3. Depends on incomplete track (specify)\n```\n\n**Q5: Scope Boundaries**\n\n```\nWhat is explicitly OUT of scope for this track?\n(Helps prevent scope creep)\n```\n\n**Q6: Technical Considerations (optional)**\n\n```\nAny specific technical approach or constraints?\n(Press enter to skip)\n```\n\n### For Bug Tracks\n\n**Q1: Bug Summary**\n\n```\nWhat is broken?\n[If argument provided, confirm]\n```\n\n**Q2: Steps to Reproduce**\n\n```\nHow can this bug be reproduced?\nList steps:\n```\n\n**Q3: Expected vs Actual Behavior**\n\n```\nWhat should happen vs what actually happens?\n```\n\n**Q4: Affected Areas**\n\n```\nWhat parts of the system are affected?\n```\n\n**Q5: Root Cause Hypothesis (optional)**\n\n```\nAny hypothesis about the cause?\n(Press enter to skip)\n```\n\n### For Chore\u002FRefactor Tracks\n\n**Q1: Task Summary**\n\n```\nWhat needs to be done?\n[If argument provided, confirm]\n```\n\n**Q2: Motivation**\n\n```\nWhy is this work needed?\n```\n\n**Q3: Success Criteria**\n\n```\nHow will we know this is complete?\n```\n\n**Q4: Risk Assessment**\n\n```\nWhat could go wrong? Any risky changes?\n```\n\n## Track ID Generation\n\nGenerate track ID in format: `{shortname}_{YYYYMMDD}`\n\n- Extract shortname from feature\u002Fbug summary (2-3 words, lowercase, hyphenated)\n- Use current date\n- Example: `user-auth_20250115`, `nav-bug_20250115`\n\nValidate uniqueness:\n\n- Check `conductor\u002Ftracks.md` for existing IDs\n- If collision, append counter: `user-auth_20250115_2`\n\n## Specification Generation\n\nCreate `conductor\u002Ftracks\u002F{trackId}\u002Fspec.md`:\n\n```markdown\n# Specification: {Track Title}\n\n**Track ID:** {trackId}\n**Type:** {Feature|Bug|Chore|Refactor}\n**Created:** {YYYY-MM-DD}\n**Status:** Draft\n\n## Summary\n\n{1-2 sentence summary}\n\n## Context\n\n{Product context from product.md relevant to this track}\n\n## User Story (for features)\n\nAs a {user}, I want to {action} so that {benefit}.\n\n## Problem Description (for bugs)\n\n{Bug description, steps to reproduce}\n\n## Acceptance Criteria\n\n- [ ] {Criterion 1}\n- [ ] {Criterion 2}\n- [ ] {Criterion 3}\n\n## Dependencies\n\n{List dependencies or \"None\"}\n\n## Out of Scope\n\n{Explicit exclusions}\n\n## Technical Notes\n\n{Technical considerations or \"None specified\"}\n\n---\n\n_Generated by Conductor. Review and edit as needed._\n```\n\n## User Review of Spec\n\nDisplay the generated spec and ask:\n\n```\nHere is the specification I've generated:\n\n{spec content}\n\nIs this specification correct?\n1. Yes, proceed to plan generation\n2. No, let me edit (opens for inline edits)\n3. Start over with different inputs\n```\n\n## Plan Generation\n\nAfter spec approval, generate `conductor\u002Ftracks\u002F{trackId}\u002Fplan.md`:\n\n### Plan Structure\n\n```markdown\n# Implementation Plan: {Track Title}\n\n**Track ID:** {trackId}\n**Spec:** spec.md\n**Created:** {YYYY-MM-DD}\n**Status:** [ ] Not Started\n\n## Overview\n\n{Brief summary of implementation approach}\n\n## Phase 1: {Phase Name}\n\n{Phase description}\n\n### Tasks\n\n- [ ] Task 1.1: {Description}\n- [ ] Task 1.2: {Description}\n- [ ] Task 1.3: {Description}\n\n### Verification\n\n- [ ] {Verification step for phase 1}\n\n## Phase 2: {Phase Name}\n\n{Phase description}\n\n### Tasks\n\n- [ ] Task 2.1: {Description}\n- [ ] Task 2.2: {Description}\n\n### Verification\n\n- [ ] {Verification step for phase 2}\n\n## Phase 3: {Phase Name} (if needed)\n\n...\n\n## Final Verification\n\n- [ ] All acceptance criteria met\n- [ ] Tests passing\n- [ ] Documentation updated (if applicable)\n- [ ] Ready for review\n\n---\n\n_Generated by Conductor. Tasks will be marked [~] in progress and [x] complete._\n```\n\n### Phase Guidelines\n\n- Group related tasks into logical phases\n- Each phase should be independently verifiable\n- Include verification task after each phase\n- TDD tracks: Include test writing tasks before implementation tasks\n- Typical structure:\n  1. **Setup\u002FFoundation** - Initial scaffolding, interfaces\n  2. **Core Implementation** - Main functionality\n  3. **Integration** - Connect with existing system\n  4. **Polish** - Error handling, edge cases, docs\n\n## User Review of Plan\n\nDisplay the generated plan and ask:\n\n```\nHere is the implementation plan:\n\n{plan content}\n\nIs this plan correct?\n1. Yes, create the track\n2. No, let me edit (opens for inline edits)\n3. Add more phases\u002Ftasks\n4. Start over\n```\n\n## Track Creation\n\nAfter plan approval:\n\n1. Create directory structure:\n\n   ```\n   conductor\u002Ftracks\u002F{trackId}\u002F\n   ├── spec.md\n   ├── plan.md\n   ├── metadata.json\n   └── index.md\n   ```\n\n2. Create `metadata.json`:\n\n   ```json\n   {\n     \"id\": \"{trackId}\",\n     \"title\": \"{Track Title}\",\n     \"type\": \"feature|bug|chore|refactor\",\n     \"status\": \"pending\",\n     \"created\": \"ISO_TIMESTAMP\",\n     \"updated\": \"ISO_TIMESTAMP\",\n     \"phases\": {\n       \"total\": N,\n       \"completed\": 0\n     },\n     \"tasks\": {\n       \"total\": M,\n       \"completed\": 0\n     }\n   }\n   ```\n\n3. Create `index.md`:\n\n   ```markdown\n   # Track: {Track Title}\n\n   **ID:** {trackId}\n   **Status:** Pending\n\n   ## Documents\n\n   - Specification\n   - Implementation Plan\n\n   ## Progress\n\n   - Phases: 0\u002F{N} complete\n   - Tasks: 0\u002F{M} complete\n\n   ## Quick Links\n\n   - Back to Tracks\n   - Product Context\n   ```\n\n4. Register in `conductor\u002Ftracks.md`:\n   - Add row to tracks table\n   - Format: `| [ ] | {trackId} | {title} | {created} | {created} |`\n\n5. Update `conductor\u002Findex.md`:\n   - Add track to \"Active Tracks\" section\n\n## Completion Message\n\n```\nTrack created successfully!\n\nTrack ID: {trackId}\nLocation: conductor\u002Ftracks\u002F{trackId}\u002F\n\nFiles created:\n- spec.md - Requirements specification\n- plan.md - Phased implementation plan\n- metadata.json - Track metadata\n- index.md - Track navigation\n\nNext steps:\n1. Review spec.md and plan.md, make any edits\n2. Run \u002Fconductor:implement {trackId} to start implementation\n3. Run \u002Fconductor:status to see project progress\n```\n\n## Error Handling\n\n- If directory creation fails: Halt and report, do not register in tracks.md\n- If any file write fails: Clean up partial track, report error\n- If tracks.md update fails: Warn user to manually register track\n","# New Track\n\nCreate a new track (feature, bug fix, chore, or refactor) with a detailed specification and phased implementation plan.\n\n## Use this skill when\n\n- Working on new track tasks or workflows\n- Needing guidance, best practices, or checklists for new track\n\n## Do not use this skill when\n\n- The task is unrelated to new 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\u002Fproduct.md` exists\n   - Check `conductor\u002Ftech-stack.md` exists\n   - Check `conductor\u002Fworkflow.md` exists\n   - If missing: Display error and suggest running `\u002Fconductor:setup` first\n\n2. Load context files:\n   - Read `conductor\u002Fproduct.md` for product context\n   - Read `conductor\u002Ftech-stack.md` for technical context\n   - Read `conductor\u002Fworkflow.md` for TDD\u002Fcommit preferences\n\n## Track Classification\n\nDetermine track type based on description or ask user:\n\n```\nWhat type of track is this?\n\n1. Feature - New functionality\n2. Bug - Fix for existing issue\n3. Chore - Maintenance, dependencies, config\n4. Refactor - Code improvement without behavior change\n```\n\n## Interactive Specification Gathering\n\n**CRITICAL RULES:**\n\n- Ask ONE question per turn\n- Wait for user response before proceeding\n- Tailor questions based on track type\n- Maximum 6 questions total\n\n### For Feature Tracks\n\n**Q1: Feature Summary**\n\n```\nDescribe the feature in 1-2 sentences.\n[If argument provided, confirm: \"You want to: {argument}. Is this correct?\"]\n```\n\n**Q2: User Story**\n\n```\nWho benefits and how?\n\nFormat: As a [user type], I want to [action] so that [benefit].\n```\n\n**Q3: Acceptance Criteria**\n\n```\nWhat must be true for this feature to be complete?\n\nList 3-5 acceptance criteria (one per line):\n```\n\n**Q4: Dependencies**\n\n```\nDoes this depend on any existing code, APIs, or other tracks?\n\n1. No dependencies\n2. Depends on existing code (specify)\n3. Depends on incomplete track (specify)\n```\n\n**Q5: Scope Boundaries**\n\n```\nWhat is explicitly OUT of scope for this track?\n(Helps prevent scope creep)\n```\n\n**Q6: Technical Considerations (optional)**\n\n```\nAny specific technical approach or constraints?\n(Press enter to skip)\n```\n\n### For Bug Tracks\n\n**Q1: Bug Summary**\n\n```\nWhat is broken?\n[If argument provided, confirm]\n```\n\n**Q2: Steps to Reproduce**\n\n```\nHow can this bug be reproduced?\nList steps:\n```\n\n**Q3: Expected vs Actual Behavior**\n\n```\nWhat should happen vs what actually happens?\n```\n\n**Q4: Affected Areas**\n\n```\nWhat parts of the system are affected?\n```\n\n**Q5: Root Cause Hypothesis (optional)**\n\n```\nAny hypothesis about the cause?\n(Press enter to skip)\n```\n\n### For Chore\u002FRefactor Tracks\n\n**Q1: Task Summary**\n\n```\nWhat needs to be done?\n[If argument provided, confirm]\n```\n\n**Q2: Motivation**\n\n```\nWhy is this work needed?\n```\n\n**Q3: Success Criteria**\n\n```\nHow will we know this is complete?\n```\n\n**Q4: Risk Assessment**\n\n```\nWhat could go wrong? Any risky changes?\n```\n\n## Track ID Generation\n\nGenerate track ID in format: `{shortname}_{YYYYMMDD}`\n\n- Extract shortname from feature\u002Fbug summary (2-3 words, lowercase, hyphenated)\n- Use current date\n- Example: `user-auth_20250115`, `nav-bug_20250115`\n\nValidate uniqueness:\n\n- Check `conductor\u002Ftracks.md` for existing IDs\n- If collision, append counter: `user-auth_20250115_2`\n\n## Specification Generation\n\nCreate `conductor\u002Ftracks\u002F{trackId}\u002Fspec.md`:\n\n```markdown\n# Specification: {Track Title}\n\n**Track ID:** {trackId}\n**Type:** {Feature|Bug|Chore|Refactor}\n**Created:** {YYYY-MM-DD}\n**Status:** Draft\n\n## Summary\n\n{1-2 sentence summary}\n\n## Context\n\n{Product context from product.md relevant to this track}\n\n## User Story (for features)\n\nAs a {user}, I want to {action} so that {benefit}.\n\n## Problem Description (for bugs)\n\n{Bug description, steps to reproduce}\n\n## Acceptance Criteria\n\n- [ ] {Criterion 1}\n- [ ] {Criterion 2}\n- [ ] {Criterion 3}\n\n## Dependencies\n\n{List dependencies or \"None\"}\n\n## Out of Scope\n\n{Explicit exclusions}\n\n## Technical Notes\n\n{Technical considerations or \"None specified\"}\n\n---\n\n_Generated by Conductor. Review and edit as needed._\n```\n\n## User Review of Spec\n\nDisplay the generated spec and ask:\n\n```\nHere is the specification I've generated:\n\n{spec content}\n\nIs this specification correct?\n1. Yes, proceed to plan generation\n2. No, let me edit (opens for inline edits)\n3. Start over with different inputs\n```\n\n## Plan Generation\n\nAfter spec approval, generate `conductor\u002Ftracks\u002F{trackId}\u002Fplan.md`:\n\n### Plan Structure\n\n```markdown\n# Implementation Plan: {Track Title}\n\n**Track ID:** {trackId}\n**Spec:** spec.md\n**Created:** {YYYY-MM-DD}\n**Status:** [ ] Not Started\n\n## Overview\n\n{Brief summary of implementation approach}\n\n## Phase 1: {Phase Name}\n\n{Phase description}\n\n### Tasks\n\n- [ ] Task 1.1: {Description}\n- [ ] Task 1.2: {Description}\n- [ ] Task 1.3: {Description}\n\n### Verification\n\n- [ ] {Verification step for phase 1}\n\n## Phase 2: {Phase Name}\n\n{Phase description}\n\n### Tasks\n\n- [ ] Task 2.1: {Description}\n- [ ] Task 2.2: {Description}\n\n### Verification\n\n- [ ] {Verification step for phase 2}\n\n## Phase 3: {Phase Name} (if needed)\n\n...\n\n## Final Verification\n\n- [ ] All acceptance criteria met\n- [ ] Tests passing\n- [ ] Documentation updated (if applicable)\n- [ ] Ready for review\n\n---\n\n_Generated by Conductor. Tasks will be marked [~] in progress and [x] complete._\n```\n\n### Phase Guidelines\n\n- Group related tasks into logical phases\n- Each phase should be independently verifiable\n- Include verification task after each phase\n- TDD tracks: Include test writing tasks before implementation tasks\n- Typical structure:\n  1. **Setup\u002FFoundation** - Initial scaffolding, interfaces\n  2. **Core Implementation** - Main functionality\n  3. **Integration** - Connect with existing system\n  4. **Polish** - Error handling, edge cases, docs\n\n## User Review of Plan\n\nDisplay the generated plan and ask:\n\n```\nHere is the implementation plan:\n\n{plan content}\n\nIs this plan correct?\n1. Yes, create the track\n2. No, let me edit (opens for inline edits)\n3. Add more phases\u002Ftasks\n4. Start over\n```\n\n## Track Creation\n\nAfter plan approval:\n\n1. Create directory structure:\n\n   ```\n   conductor\u002Ftracks\u002F{trackId}\u002F\n   ├── spec.md\n   ├── plan.md\n   ├── metadata.json\n   └── index.md\n   ```\n\n2. Create `metadata.json`:\n\n   ```json\n   {\n     \"id\": \"{trackId}\",\n     \"title\": \"{Track Title}\",\n     \"type\": \"feature|bug|chore|refactor\",\n     \"status\": \"pending\",\n     \"created\": \"ISO_TIMESTAMP\",\n     \"updated\": \"ISO_TIMESTAMP\",\n     \"phases\": {\n       \"total\": N,\n       \"completed\": 0\n     },\n     \"tasks\": {\n       \"total\": M,\n       \"completed\": 0\n     }\n   }\n   ```\n\n3. Create `index.md`:\n\n   ```markdown\n   # Track: {Track Title}\n\n   **ID:** {trackId}\n   **Status:** Pending\n\n   ## Documents\n\n   - Specification\n   - Implementation Plan\n\n   ## Progress\n\n   - Phases: 0\u002F{N} complete\n   - Tasks: 0\u002F{M} complete\n\n   ## Quick Links\n\n   - Back to Tracks\n   - Product Context\n   ```\n\n4. Register in `conductor\u002Ftracks.md`:\n   - Add row to tracks table\n   - Format: `| [ ] | {trackId} | {title} | {created} | {created} |`\n\n5. Update `conductor\u002Findex.md`:\n   - Add track to \"Active Tracks\" section\n\n## Completion Message\n\n```\nTrack created successfully!\n\nTrack ID: {trackId}\nLocation: conductor\u002Ftracks\u002F{trackId}\u002F\n\nFiles created:\n- spec.md - Requirements specification\n- plan.md - Phased implementation plan\n- metadata.json - Track metadata\n- index.md - Track navigation\n\nNext steps:\n1. Review spec.md and plan.md, make any edits\n2. Run \u002Fconductor:implement {trackId} to start implementation\n3. Run \u002Fconductor:status to see project progress\n```\n\n## Error Handling\n\n- If directory creation fails: Halt and report, do not register in tracks.md\n- If any file write fails: Clean up partial track, report error\n- If tracks.md update fails: Warn user to manually register track\n",{"name":5,"risk":30,"source":28,"date_added":38,"description":7},"2026-02-27","main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fglobal\u002Fconductor-new-track","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill conductor-new-track",{"tool":51,"command":52},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill conductor-new-track",{"tool":54,"command":55},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill conductor-new-track","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fglobal\u002Fconductor-new-track\u002FSKILL.md",true,[],[60,83,109,119,132,151],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":71,"publishedAt":33},"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",[66],{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[72,73,74,75,76,77,78,79,80,81,82,29],"wechat search","wechat","search","capabilities","openclaw","design","web search","compliance","web","official","fetch",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":33},"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",[],[90,91,92,93,94,95,74,96,97,98,99,100,101,102,103,104,105,106,107,108],"trend","trend tap","tap","api keys","Bash","time","trending","hacker","aggregator","do","when","brew","live","data","google","install","read","across","api",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":33},"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",[],[116,117,90,101,102,103,104,94,74,106,118,107,108,100,98,97,96,105,95,93],"trend radar","radar","pulse",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":33},"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",[],[126,127,128,129,130,131],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":143,"publishedAt":33},"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",[138],{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[134,80,144,145,146,29,101,147,148,149,92,150,105],"Audio","cli","youtube","images","https","files","pdfs",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":33},"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",[],[153,158,159,160,105,161,148,162,163,164,165,166],"status","play","go","latest","github","discover","control","cmd","volume"]