[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CSKZG3S954XSWZY0C6JH20":3,"skill-same:01M6CSKZG3S954XSWZY0C6JH20":75},{"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":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":37,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M6CSKZG3S954XSWZY0C6JH20","conductor-new-track",null,"Create a new track with specification and phased implementation plan","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-new-track\u002FSKILL.md",[],[19,20,21,22,23,24,25],"conductor new track","create","plan","phased implementation","implementation","specification","community","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":31,"source":25,"date_added":32,"description":7},"unknown","2026-02-27","main","a50a3aa6b39fb0e1b7db88bef1bfc9c93606e126","modules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fconductor-new-track",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":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add Sam-06060\u002Fjarvis-assistant --skill conductor-new-track",{"tool":47,"command":48},"bunx","bunx skills add Sam-06060\u002Fjarvis-assistant --skill conductor-new-track",{"tool":50,"command":51},"pnpm","pnpm dlx skills add Sam-06060\u002Fjarvis-assistant --skill conductor-new-track","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fconductor-new-track\u002FSKILL.md",true,[55,61,67,71],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"LICENSE.txt","LICENSE","许可证",11358,"https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fweb-artifacts-builder\u002FLICENSE.txt",{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"scripts\u002Fbundle-artifact.sh","SCRIPT","脚本",1518,"https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fweb-artifacts-builder\u002Fscripts\u002Fbundle-artifact.sh",{"path":68,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":69,"sourceHtmlUrl":70},"scripts\u002Finit-artifact.sh",9925,"https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fweb-artifacts-builder\u002Fscripts\u002Finit-artifact.sh",{"path":72,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":73,"sourceHtmlUrl":74},"scripts\u002Fshadcn-components.tar.gz",19969,"https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fweb-artifacts-builder\u002Fscripts\u002Fshadcn-components.tar.gz",[76,89,104,131,150,177],{"skillNo":77,"name":78,"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":79,"categories":80,"keywords":86,"publishedAt":26},"01M6GDRVS6FXX3ESH0C9DW01C0","test_skill","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fscratch\u002Ftest_skill\u002FSKILL.md",[81],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[87,88],"Test Skill","test",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":26},"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",[],[96,97,98,99,100,101,102,25,20,103],"zustand store ts","zustand","store","with","types","middleware","patterns","typescript",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":113,"publishedAt":26},"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",[110],{"categoryNo":111,"categoryName":112,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000023","Skill与智能体开发",[114,115,116,117,118,119,120,121,122,123,124,125,126,127,25,128,129,130],"automation","zoom automation","zoom","first","Tools","search","MCP","via","meeting","automate","critical","creation","webinars","composio","recordings","management","tracking",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":138,"publishedAt":26},"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",[137],{"categoryNo":111,"categoryName":112,"taxonomyType":84,"taxonomyTypeDesc":85},[139,114,140,141,142,143,144,25,119,145,127,146,124,123,118,147,20,148,120,149],"crm automation","zoho crm","crm","zoho crm automation","zoho","leads","contacts","records","update","tasks","manage",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":159,"publishedAt":26},"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",[156],{"categoryNo":157,"categoryName":158,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000009","前端开发",[160,161,162,163,164,103,165,166,167,168,169,170,99,171,172,173,174,25,175,176],"expert","zod","zod validation expert","validation","react","safe","parsing","errors","schema validation","react hook form","hook","trpc","form","type","next","schema","Next.js",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":184,"publishedAt":26},"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",[183],{"categoryNo":111,"categoryName":112,"taxonomyType":84,"taxonomyTypeDesc":85},[185,186,187,188,189,190,191,192,25,193,194,195,196,197,198,199,200,201,202,120],"zeroize audit","audit","write","passwords","get","project","c++","activate","assembly","read","Bash","secrets","analysis","data","flow","verification","code","rust"]