[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XFS5C671NA62YV97T7GZGS":3,"skill-same:01M6XFS5C671NA62YV97T7GZGS":65},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":14,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M6XFS5C671NA62YV97T7GZGS","context-driven-development",null,"Guide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation.","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\u002Fcopilot\u002Fcontext-driven-development\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"development","context","context driven development","driven","2026","documentation","managed","project documentation","unknown","for","implementing","as","project","structured","artifact","community","alignment","guide","team","code","2026-11-10 10:12:30",false,"---\nname: context-driven-development\ndescription: \"Guide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation.\"\nrisk: unknown\nsource: community\ndate_added: '2026-02-27'\n---\n\n# Context-Driven Development\n\nGuide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation.\n\n## Do not use this skill when\n\n- The task is unrelated to context-driven development\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## Use this skill when\n\n- Setting up new projects with Conductor\n- Understanding the relationship between context artifacts\n- Maintaining consistency across AI-assisted development sessions\n- Onboarding team members to an existing Conductor project\n- Deciding when to update context documents\n- Managing greenfield vs brownfield project contexts\n\n## Core Philosophy\n\nContext-Driven Development treats project context as a first-class artifact managed alongside code. Instead of relying on ad-hoc prompts or scattered documentation, establish a persistent, structured foundation that informs all AI interactions.\n\nKey principles:\n\n1. **Context precedes code**: Define what you're building and how before implementation\n2. **Living documentation**: Context artifacts evolve with the project\n3. **Single source of truth**: One canonical location for each type of information\n4. **AI alignment**: Consistent context produces consistent AI behavior\n\n## The Workflow\n\nFollow the **Context → Spec & Plan → Implement** workflow:\n\n1. **Context Phase**: Establish or verify project context artifacts exist and are current\n2. **Specification Phase**: Define requirements and acceptance criteria for work units\n3. **Planning Phase**: Break specifications into phased, actionable tasks\n4. **Implementation Phase**: Execute tasks following established workflow patterns\n\n## Artifact Relationships\n\n### product.md - Defines WHAT and WHY\n\nPurpose: Captures product vision, goals, target users, and business context.\n\nContents:\n\n- Product name and one-line description\n- Problem statement and solution approach\n- Target user personas\n- Core features and capabilities\n- Success metrics and KPIs\n- Product roadmap (high-level)\n\nUpdate when:\n\n- Product vision or goals change\n- New major features are planned\n- Target audience shifts\n- Business priorities evolve\n\n### product-guidelines.md - Defines HOW to Communicate\n\nPurpose: Establishes brand voice, messaging standards, and communication patterns.\n\nContents:\n\n- Brand voice and tone guidelines\n- Terminology and glossary\n- Error message conventions\n- User-facing copy standards\n- Documentation style\n\nUpdate when:\n\n- Brand guidelines change\n- New terminology is introduced\n- Communication patterns need refinement\n\n### tech-stack.md - Defines WITH WHAT\n\nPurpose: Documents technology choices, dependencies, and architectural decisions.\n\nContents:\n\n- Primary languages and frameworks\n- Key dependencies with versions\n- Infrastructure and deployment targets\n- Development tools and environment\n- Testing frameworks\n- Code quality tools\n\nUpdate when:\n\n- Adding new dependencies\n- Upgrading major versions\n- Changing infrastructure\n- Adopting new tools or patterns\n\n### workflow.md - Defines HOW to Work\n\nPurpose: Establishes development practices, quality gates, and team workflows.\n\nContents:\n\n- Development methodology (TDD, etc.)\n- Git workflow and commit conventions\n- Code review requirements\n- Testing requirements and coverage targets\n- Quality assurance gates\n- Deployment procedures\n\nUpdate when:\n\n- Team practices evolve\n- Quality standards change\n- New workflow patterns are adopted\n\n### tracks.md - Tracks WHAT'S HAPPENING\n\nPurpose: Registry of all work units with status and metadata.\n\nContents:\n\n- Active tracks with current status\n- Completed tracks with completion dates\n- Track metadata (type, priority, assignee)\n- Links to individual track directories\n\nUpdate when:\n\n- New tracks are created\n- Track status changes\n- Tracks are completed or archived\n\n## Context Maintenance Principles\n\n### Keep Artifacts Synchronized\n\nEnsure changes in one artifact reflect in related documents:\n\n- New feature in product.md → Update tech-stack.md if new dependencies needed\n- Completed track → Update product.md to reflect new capabilities\n- Workflow change → Update all affected track plans\n\n### Update tech-stack.md When Adding Dependencies\n\nBefore adding any new dependency:\n\n1. Check if existing dependencies solve the need\n2. Document the rationale for new dependencies\n3. Add version constraints\n4. Note any configuration requirements\n\n### Update product.md When Features Complete\n\nAfter completing a feature track:\n\n1. Move feature from \"planned\" to \"implemented\" in product.md\n2. Update any affected success metrics\n3. Document any scope changes from original plan\n\n### Verify Context Before Implementation\n\nBefore starting any track:\n\n1. Read all context artifacts\n2. Flag any outdated information\n3. Propose updates before proceeding\n4. Confirm context accuracy with stakeholders\n\n## Greenfield vs Brownfield Handling\n\n### Greenfield Projects (New)\n\nFor new projects:\n\n1. Run `\u002Fconductor:setup` to create all artifacts interactively\n2. Answer questions about product vision, tech preferences, and workflow\n3. Generate initial style guides for chosen languages\n4. Create empty tracks registry\n\nCharacteristics:\n\n- Full control over context structure\n- Define standards before code exists\n- Establish patterns early\n\n### Brownfield Projects (Existing)\n\nFor existing codebases:\n\n1. Run `\u002Fconductor:setup` with existing codebase detection\n2. System analyzes existing code, configs, and documentation\n3. Pre-populate artifacts based on discovered patterns\n4. Review and refine generated context\n\nCharacteristics:\n\n- Extract implicit context from existing code\n- Reconcile existing patterns with desired patterns\n- Document technical debt and modernization plans\n- Preserve working patterns while establishing standards\n\n## Benefits\n\n### Team Alignment\n\n- New team members onboard faster with explicit context\n- Consistent terminology and conventions across the team\n- Shared understanding of product goals and technical decisions\n\n### AI Consistency\n\n- AI assistants produce aligned outputs across sessions\n- Reduced need to re-explain context in each interaction\n- Predictable behavior based on documented standards\n\n### Institutional Memory\n\n- Decisions and rationale are preserved\n- Context survives team changes\n- Historical context informs future decisions\n\n### Quality Assurance\n\n- Standards are explicit and verifiable\n- Deviations from context are detectable\n- Quality gates are documented and enforceable\n\n## Directory Structure\n\n```\nconductor\u002F\n├── index.md              # Navigation hub linking all artifacts\n├── product.md            # Product vision and goals\n├── product-guidelines.md # Communication standards\n├── tech-stack.md         # Technology preferences\n├── workflow.md           # Development practices\n├── tracks.md             # Work unit registry\n├── setup_state.json      # Resumable setup state\n├── code_styleguides\u002F     # Language-specific conventions\n│   ├── python.md\n│   ├── typescript.md\n│   └── ...\n└── tracks\u002F\n    └── \u003Ctrack-id>\u002F\n        ├── spec.md\n        ├── plan.md\n        ├── metadata.json\n        └── index.md\n```\n\n## Context Lifecycle\n\n1. **Creation**: Initial setup via `\u002Fconductor:setup`\n2. **Validation**: Verify before each track\n3. **Evolution**: Update as project grows\n4. **Synchronization**: Keep artifacts aligned\n5. **Archival**: Document historical decisions\n\n## Context Validation Checklist\n\nBefore starting implementation on any track, validate context:\n\n### Product Context\n\n- [ ] product.md reflects current product vision\n- [ ] Target users are accurately described\n- [ ] Feature list is up to date\n- [ ] Success metrics are defined\n\n### Technical Context\n\n- [ ] tech-stack.md lists all current dependencies\n- [ ] Version numbers are accurate\n- [ ] Infrastructure targets are correct\n- [ ] Development tools are documented\n\n### Workflow Context\n\n- [ ] workflow.md describes current practices\n- [ ] Quality gates are defined\n- [ ] Coverage targets are specified\n- [ ] Commit conventions are documented\n\n### Track Context\n\n- [ ] tracks.md shows all active work\n- [ ] No stale or abandoned tracks\n- [ ] Dependencies between tracks are noted\n\n## Common Anti-Patterns\n\nAvoid these context management mistakes:\n\n### Stale Context\n\nProblem: Context documents become outdated and misleading.\nSolution: Update context as part of each track's completion process.\n\n### Context Sprawl\n\nProblem: Information scattered across multiple locations.\nSolution: Use the defined artifact structure; resist creating new document types.\n\n### Implicit Context\n\nProblem: Relying on knowledge not captured in artifacts.\nSolution: If you reference something repeatedly, add it to the appropriate artifact.\n\n### Context Hoarding\n\nProblem: One person maintains context without team input.\nSolution: Review context artifacts in pull requests; make updates collaborative.\n\n### Over-Specification\n\nProblem: Context becomes so detailed it's impossible to maintain.\nSolution: Keep artifacts focused on decisions that affect AI behavior and team alignment.\n\n## Integration with Development Tools\n\n### IDE Integration\n\nConfigure your IDE to display context files prominently:\n\n- Pin conductor\u002Fproduct.md for quick reference\n- Add tech-stack.md to project notes\n- Create snippets for common patterns from style guides\n\n### Git Hooks\n\nConsider pre-commit hooks that:\n\n- Warn when dependencies change without tech-stack.md update\n- Remind to update product.md when feature branches merge\n- Validate context artifact syntax\n\n### CI\u002FCD Integration\n\nInclude context validation in pipelines:\n\n- Check tech-stack.md matches actual dependencies\n- Verify links in context documents resolve\n- Ensure tracks.md status matches git branch state\n\n## Session Continuity\n\nConductor supports multi-session development through context persistence:\n\n### Starting a New Session\n\n1. Read index.md to orient yourself\n2. Check tracks.md for active work\n3. Review relevant track's plan.md for current task\n4. Verify context artifacts are current\n\n### Ending a Session\n\n1. Update plan.md with current progress\n2. Note any blockers or decisions made\n3. Commit in-progress work with clear status\n4. Update tracks.md if status changed\n\n### Handling Interruptions\n\nIf interrupted mid-task:\n\n1. Mark task as `[~]` with note about stopping point\n2. Commit work-in-progress to feature branch\n3. Document any uncommitted decisions in plan.md\n\n## Best Practices\n\n1. **Read context first**: Always read relevant artifacts before starting work\n2. **Small updates**: Make incremental context changes, not massive rewrites\n3. **Link decisions**: Reference context when making implementation choices\n4. **Version context**: Commit context changes alongside code changes\n5. **Review context**: Include context artifact reviews in code reviews\n6. **Validate regularly**: Run context validation checklist before major work\n7. **Communicate changes**: Notify team when context artifacts change significantly\n8. **Preserve history**: Use git to track context evolution over time\n9. **Question staleness**: If context feels wrong, investigate and update\n10. **Keep it actionable**: Every context item should inform a decision or behavior\n","# Context-Driven Development\n\nGuide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation.\n\n## Do not use this skill when\n\n- The task is unrelated to context-driven development\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## Use this skill when\n\n- Setting up new projects with Conductor\n- Understanding the relationship between context artifacts\n- Maintaining consistency across AI-assisted development sessions\n- Onboarding team members to an existing Conductor project\n- Deciding when to update context documents\n- Managing greenfield vs brownfield project contexts\n\n## Core Philosophy\n\nContext-Driven Development treats project context as a first-class artifact managed alongside code. Instead of relying on ad-hoc prompts or scattered documentation, establish a persistent, structured foundation that informs all AI interactions.\n\nKey principles:\n\n1. **Context precedes code**: Define what you're building and how before implementation\n2. **Living documentation**: Context artifacts evolve with the project\n3. **Single source of truth**: One canonical location for each type of information\n4. **AI alignment**: Consistent context produces consistent AI behavior\n\n## The Workflow\n\nFollow the **Context → Spec & Plan → Implement** workflow:\n\n1. **Context Phase**: Establish or verify project context artifacts exist and are current\n2. **Specification Phase**: Define requirements and acceptance criteria for work units\n3. **Planning Phase**: Break specifications into phased, actionable tasks\n4. **Implementation Phase**: Execute tasks following established workflow patterns\n\n## Artifact Relationships\n\n### product.md - Defines WHAT and WHY\n\nPurpose: Captures product vision, goals, target users, and business context.\n\nContents:\n\n- Product name and one-line description\n- Problem statement and solution approach\n- Target user personas\n- Core features and capabilities\n- Success metrics and KPIs\n- Product roadmap (high-level)\n\nUpdate when:\n\n- Product vision or goals change\n- New major features are planned\n- Target audience shifts\n- Business priorities evolve\n\n### product-guidelines.md - Defines HOW to Communicate\n\nPurpose: Establishes brand voice, messaging standards, and communication patterns.\n\nContents:\n\n- Brand voice and tone guidelines\n- Terminology and glossary\n- Error message conventions\n- User-facing copy standards\n- Documentation style\n\nUpdate when:\n\n- Brand guidelines change\n- New terminology is introduced\n- Communication patterns need refinement\n\n### tech-stack.md - Defines WITH WHAT\n\nPurpose: Documents technology choices, dependencies, and architectural decisions.\n\nContents:\n\n- Primary languages and frameworks\n- Key dependencies with versions\n- Infrastructure and deployment targets\n- Development tools and environment\n- Testing frameworks\n- Code quality tools\n\nUpdate when:\n\n- Adding new dependencies\n- Upgrading major versions\n- Changing infrastructure\n- Adopting new tools or patterns\n\n### workflow.md - Defines HOW to Work\n\nPurpose: Establishes development practices, quality gates, and team workflows.\n\nContents:\n\n- Development methodology (TDD, etc.)\n- Git workflow and commit conventions\n- Code review requirements\n- Testing requirements and coverage targets\n- Quality assurance gates\n- Deployment procedures\n\nUpdate when:\n\n- Team practices evolve\n- Quality standards change\n- New workflow patterns are adopted\n\n### tracks.md - Tracks WHAT'S HAPPENING\n\nPurpose: Registry of all work units with status and metadata.\n\nContents:\n\n- Active tracks with current status\n- Completed tracks with completion dates\n- Track metadata (type, priority, assignee)\n- Links to individual track directories\n\nUpdate when:\n\n- New tracks are created\n- Track status changes\n- Tracks are completed or archived\n\n## Context Maintenance Principles\n\n### Keep Artifacts Synchronized\n\nEnsure changes in one artifact reflect in related documents:\n\n- New feature in product.md → Update tech-stack.md if new dependencies needed\n- Completed track → Update product.md to reflect new capabilities\n- Workflow change → Update all affected track plans\n\n### Update tech-stack.md When Adding Dependencies\n\nBefore adding any new dependency:\n\n1. Check if existing dependencies solve the need\n2. Document the rationale for new dependencies\n3. Add version constraints\n4. Note any configuration requirements\n\n### Update product.md When Features Complete\n\nAfter completing a feature track:\n\n1. Move feature from \"planned\" to \"implemented\" in product.md\n2. Update any affected success metrics\n3. Document any scope changes from original plan\n\n### Verify Context Before Implementation\n\nBefore starting any track:\n\n1. Read all context artifacts\n2. Flag any outdated information\n3. Propose updates before proceeding\n4. Confirm context accuracy with stakeholders\n\n## Greenfield vs Brownfield Handling\n\n### Greenfield Projects (New)\n\nFor new projects:\n\n1. Run `\u002Fconductor:setup` to create all artifacts interactively\n2. Answer questions about product vision, tech preferences, and workflow\n3. Generate initial style guides for chosen languages\n4. Create empty tracks registry\n\nCharacteristics:\n\n- Full control over context structure\n- Define standards before code exists\n- Establish patterns early\n\n### Brownfield Projects (Existing)\n\nFor existing codebases:\n\n1. Run `\u002Fconductor:setup` with existing codebase detection\n2. System analyzes existing code, configs, and documentation\n3. Pre-populate artifacts based on discovered patterns\n4. Review and refine generated context\n\nCharacteristics:\n\n- Extract implicit context from existing code\n- Reconcile existing patterns with desired patterns\n- Document technical debt and modernization plans\n- Preserve working patterns while establishing standards\n\n## Benefits\n\n### Team Alignment\n\n- New team members onboard faster with explicit context\n- Consistent terminology and conventions across the team\n- Shared understanding of product goals and technical decisions\n\n### AI Consistency\n\n- AI assistants produce aligned outputs across sessions\n- Reduced need to re-explain context in each interaction\n- Predictable behavior based on documented standards\n\n### Institutional Memory\n\n- Decisions and rationale are preserved\n- Context survives team changes\n- Historical context informs future decisions\n\n### Quality Assurance\n\n- Standards are explicit and verifiable\n- Deviations from context are detectable\n- Quality gates are documented and enforceable\n\n## Directory Structure\n\n```\nconductor\u002F\n├── index.md              # Navigation hub linking all artifacts\n├── product.md            # Product vision and goals\n├── product-guidelines.md # Communication standards\n├── tech-stack.md         # Technology preferences\n├── workflow.md           # Development practices\n├── tracks.md             # Work unit registry\n├── setup_state.json      # Resumable setup state\n├── code_styleguides\u002F     # Language-specific conventions\n│   ├── python.md\n│   ├── typescript.md\n│   └── ...\n└── tracks\u002F\n    └── \u003Ctrack-id>\u002F\n        ├── spec.md\n        ├── plan.md\n        ├── metadata.json\n        └── index.md\n```\n\n## Context Lifecycle\n\n1. **Creation**: Initial setup via `\u002Fconductor:setup`\n2. **Validation**: Verify before each track\n3. **Evolution**: Update as project grows\n4. **Synchronization**: Keep artifacts aligned\n5. **Archival**: Document historical decisions\n\n## Context Validation Checklist\n\nBefore starting implementation on any track, validate context:\n\n### Product Context\n\n- [ ] product.md reflects current product vision\n- [ ] Target users are accurately described\n- [ ] Feature list is up to date\n- [ ] Success metrics are defined\n\n### Technical Context\n\n- [ ] tech-stack.md lists all current dependencies\n- [ ] Version numbers are accurate\n- [ ] Infrastructure targets are correct\n- [ ] Development tools are documented\n\n### Workflow Context\n\n- [ ] workflow.md describes current practices\n- [ ] Quality gates are defined\n- [ ] Coverage targets are specified\n- [ ] Commit conventions are documented\n\n### Track Context\n\n- [ ] tracks.md shows all active work\n- [ ] No stale or abandoned tracks\n- [ ] Dependencies between tracks are noted\n\n## Common Anti-Patterns\n\nAvoid these context management mistakes:\n\n### Stale Context\n\nProblem: Context documents become outdated and misleading.\nSolution: Update context as part of each track's completion process.\n\n### Context Sprawl\n\nProblem: Information scattered across multiple locations.\nSolution: Use the defined artifact structure; resist creating new document types.\n\n### Implicit Context\n\nProblem: Relying on knowledge not captured in artifacts.\nSolution: If you reference something repeatedly, add it to the appropriate artifact.\n\n### Context Hoarding\n\nProblem: One person maintains context without team input.\nSolution: Review context artifacts in pull requests; make updates collaborative.\n\n### Over-Specification\n\nProblem: Context becomes so detailed it's impossible to maintain.\nSolution: Keep artifacts focused on decisions that affect AI behavior and team alignment.\n\n## Integration with Development Tools\n\n### IDE Integration\n\nConfigure your IDE to display context files prominently:\n\n- Pin conductor\u002Fproduct.md for quick reference\n- Add tech-stack.md to project notes\n- Create snippets for common patterns from style guides\n\n### Git Hooks\n\nConsider pre-commit hooks that:\n\n- Warn when dependencies change without tech-stack.md update\n- Remind to update product.md when feature branches merge\n- Validate context artifact syntax\n\n### CI\u002FCD Integration\n\nInclude context validation in pipelines:\n\n- Check tech-stack.md matches actual dependencies\n- Verify links in context documents resolve\n- Ensure tracks.md status matches git branch state\n\n## Session Continuity\n\nConductor supports multi-session development through context persistence:\n\n### Starting a New Session\n\n1. Read index.md to orient yourself\n2. Check tracks.md for active work\n3. Review relevant track's plan.md for current task\n4. Verify context artifacts are current\n\n### Ending a Session\n\n1. Update plan.md with current progress\n2. Note any blockers or decisions made\n3. Commit in-progress work with clear status\n4. Update tracks.md if status changed\n\n### Handling Interruptions\n\nIf interrupted mid-task:\n\n1. Mark task as `[~]` with note about stopping point\n2. Commit work-in-progress to feature branch\n3. Document any uncommitted decisions in plan.md\n\n## Best Practices\n\n1. **Read context first**: Always read relevant artifacts before starting work\n2. **Small updates**: Make incremental context changes, not massive rewrites\n3. **Link decisions**: Reference context when making implementation choices\n4. **Version context**: Commit context changes alongside code changes\n5. **Review context**: Include context artifact reviews in code reviews\n6. **Validate regularly**: Run context validation checklist before major work\n7. **Communicate changes**: Notify team when context artifacts change significantly\n8. **Preserve history**: Use git to track context evolution over time\n9. **Question staleness**: If context feels wrong, investigate and update\n10. **Keep it actionable**: Every context item should inform a decision or behavior\n",{"name":5,"risk":27,"source":34,"date_added":44,"description":7},"2026-02-27","main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fcopilot\u002Fcontext-driven-development","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill context-driven-development",{"tool":57,"command":58},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill context-driven-development",{"tool":60,"command":61},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill context-driven-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Fcontext-driven-development\u002FSKILL.md",true,[],[66,90,116,126,139,158],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":77,"publishedAt":39},"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",[72],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[78,79,80,81,82,83,84,85,86,87,88,89],"wechat search","wechat","search","capabilities","openclaw","design","web search","compliance","web","official","fetch","with",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":39},"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",[],[97,98,99,100,101,102,80,103,104,105,106,107,108,109,110,111,112,113,114,115],"trend","trend tap","tap","api keys","Bash","time","trending","hacker","aggregator","do","when","brew","live","data","google","install","read","across","api",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":39},"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",[],[123,124,97,108,109,110,111,101,80,113,125,114,115,107,105,104,103,112,102,100],"trend radar","radar","pulse",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":39},"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",[],[133,134,135,136,137,138],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":150,"publishedAt":39},"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",[145],{"categoryNo":146,"categoryName":147,"taxonomyType":148,"taxonomyTypeDesc":149},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[141,86,151,152,153,89,108,154,155,156,99,157,112],"Audio","cli","youtube","images","https","files","pdfs",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":39},"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",[],[160,165,166,167,112,168,155,169,170,171,172,173],"status","play","go","latest","github","discover","control","cmd","volume"]