[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CSKTD47WTKGNF90849DBQ2":3,"skill-same:01M6CSKTD47WTKGNF90849DBQ2":63},{"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":23,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M6CSKTD47WTKGNF90849DBQ2","conductor-implement",null,"Execute tasks from a track's implementation plan following TDD workflow","Sam-06060\u002Fjarvis-assistant","Sam-06060","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F208600848?v=4","01M6CRKT7C7FXD21V6HXF293S0","Samson Frank Ganta","01M6CRKTBEKYFD8YX5Z1GT99EE",6,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fconductor-implement\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33],"implement","conductor implement","tdd","workflow","tasks","tdd workflow","plan","execute","implementation","community","2026-11-10 10:12:30",false,"---\nname: conductor-implement\ndescription: \"Execute tasks from a track's implementation plan following TDD workflow\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Implement Track\n\nExecute tasks from a track's implementation plan, following the workflow rules defined in `conductor\u002Fworkflow.md`.\n\n## Use this skill when\n\n- Working on implement track tasks or workflows\n- Needing guidance, best practices, or checklists for implement track\n\n## Do not use this skill when\n\n- The task is unrelated to implement 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\u002Fworkflow.md` exists\n   - Check `conductor\u002Ftracks.md` exists\n   - If missing: Display error and suggest running `\u002Fconductor:setup` first\n\n2. Load workflow configuration:\n   - Read `conductor\u002Fworkflow.md`\n   - Parse TDD strictness level\n   - Parse commit strategy\n   - Parse verification checkpoint rules\n\n## Track Selection\n\n### If argument provided:\n\n- Validate track exists: `conductor\u002Ftracks\u002F{argument}\u002Fplan.md`\n- If not found: Search for partial matches, suggest corrections\n\n### If no argument:\n\n1. Read `conductor\u002Ftracks.md`\n2. Parse for incomplete tracks (status `[ ]` or `[~]`)\n3. Display selection menu:\n\n   ```\n   Select a track to implement:\n\n   In Progress:\n   1. [~] auth_20250115 - User Authentication (Phase 2, Task 3)\n\n   Pending:\n   2. [ ] nav-fix_20250114 - Navigation Bug Fix\n   3. [ ] dashboard_20250113 - Dashboard Feature\n\n   Enter number or track ID:\n   ```\n\n## Context Loading\n\nLoad all relevant context for implementation:\n\n1. Track documents:\n   - `conductor\u002Ftracks\u002F{trackId}\u002Fspec.md` - Requirements\n   - `conductor\u002Ftracks\u002F{trackId}\u002Fplan.md` - Task list\n   - `conductor\u002Ftracks\u002F{trackId}\u002Fmetadata.json` - Progress state\n\n2. Project context:\n   - `conductor\u002Fproduct.md` - Product understanding\n   - `conductor\u002Ftech-stack.md` - Technical constraints\n   - `conductor\u002Fworkflow.md` - Process rules\n\n3. Code style (if exists):\n   - `conductor\u002Fcode_styleguides\u002F{language}.md`\n\n## Track Status Update\n\nUpdate track to in-progress:\n\n1. In `conductor\u002Ftracks.md`:\n   - Change `[ ]` to `[~]` for this track\n\n2. In `conductor\u002Ftracks\u002F{trackId}\u002Fmetadata.json`:\n   - Set `status: \"in_progress\"`\n   - Update `updated` timestamp\n\n## Task Execution Loop\n\nFor each incomplete task in plan.md (marked with `[ ]`):\n\n### 1. Task Identification\n\nParse plan.md to find next incomplete task:\n\n- Look for lines matching `- [ ] Task X.Y: {description}`\n- Track current phase from structure\n\n### 2. Task Start\n\nMark task as in-progress:\n\n- Update plan.md: Change `[ ]` to `[~]` for current task\n- Announce: \"Starting Task X.Y: {description}\"\n\n### 3. TDD Workflow (if TDD enabled in workflow.md)\n\n**Red Phase - Write Failing Test:**\n\n```\nFollowing TDD workflow for Task X.Y...\n\nStep 1: Writing failing test\n```\n\n- Create test file if needed\n- Write test(s) for the task functionality\n- Run tests to confirm they fail\n- If tests pass unexpectedly: HALT, investigate\n\n**Green Phase - Implement:**\n\n```\nStep 2: Implementing minimal code to pass test\n```\n\n- Write minimum code to make test pass\n- Run tests to confirm they pass\n- If tests fail: Debug and fix\n\n**Refactor Phase:**\n\n```\nStep 3: Refactoring while keeping tests green\n```\n\n- Clean up code\n- Run tests to ensure still passing\n\n### 4. Non-TDD Workflow (if TDD not strict)\n\n- Implement the task directly\n- Run any existing tests\n- Manual verification as needed\n\n### 5. Task Completion\n\n**Commit changes** (following commit strategy from workflow.md):\n\n```bash\ngit add -A\ngit commit -m \"{commit_prefix}: {task description} ({trackId})\"\n```\n\n**Update plan.md:**\n\n- Change `[~]` to `[x]` for completed task\n- Commit plan update:\n\n```bash\ngit add conductor\u002Ftracks\u002F{trackId}\u002Fplan.md\ngit commit -m \"chore: mark task X.Y complete ({trackId})\"\n```\n\n**Update metadata.json:**\n\n- Increment `tasks.completed`\n- Update `updated` timestamp\n\n### 6. Phase Completion Check\n\nAfter each task, check if phase is complete:\n\n- Parse plan.md for phase structure\n- If all tasks in current phase are `[x]`:\n\n**Run phase verification:**\n\n```\nPhase {N} complete. Running verification...\n```\n\n- Execute verification tasks listed for the phase\n- Run full test suite: `npm test` \u002F `pytest` \u002F etc.\n\n**Report and wait for approval:**\n\n```\nPhase {N} Verification Results:\n- All phase tasks: Complete\n- Tests: {passing\u002Ffailing}\n- Verification: {pass\u002Ffail}\n\nApprove to continue to Phase {N+1}?\n1. Yes, continue\n2. No, there are issues to fix\n3. Pause implementation\n```\n\n**CRITICAL: Wait for explicit user approval before proceeding to next phase.**\n\n## Error Handling During Implementation\n\n### On Tool Failure\n\n```\nERROR: {tool} failed with: {error message}\n\nOptions:\n1. Retry the operation\n2. Skip this task and continue\n3. Pause implementation\n4. Revert current task changes\n```\n\n- HALT and present options\n- Do NOT automatically continue\n\n### On Test Failure\n\n```\nTESTS FAILING after Task X.Y\n\nFailed tests:\n- {test name}: {failure reason}\n\nOptions:\n1. Attempt to fix\n2. Rollback task changes\n3. Pause for manual intervention\n```\n\n### On Git Failure\n\n```\nGIT ERROR: {error message}\n\nThis may indicate:\n- Uncommitted changes from outside Conductor\n- Merge conflicts\n- Permission issues\n\nOptions:\n1. Show git status\n2. Attempt to resolve\n3. Pause for manual intervention\n```\n\n## Track Completion\n\nWhen all phases and tasks are complete:\n\n### 1. Final Verification\n\n```\nAll tasks complete. Running final verification...\n```\n\n- Run full test suite\n- Check all acceptance criteria from spec.md\n- Generate verification report\n\n### 2. Update Track Status\n\nIn `conductor\u002Ftracks.md`:\n\n- Change `[~]` to `[x]` for this track\n- Update the \"Updated\" column\n\nIn `conductor\u002Ftracks\u002F{trackId}\u002Fmetadata.json`:\n\n- Set `status: \"complete\"`\n- Set `phases.completed` to total\n- Set `tasks.completed` to total\n- Update `updated` timestamp\n\nIn `conductor\u002Ftracks\u002F{trackId}\u002Fplan.md`:\n\n- Update header status to `[x] Complete`\n\n### 3. Documentation Sync Offer\n\n```\nTrack complete! Would you like to sync documentation?\n\nThis will update:\n- conductor\u002Fproduct.md (if new features added)\n- conductor\u002Ftech-stack.md (if new dependencies added)\n- README.md (if applicable)\n\n1. Yes, sync documentation\n2. No, skip\n```\n\n### 4. Cleanup Offer\n\n```\nTrack {trackId} is complete.\n\nCleanup options:\n1. Archive - Move to conductor\u002Ftracks\u002F_archive\u002F\n2. Delete - Remove track directory\n3. Keep - Leave as-is\n```\n\n### 5. Completion Summary\n\n```\nTrack Complete: {track title}\n\nSummary:\n- Track ID: {trackId}\n- Phases completed: {N}\u002F{N}\n- Tasks completed: {M}\u002F{M}\n- Commits created: {count}\n- Tests: All passing\n\nNext steps:\n- Run \u002Fconductor:status to see project progress\n- Run \u002Fconductor:new-track for next feature\n```\n\n## Progress Tracking\n\nMaintain progress in `metadata.json` throughout:\n\n```json\n{\n  \"id\": \"auth_20250115\",\n  \"title\": \"User Authentication\",\n  \"type\": \"feature\",\n  \"status\": \"in_progress\",\n  \"created\": \"2025-01-15T10:00:00Z\",\n  \"updated\": \"2025-01-15T14:30:00Z\",\n  \"current_phase\": 2,\n  \"current_task\": \"2.3\",\n  \"phases\": {\n    \"total\": 3,\n    \"completed\": 1\n  },\n  \"tasks\": {\n    \"total\": 12,\n    \"completed\": 7\n  },\n  \"commits\": [\n    \"abc1234: feat: add login form (auth_20250115)\",\n    \"def5678: feat: add password validation (auth_20250115)\"\n  ]\n}\n```\n\n## Resumption\n\nIf implementation is paused and resumed:\n\n1. Load `metadata.json` for current state\n2. Find current task from `current_task` field\n3. Check if task is `[~]` in plan.md\n4. Ask user:\n\n   ```\n   Resuming track: {title}\n\n   Last task in progress: Task {X.Y}: {description}\n\n   Options:\n   1. Continue from where we left off\n   2. Restart current task\n   3. Show progress summary first\n   ```\n\n## Critical Rules\n\n1. **NEVER skip verification checkpoints** - Always wait for user approval between phases\n2. **STOP on any failure** - Do not attempt to continue past errors\n3. **Follow workflow.md strictly** - TDD, commit strategy, and verification rules are mandatory\n4. **Keep plan.md updated** - Task status must reflect actual progress\n5. **Commit frequently** - Each task completion should be committed\n6. **Track all commits** - Record commit hashes in metadata.json for potential revert\n","# Implement Track\n\nExecute tasks from a track's implementation plan, following the workflow rules defined in `conductor\u002Fworkflow.md`.\n\n## Use this skill when\n\n- Working on implement track tasks or workflows\n- Needing guidance, best practices, or checklists for implement track\n\n## Do not use this skill when\n\n- The task is unrelated to implement 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\u002Fworkflow.md` exists\n   - Check `conductor\u002Ftracks.md` exists\n   - If missing: Display error and suggest running `\u002Fconductor:setup` first\n\n2. Load workflow configuration:\n   - Read `conductor\u002Fworkflow.md`\n   - Parse TDD strictness level\n   - Parse commit strategy\n   - Parse verification checkpoint rules\n\n## Track Selection\n\n### If argument provided:\n\n- Validate track exists: `conductor\u002Ftracks\u002F{argument}\u002Fplan.md`\n- If not found: Search for partial matches, suggest corrections\n\n### If no argument:\n\n1. Read `conductor\u002Ftracks.md`\n2. Parse for incomplete tracks (status `[ ]` or `[~]`)\n3. Display selection menu:\n\n   ```\n   Select a track to implement:\n\n   In Progress:\n   1. [~] auth_20250115 - User Authentication (Phase 2, Task 3)\n\n   Pending:\n   2. [ ] nav-fix_20250114 - Navigation Bug Fix\n   3. [ ] dashboard_20250113 - Dashboard Feature\n\n   Enter number or track ID:\n   ```\n\n## Context Loading\n\nLoad all relevant context for implementation:\n\n1. Track documents:\n   - `conductor\u002Ftracks\u002F{trackId}\u002Fspec.md` - Requirements\n   - `conductor\u002Ftracks\u002F{trackId}\u002Fplan.md` - Task list\n   - `conductor\u002Ftracks\u002F{trackId}\u002Fmetadata.json` - Progress state\n\n2. Project context:\n   - `conductor\u002Fproduct.md` - Product understanding\n   - `conductor\u002Ftech-stack.md` - Technical constraints\n   - `conductor\u002Fworkflow.md` - Process rules\n\n3. Code style (if exists):\n   - `conductor\u002Fcode_styleguides\u002F{language}.md`\n\n## Track Status Update\n\nUpdate track to in-progress:\n\n1. In `conductor\u002Ftracks.md`:\n   - Change `[ ]` to `[~]` for this track\n\n2. In `conductor\u002Ftracks\u002F{trackId}\u002Fmetadata.json`:\n   - Set `status: \"in_progress\"`\n   - Update `updated` timestamp\n\n## Task Execution Loop\n\nFor each incomplete task in plan.md (marked with `[ ]`):\n\n### 1. Task Identification\n\nParse plan.md to find next incomplete task:\n\n- Look for lines matching `- [ ] Task X.Y: {description}`\n- Track current phase from structure\n\n### 2. Task Start\n\nMark task as in-progress:\n\n- Update plan.md: Change `[ ]` to `[~]` for current task\n- Announce: \"Starting Task X.Y: {description}\"\n\n### 3. TDD Workflow (if TDD enabled in workflow.md)\n\n**Red Phase - Write Failing Test:**\n\n```\nFollowing TDD workflow for Task X.Y...\n\nStep 1: Writing failing test\n```\n\n- Create test file if needed\n- Write test(s) for the task functionality\n- Run tests to confirm they fail\n- If tests pass unexpectedly: HALT, investigate\n\n**Green Phase - Implement:**\n\n```\nStep 2: Implementing minimal code to pass test\n```\n\n- Write minimum code to make test pass\n- Run tests to confirm they pass\n- If tests fail: Debug and fix\n\n**Refactor Phase:**\n\n```\nStep 3: Refactoring while keeping tests green\n```\n\n- Clean up code\n- Run tests to ensure still passing\n\n### 4. Non-TDD Workflow (if TDD not strict)\n\n- Implement the task directly\n- Run any existing tests\n- Manual verification as needed\n\n### 5. Task Completion\n\n**Commit changes** (following commit strategy from workflow.md):\n\n```bash\ngit add -A\ngit commit -m \"{commit_prefix}: {task description} ({trackId})\"\n```\n\n**Update plan.md:**\n\n- Change `[~]` to `[x]` for completed task\n- Commit plan update:\n\n```bash\ngit add conductor\u002Ftracks\u002F{trackId}\u002Fplan.md\ngit commit -m \"chore: mark task X.Y complete ({trackId})\"\n```\n\n**Update metadata.json:**\n\n- Increment `tasks.completed`\n- Update `updated` timestamp\n\n### 6. Phase Completion Check\n\nAfter each task, check if phase is complete:\n\n- Parse plan.md for phase structure\n- If all tasks in current phase are `[x]`:\n\n**Run phase verification:**\n\n```\nPhase {N} complete. Running verification...\n```\n\n- Execute verification tasks listed for the phase\n- Run full test suite: `npm test` \u002F `pytest` \u002F etc.\n\n**Report and wait for approval:**\n\n```\nPhase {N} Verification Results:\n- All phase tasks: Complete\n- Tests: {passing\u002Ffailing}\n- Verification: {pass\u002Ffail}\n\nApprove to continue to Phase {N+1}?\n1. Yes, continue\n2. No, there are issues to fix\n3. Pause implementation\n```\n\n**CRITICAL: Wait for explicit user approval before proceeding to next phase.**\n\n## Error Handling During Implementation\n\n### On Tool Failure\n\n```\nERROR: {tool} failed with: {error message}\n\nOptions:\n1. Retry the operation\n2. Skip this task and continue\n3. Pause implementation\n4. Revert current task changes\n```\n\n- HALT and present options\n- Do NOT automatically continue\n\n### On Test Failure\n\n```\nTESTS FAILING after Task X.Y\n\nFailed tests:\n- {test name}: {failure reason}\n\nOptions:\n1. Attempt to fix\n2. Rollback task changes\n3. Pause for manual intervention\n```\n\n### On Git Failure\n\n```\nGIT ERROR: {error message}\n\nThis may indicate:\n- Uncommitted changes from outside Conductor\n- Merge conflicts\n- Permission issues\n\nOptions:\n1. Show git status\n2. Attempt to resolve\n3. Pause for manual intervention\n```\n\n## Track Completion\n\nWhen all phases and tasks are complete:\n\n### 1. Final Verification\n\n```\nAll tasks complete. Running final verification...\n```\n\n- Run full test suite\n- Check all acceptance criteria from spec.md\n- Generate verification report\n\n### 2. Update Track Status\n\nIn `conductor\u002Ftracks.md`:\n\n- Change `[~]` to `[x]` for this track\n- Update the \"Updated\" column\n\nIn `conductor\u002Ftracks\u002F{trackId}\u002Fmetadata.json`:\n\n- Set `status: \"complete\"`\n- Set `phases.completed` to total\n- Set `tasks.completed` to total\n- Update `updated` timestamp\n\nIn `conductor\u002Ftracks\u002F{trackId}\u002Fplan.md`:\n\n- Update header status to `[x] Complete`\n\n### 3. Documentation Sync Offer\n\n```\nTrack complete! Would you like to sync documentation?\n\nThis will update:\n- conductor\u002Fproduct.md (if new features added)\n- conductor\u002Ftech-stack.md (if new dependencies added)\n- README.md (if applicable)\n\n1. Yes, sync documentation\n2. No, skip\n```\n\n### 4. Cleanup Offer\n\n```\nTrack {trackId} is complete.\n\nCleanup options:\n1. Archive - Move to conductor\u002Ftracks\u002F_archive\u002F\n2. Delete - Remove track directory\n3. Keep - Leave as-is\n```\n\n### 5. Completion Summary\n\n```\nTrack Complete: {track title}\n\nSummary:\n- Track ID: {trackId}\n- Phases completed: {N}\u002F{N}\n- Tasks completed: {M}\u002F{M}\n- Commits created: {count}\n- Tests: All passing\n\nNext steps:\n- Run \u002Fconductor:status to see project progress\n- Run \u002Fconductor:new-track for next feature\n```\n\n## Progress Tracking\n\nMaintain progress in `metadata.json` throughout:\n\n```json\n{\n  \"id\": \"auth_20250115\",\n  \"title\": \"User Authentication\",\n  \"type\": \"feature\",\n  \"status\": \"in_progress\",\n  \"created\": \"2025-01-15T10:00:00Z\",\n  \"updated\": \"2025-01-15T14:30:00Z\",\n  \"current_phase\": 2,\n  \"current_task\": \"2.3\",\n  \"phases\": {\n    \"total\": 3,\n    \"completed\": 1\n  },\n  \"tasks\": {\n    \"total\": 12,\n    \"completed\": 7\n  },\n  \"commits\": [\n    \"abc1234: feat: add login form (auth_20250115)\",\n    \"def5678: feat: add password validation (auth_20250115)\"\n  ]\n}\n```\n\n## Resumption\n\nIf implementation is paused and resumed:\n\n1. Load `metadata.json` for current state\n2. Find current task from `current_task` field\n3. Check if task is `[~]` in plan.md\n4. Ask user:\n\n   ```\n   Resuming track: {title}\n\n   Last task in progress: Task {X.Y}: {description}\n\n   Options:\n   1. Continue from where we left off\n   2. Restart current task\n   3. Show progress summary first\n   ```\n\n## Critical Rules\n\n1. **NEVER skip verification checkpoints** - Always wait for user approval between phases\n2. **STOP on any failure** - Do not attempt to continue past errors\n3. **Follow workflow.md strictly** - TDD, commit strategy, and verification rules are mandatory\n4. **Keep plan.md updated** - Task status must reflect actual progress\n5. **Commit frequently** - Each task completion should be committed\n6. **Track all commits** - Record commit hashes in metadata.json for potential revert\n",{"name":5,"risk":39,"source":33,"date_added":40,"description":7},"critical","2026-02-27","main","a50a3aa6b39fb0e1b7db88bef1bfc9c93606e126","modules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fconductor-implement",0,"https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant","https:\u002F\u002Fgithub.com\u002FSam-06060","Mobile Application Developer | Kotlin | Flutter, KMP, Swfit, Android,Swift UI | Building at Saar It Resources | Creator of Jarvis (AI Assistant)","2026-06-23 05:13:38",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add Sam-06060\u002Fjarvis-assistant --skill conductor-implement",{"tool":55,"command":56},"bunx","bunx skills add Sam-06060\u002Fjarvis-assistant --skill conductor-implement",{"tool":58,"command":59},"pnpm","pnpm dlx skills add Sam-06060\u002Fjarvis-assistant --skill conductor-implement","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fconductor-implement\u002FSKILL.md",true,[],[64,75,91,115,133,160],{"skillNo":65,"name":66,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":72,"publishedAt":34},"01M6GDRVS6FXX3ESH0C9DW01C0","test_skill","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fscratch\u002Ftest_skill\u002FSKILL.md",[69],{"categoryNo":70,"categoryName":71,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[73,74],"Test Skill","test",{"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":81,"publishedAt":34},"01M6GDRQ40HX22MA6XWC31RHHK","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzustand-store-ts\u002FSKILL.md",[],[82,83,84,85,86,87,88,33,89,90],"zustand store ts","zustand","store","with","types","middleware","patterns","create","typescript",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":98,"publishedAt":34},"01M6GDRKEA0WE670SPFWX5GKCN","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoom-automation\u002FSKILL.md",[97],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[99,100,101,102,103,104,105,106,107,108,39,109,110,111,33,112,113,114],"automation","zoom automation","zoom","first","Tools","search","MCP","via","meeting","automate","creation","webinars","composio","recordings","management","tracking",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":122,"publishedAt":34},"01M6GDRFS1452PC71JQ38S24HR","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoho-crm-automation\u002FSKILL.md",[121],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[123,99,124,125,126,127,128,33,104,129,111,130,39,108,103,131,89,28,105,132],"crm automation","zoho crm","crm","zoho crm automation","zoho","leads","contacts","records","update","manage",{"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":142,"publishedAt":34},"01M6GDRCKQBAVTGHX5XBH26KPZ","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzod-validation-expert\u002FSKILL.md",[139],{"categoryNo":140,"categoryName":141,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[143,144,145,146,147,90,148,149,150,151,152,153,85,154,155,156,157,33,158,159],"expert","zod","zod validation expert","validation","react","safe","parsing","errors","schema validation","react hook form","hook","trpc","form","type","next","schema","Next.js",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":167,"publishedAt":34},"01M6GDR658B08K4MY0RWD4A6EH","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzeroize-audit\u002FSKILL.md",[166],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[168,169,170,171,172,173,174,175,33,176,177,178,179,180,181,182,183,184,185,105],"zeroize audit","audit","write","passwords","get","project","c++","activate","assembly","read","Bash","secrets","analysis","data","flow","verification","code","rust"]