[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DBYXWQGB95SSYT3FN3H4ZF":3,"skill-same:01M6DBYXWQGB95SSYT3FN3H4ZF":53},{"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":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":14,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M6DBYXWQGB95SSYT3FN3H4ZF","source-command-plan",null,"Restate requirements, assess risks, and create step-by-step implementation plan. WAIT for user CONFIRM before touching any code.","Prekzursil\u002Fagent-skills-toolchain","Prekzursil","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54636077?v=4","01M6DACZ1PCQHD99SCR1YXG28B","Andrei Mihai Visalon","01M6DACZ670WZF535V3WYYSS4Z",0,"MIT","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsource-command-plan\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27],"plan","command","source command plan","create","code","wait for","user","implementation","requirements","2026-11-10 10:12:30",false,"---\nname: \"source-command-plan\"\ndescription: \"Restate requirements, assess risks, and create step-by-step implementation plan. WAIT for user CONFIRM before touching any code.\"\n---\n\n# source-command-plan\n\nUse this skill when the user asks to run the migrated source command `plan`.\n\n## Command Template\n\n# Plan Command\n\nThis command invokes the **planner** agent to create a comprehensive implementation plan before writing any code.\n\n## What This Command Does\n\n1. **Restate Requirements** - Clarify what needs to be built\n2. **Identify Risks** - Surface potential issues and blockers\n3. **Create Step Plan** - Break down implementation into phases\n4. **Wait for Confirmation** - MUST receive user approval before proceeding\n\n## When to Use\n\nUse `\u002Fplan` when:\n- Starting a new feature\n- Making significant architectural changes\n- Working on complex refactoring\n- Multiple files\u002Fcomponents will be affected\n- Requirements are unclear or ambiguous\n\n## How It Works\n\nThe planner agent will:\n\n1. **Analyze the request** and restate requirements in clear terms\n2. **Break down into phases** with specific, actionable steps\n3. **Identify dependencies** between components\n4. **Assess risks** and potential blockers\n5. **Estimate complexity** (High\u002FMedium\u002FLow)\n6. **Present the plan** and WAIT for your explicit confirmation\n\n## Example Usage\n\n```\nUser: \u002Fplan I need to add real-time notifications when markets resolve\n\nAgent (planner):\n# Implementation Plan: Real-Time Market Resolution Notifications\n\n## Requirements Restatement\n- Send notifications to users when markets they're watching resolve\n- Support multiple notification channels (in-app, email, webhook)\n- Ensure notifications are delivered reliably\n- Include market outcome and user's position result\n\n## Implementation Phases\n\n### Phase 1: Database Schema\n- Add notifications table with columns: id, user_id, market_id, type, status, created_at\n- Add user_notification_preferences table for channel preferences\n- Create indexes on user_id and market_id for performance\n\n### Phase 2: Notification Service\n- Create notification service in lib\u002Fnotifications.ts\n- Implement notification queue using BullMQ\u002FRedis\n- Add retry logic for failed deliveries\n- Create notification templates\n\n### Phase 3: Integration Points\n- Hook into market resolution logic (when status changes to \"resolved\")\n- Query all users with positions in market\n- Enqueue notifications for each user\n\n### Phase 4: Frontend Components\n- Create NotificationBell component in header\n- Add NotificationList modal\n- Implement real-time updates via Supabase subscriptions\n- Add notification preferences page\n\n## Dependencies\n- Redis (for queue)\n- Email service (SendGrid\u002FResend)\n- Supabase real-time subscriptions\n\n## Risks\n- HIGH: Email deliverability (SPF\u002FDKIM required)\n- MEDIUM: Performance with 1000+ users per market\n- MEDIUM: Notification spam if markets resolve frequently\n- LOW: Real-time subscription overhead\n\n## Estimated Complexity: MEDIUM\n- Backend: 4-6 hours\n- Frontend: 3-4 hours\n- Testing: 2-3 hours\n- Total: 9-13 hours\n\n**WAITING FOR CONFIRMATION**: Proceed with this plan? (yes\u002Fno\u002Fmodify)\n```\n\n## Important Notes\n\n**CRITICAL**: The planner agent will **NOT** write any code until you explicitly confirm the plan with \"yes\" or \"proceed\" or similar affirmative response.\n\nIf you want changes, respond with:\n- \"modify: [your changes]\"\n- \"different approach: [alternative]\"\n- \"skip phase 2 and do phase 3 first\"\n\n## Integration with Other Commands\n\nAfter planning:\n- Use `\u002Ftdd` to implement with test-driven development\n- Use `\u002Fbuild-fix` if build errors occur\n- Use `\u002Fcode-review` to review completed implementation\n\n## Related Agents\n\nThis command invokes the `planner` agent provided by ECC.\n\nFor manual installs, the source file lives at:\n`agents\u002Fplanner.md`\n","# source-command-plan\n\nUse this skill when the user asks to run the migrated source command `plan`.\n\n## Command Template\n\n# Plan Command\n\nThis command invokes the **planner** agent to create a comprehensive implementation plan before writing any code.\n\n## What This Command Does\n\n1. **Restate Requirements** - Clarify what needs to be built\n2. **Identify Risks** - Surface potential issues and blockers\n3. **Create Step Plan** - Break down implementation into phases\n4. **Wait for Confirmation** - MUST receive user approval before proceeding\n\n## When to Use\n\nUse `\u002Fplan` when:\n- Starting a new feature\n- Making significant architectural changes\n- Working on complex refactoring\n- Multiple files\u002Fcomponents will be affected\n- Requirements are unclear or ambiguous\n\n## How It Works\n\nThe planner agent will:\n\n1. **Analyze the request** and restate requirements in clear terms\n2. **Break down into phases** with specific, actionable steps\n3. **Identify dependencies** between components\n4. **Assess risks** and potential blockers\n5. **Estimate complexity** (High\u002FMedium\u002FLow)\n6. **Present the plan** and WAIT for your explicit confirmation\n\n## Example Usage\n\n```\nUser: \u002Fplan I need to add real-time notifications when markets resolve\n\nAgent (planner):\n# Implementation Plan: Real-Time Market Resolution Notifications\n\n## Requirements Restatement\n- Send notifications to users when markets they're watching resolve\n- Support multiple notification channels (in-app, email, webhook)\n- Ensure notifications are delivered reliably\n- Include market outcome and user's position result\n\n## Implementation Phases\n\n### Phase 1: Database Schema\n- Add notifications table with columns: id, user_id, market_id, type, status, created_at\n- Add user_notification_preferences table for channel preferences\n- Create indexes on user_id and market_id for performance\n\n### Phase 2: Notification Service\n- Create notification service in lib\u002Fnotifications.ts\n- Implement notification queue using BullMQ\u002FRedis\n- Add retry logic for failed deliveries\n- Create notification templates\n\n### Phase 3: Integration Points\n- Hook into market resolution logic (when status changes to \"resolved\")\n- Query all users with positions in market\n- Enqueue notifications for each user\n\n### Phase 4: Frontend Components\n- Create NotificationBell component in header\n- Add NotificationList modal\n- Implement real-time updates via Supabase subscriptions\n- Add notification preferences page\n\n## Dependencies\n- Redis (for queue)\n- Email service (SendGrid\u002FResend)\n- Supabase real-time subscriptions\n\n## Risks\n- HIGH: Email deliverability (SPF\u002FDKIM required)\n- MEDIUM: Performance with 1000+ users per market\n- MEDIUM: Notification spam if markets resolve frequently\n- LOW: Real-time subscription overhead\n\n## Estimated Complexity: MEDIUM\n- Backend: 4-6 hours\n- Frontend: 3-4 hours\n- Testing: 2-3 hours\n- Total: 9-13 hours\n\n**WAITING FOR CONFIRMATION**: Proceed with this plan? (yes\u002Fno\u002Fmodify)\n```\n\n## Important Notes\n\n**CRITICAL**: The planner agent will **NOT** write any code until you explicitly confirm the plan with \"yes\" or \"proceed\" or similar affirmative response.\n\nIf you want changes, respond with:\n- \"modify: [your changes]\"\n- \"different approach: [alternative]\"\n- \"skip phase 2 and do phase 3 first\"\n\n## Integration with Other Commands\n\nAfter planning:\n- Use `\u002Ftdd` to implement with test-driven development\n- Use `\u002Fbuild-fix` if build errors occur\n- Use `\u002Fcode-review` to review completed implementation\n\n## Related Agents\n\nThis command invokes the `planner` agent provided by ECC.\n\nFor manual installs, the source file lives at:\n`agents\u002Fplanner.md`\n",{"name":5,"description":7},"main","a298c929b6cbd662e1fce54302ce520d5ceea1a5",".agents\u002Fskills\u002Fsource-command-plan","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain","https:\u002F\u002Fgithub.com\u002FPrekzursil","2026-11-02 14:30:57",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add Prekzursil\u002Fagent-skills-toolchain --skill source-command-plan",{"tool":45,"command":46},"bunx","bunx skills add Prekzursil\u002Fagent-skills-toolchain --skill source-command-plan",{"tool":48,"command":49},"pnpm","pnpm dlx skills add Prekzursil\u002Fagent-skills-toolchain --skill source-command-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsource-command-plan\u002FSKILL.md",true,[],[54,75,106,133,147,162],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":28},"01M6DF7D7478R55P46REYH4QAC","clarify-requirements","Resolve genuine pre-execution ambiguity by scanning repo context, generating 1-6 grounded options, and asking 1-3 focused questions via AskUserQuestion. NOT for mid-task use (injection risk); NOT when the goal is already unambiguous; use to disambiguate vague prompts before any file edits.","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Fworkspace-hooks\u002Fskills\u002Fclarify-requirements\u002FSKILL.md",[],[61,62,27,63,64,65,66,67,68,69,70,71,72,73,74],"clarify requirements","clarify","risk","options","task","prompts","goal","scanning","use","context","repo","injection","execution","file",{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":86,"publishedAt":28},"01M6DF79CA4BHJS66J8EZDBPWJ","openmm-md","Run FREE, open-source, Windows-native GPU molecular dynamics via the openmm-md MCP (OpenMM + CUDA on the local NVIDIA GPU). Use for protein \u002F protein-ligand MD when you want a free stack or are on Windows without a Schrodinger license. Covers the full workflow (prepare, solvate, minimize, equilibrate, production, analyze, mmgbsa) AND an honest decision guide vs Schrodinger Desmond, including how to run Desmond legitimately on Linux or a cloud GPU with a real license. This is a deliberately LESSER free alternative and does NOT replace the schrodinger MCP tools. Do NOT use it to pick a free tool when a validated FEP+, WaterMap, IFD-MD, or Prime MM-GBSA result is actually required.","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Fmcp\u002Fopenmm-md-mcp\u002Fskill\u002Fopenmm-md\u002FSKILL.md",[81],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[87,88,89,90,91,92,93,94,95,96,97,98,99,100,69,101,102,103,104,105],"openmm md","how","decision","pick","linux","analyze","tool","stack","open","NVIDIA","gpu","license","workflow","windows","free","molecular dynamics","local","do","MCP",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":118,"publishedAt":28},"01M6DF76C1MG85VEWP8VZCBNMN","visual-review","Take screenshots of web pages and UI using Playwright for visual review and iteration","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fvisual-review\u002FSKILL.md",[112,115],{"categoryNo":113,"categoryName":114,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":116,"categoryName":117,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000008","测试与质量",[119,120,121,122,123,124,125,126,127,128,88,129,130,131,132],"review","visual","visual review","pages","web","false","iteration","take","check","slides","ui","screenshot","playwright","screenshots",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":28},"01M6DF73AQVCBZKEN0YXEX9FXP","status","Diagnostic status report — shows metaswarm installation state, project setup, and potential issues","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fstatus\u002FSKILL.md",[],[135,140,141,142,143,144,145,146],"setup","report","project","installation","project setup","issues","state",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":154,"publishedAt":28},"01M6DF6X6C2XB0P6GX76P7TTYV","start","Use when starting work on any task, when the user mentions metaswarm, or when the user wants to begin tracked development work","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fstart\u002FSKILL.md",[153],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[149,155,65,156,157,158,69,25,159,160,161],"start issue","issue","ready","work on issue","work","work on","development",{"skillNo":163,"name":140,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":28},"01M6DF6QMJ9AJKFKHHKRT005PQ","Interactive project setup — detects your project, configures metaswarm, writes project-local files","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fsetup\u002FSKILL.md",[],[140,142,103,168,144,169],"files","interactive"]