[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GD47K6326XYY583PAAPGSP":3,"skill-same:01M6GD47K6326XYY583PAAPGSP":62},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6GD47K6326XYY583PAAPGSP","tdd-workflows-tdd-cycle",null,"Use when working with tdd workflows tdd cycle","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\u002Ftdd-workflows-tdd-cycle\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32],"tdd","workflows","cycle","tdd cycle","tdd workflows tdd cycle","tdd workflows","use","community","with","2026-11-10 10:12:30",false,"---\nname: tdd-workflows-tdd-cycle\ndescription: \"Use when working with tdd workflows tdd cycle\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n## Use this skill when\n\n- Working on tdd workflows tdd cycle tasks or workflows\n- Needing guidance, best practices, or checklists for tdd workflows tdd cycle\n\n## Do not use this skill when\n\n- The task is unrelated to tdd workflows tdd cycle\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\nExecute a comprehensive Test-Driven Development (TDD) workflow with strict red-green-refactor discipline:\n\n[Extended thinking: This workflow enforces test-first development through coordinated agent orchestration. Each phase of the TDD cycle is strictly enforced with fail-first verification, incremental implementation, and continuous refactoring. The workflow supports both single test and test suite approaches with configurable coverage thresholds.]\n\n## Configuration\n\n### Coverage Thresholds\n- Minimum line coverage: 80%\n- Minimum branch coverage: 75%\n- Critical path coverage: 100%\n\n### Refactoring Triggers\n- Cyclomatic complexity > 10\n- Method length > 20 lines\n- Class length > 200 lines\n- Duplicate code blocks > 3 lines\n\n## Phase 1: Test Specification and Design\n\n### 1. Requirements Analysis\n- Use Task tool with subagent_type=\"comprehensive-review::architect-review\"\n- Prompt: \"Analyze requirements for: $ARGUMENTS. Define acceptance criteria, identify edge cases, and create test scenarios. Output a comprehensive test specification.\"\n- Output: Test specification, acceptance criteria, edge case matrix\n- Validation: Ensure all requirements have corresponding test scenarios\n\n### 2. Test Architecture Design\n- Use Task tool with subagent_type=\"unit-testing::test-automator\"\n- Prompt: \"Design test architecture for: $ARGUMENTS based on test specification. Define test structure, fixtures, mocks, and test data strategy. Ensure testability and maintainability.\"\n- Output: Test architecture, fixture design, mock strategy\n- Validation: Architecture supports isolated, fast, reliable tests\n\n## Phase 2: RED - Write Failing Tests\n\n### 3. Write Unit Tests (Failing)\n- Use Task tool with subagent_type=\"unit-testing::test-automator\"\n- Prompt: \"Write FAILING unit tests for: $ARGUMENTS. Tests must fail initially. Include edge cases, error scenarios, and happy paths. DO NOT implement production code.\"\n- Output: Failing unit tests, test documentation\n- **CRITICAL**: Verify all tests fail with expected error messages\n\n### 4. Verify Test Failure\n- Use Task tool with subagent_type=\"tdd-workflows::code-reviewer\"\n- Prompt: \"Verify that all tests for: $ARGUMENTS are failing correctly. Ensure failures are for the right reasons (missing implementation, not test errors). Confirm no false positives.\"\n- Output: Test failure verification report\n- **GATE**: Do not proceed until all tests fail appropriately\n\n## Phase 3: GREEN - Make Tests Pass\n\n### 5. Minimal Implementation\n- Use Task tool with subagent_type=\"backend-development::backend-architect\"\n- Prompt: \"Implement MINIMAL code to make tests pass for: $ARGUMENTS. Focus only on making tests green. Do not add extra features or optimizations. Keep it simple.\"\n- Output: Minimal working implementation\n- Constraint: No code beyond what's needed to pass tests\n\n### 6. Verify Test Success\n- Use Task tool with subagent_type=\"unit-testing::test-automator\"\n- Prompt: \"Run all tests for: $ARGUMENTS and verify they pass. Check test coverage metrics. Ensure no tests were accidentally broken.\"\n- Output: Test execution report, coverage metrics\n- **GATE**: All tests must pass before proceeding\n\n## Phase 4: REFACTOR - Improve Code Quality\n\n### 7. Code Refactoring\n- Use Task tool with subagent_type=\"tdd-workflows::code-reviewer\"\n- Prompt: \"Refactor implementation for: $ARGUMENTS while keeping tests green. Apply SOLID principles, remove duplication, improve naming, and optimize performance. Run tests after each refactoring.\"\n- Output: Refactored code, refactoring report\n- Constraint: Tests must remain green throughout\n\n### 8. Test Refactoring\n- Use Task tool with subagent_type=\"unit-testing::test-automator\"\n- Prompt: \"Refactor tests for: $ARGUMENTS. Remove test duplication, improve test names, extract common fixtures, and enhance test readability. Ensure tests still provide same coverage.\"\n- Output: Refactored tests, improved test structure\n- Validation: Coverage metrics unchanged or improved\n\n## Phase 5: Integration and System Tests\n\n### 9. Write Integration Tests (Failing First)\n- Use Task tool with subagent_type=\"unit-testing::test-automator\"\n- Prompt: \"Write FAILING integration tests for: $ARGUMENTS. Test component interactions, API contracts, and data flow. Tests must fail initially.\"\n- Output: Failing integration tests\n- Validation: Tests fail due to missing integration logic\n\n### 10. Implement Integration\n- Use Task tool with subagent_type=\"backend-development::backend-architect\"\n- Prompt: \"Implement integration code for: $ARGUMENTS to make integration tests pass. Focus on component interaction and data flow.\"\n- Output: Integration implementation\n- Validation: All integration tests pass\n\n## Phase 6: Continuous Improvement Cycle\n\n### 11. Performance and Edge Case Tests\n- Use Task tool with subagent_type=\"unit-testing::test-automator\"\n- Prompt: \"Add performance tests and additional edge case tests for: $ARGUMENTS. Include stress tests, boundary tests, and error recovery tests.\"\n- Output: Extended test suite\n- Metric: Increased test coverage and scenario coverage\n\n### 12. Final Code Review\n- Use Task tool with subagent_type=\"comprehensive-review::architect-review\"\n- Prompt: \"Perform comprehensive review of: $ARGUMENTS. Verify TDD process was followed, check code quality, test quality, and coverage. Suggest improvements.\"\n- Output: Review report, improvement suggestions\n- Action: Implement critical suggestions while maintaining green tests\n\n## Incremental Development Mode\n\nFor test-by-test development:\n1. Write ONE failing test\n2. Make ONLY that test pass\n3. Refactor if needed\n4. Repeat for next test\n\nUse this approach by adding `--incremental` flag to focus on one test at a time.\n\n## Test Suite Mode\n\nFor comprehensive test suite development:\n1. Write ALL tests for a feature\u002Fmodule (failing)\n2. Implement code to pass ALL tests\n3. Refactor entire module\n4. Add integration tests\n\nUse this approach by adding `--suite` flag for batch test development.\n\n## Validation Checkpoints\n\n### RED Phase Validation\n- [ ] All tests written before implementation\n- [ ] All tests fail with meaningful error messages\n- [ ] Test failures are due to missing implementation\n- [ ] No test passes accidentally\n\n### GREEN Phase Validation\n- [ ] All tests pass\n- [ ] No extra code beyond test requirements\n- [ ] Coverage meets minimum thresholds\n- [ ] No test was modified to make it pass\n\n### REFACTOR Phase Validation\n- [ ] All tests still pass after refactoring\n- [ ] Code complexity reduced\n- [ ] Duplication eliminated\n- [ ] Performance improved or maintained\n- [ ] Test readability improved\n\n## Coverage Reports\n\nGenerate coverage reports after each phase:\n- Line coverage\n- Branch coverage\n- Function coverage\n- Statement coverage\n\n## Failure Recovery\n\nIf TDD discipline is broken:\n1. **STOP** immediately\n2. Identify which phase was violated\n3. Rollback to last valid state\n4. Resume from correct phase\n5. Document lesson learned\n\n## TDD Metrics Tracking\n\nTrack and report:\n- Time in each phase (Red\u002FGreen\u002FRefactor)\n- Number of test-implementation cycles\n- Coverage progression\n- Refactoring frequency\n- Defect escape rate\n\n## Anti-Patterns to Avoid\n\n- Writing implementation before tests\n- Writing tests that already pass\n- Skipping the refactor phase\n- Writing multiple features without tests\n- Modifying tests to make them pass\n- Ignoring failing tests\n- Writing tests after implementation\n\n## Success Criteria\n\n- 100% of code written test-first\n- All tests pass continuously\n- Coverage exceeds thresholds\n- Code complexity within limits\n- Zero defects in covered code\n- Clear test documentation\n- Fast test execution (\u003C 5 seconds for unit tests)\n\n## Notes\n\n- Enforce strict RED-GREEN-REFACTOR discipline\n- Each phase must be completed before moving to next\n- Tests are the specification\n- If a test is hard to write, the design needs improvement\n- Refactoring is NOT optional\n- Keep test execution fast\n- Tests should be independent and isolated\n\nTDD implementation for: $ARGUMENTS\n","## Use this skill when\n\n- Working on tdd workflows tdd cycle tasks or workflows\n- Needing guidance, best practices, or checklists for tdd workflows tdd cycle\n\n## Do not use this skill when\n\n- The task is unrelated to tdd workflows tdd cycle\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\nExecute a comprehensive Test-Driven Development (TDD) workflow with strict red-green-refactor discipline:\n\n[Extended thinking: This workflow enforces test-first development through coordinated agent orchestration. Each phase of the TDD cycle is strictly enforced with fail-first verification, incremental implementation, and continuous refactoring. The workflow supports both single test and test suite approaches with configurable coverage thresholds.]\n\n## Configuration\n\n### Coverage Thresholds\n- Minimum line coverage: 80%\n- Minimum branch coverage: 75%\n- Critical path coverage: 100%\n\n### Refactoring Triggers\n- Cyclomatic complexity > 10\n- Method length > 20 lines\n- Class length > 200 lines\n- Duplicate code blocks > 3 lines\n\n## Phase 1: Test Specification and Design\n\n### 1. Requirements Analysis\n- Use Task tool with subagent_type=\"comprehensive-review::architect-review\"\n- Prompt: \"Analyze requirements for: $ARGUMENTS. Define acceptance criteria, identify edge cases, and create test scenarios. Output a comprehensive test specification.\"\n- Output: Test specification, acceptance criteria, edge case matrix\n- Validation: Ensure all requirements have corresponding test scenarios\n\n### 2. Test Architecture Design\n- Use Task tool with subagent_type=\"unit-testing::test-automator\"\n- Prompt: \"Design test architecture for: $ARGUMENTS based on test specification. Define test structure, fixtures, mocks, and test data strategy. Ensure testability and maintainability.\"\n- Output: Test architecture, fixture design, mock strategy\n- Validation: Architecture supports isolated, fast, reliable tests\n\n## Phase 2: RED - Write Failing Tests\n\n### 3. Write Unit Tests (Failing)\n- Use Task tool with subagent_type=\"unit-testing::test-automator\"\n- Prompt: \"Write FAILING unit tests for: $ARGUMENTS. Tests must fail initially. Include edge cases, error scenarios, and happy paths. DO NOT implement production code.\"\n- Output: Failing unit tests, test documentation\n- **CRITICAL**: Verify all tests fail with expected error messages\n\n### 4. Verify Test Failure\n- Use Task tool with subagent_type=\"tdd-workflows::code-reviewer\"\n- Prompt: \"Verify that all tests for: $ARGUMENTS are failing correctly. Ensure failures are for the right reasons (missing implementation, not test errors). Confirm no false positives.\"\n- Output: Test failure verification report\n- **GATE**: Do not proceed until all tests fail appropriately\n\n## Phase 3: GREEN - Make Tests Pass\n\n### 5. Minimal Implementation\n- Use Task tool with subagent_type=\"backend-development::backend-architect\"\n- Prompt: \"Implement MINIMAL code to make tests pass for: $ARGUMENTS. Focus only on making tests green. Do not add extra features or optimizations. Keep it simple.\"\n- Output: Minimal working implementation\n- Constraint: No code beyond what's needed to pass tests\n\n### 6. Verify Test Success\n- Use Task tool with subagent_type=\"unit-testing::test-automator\"\n- Prompt: \"Run all tests for: $ARGUMENTS and verify they pass. Check test coverage metrics. Ensure no tests were accidentally broken.\"\n- Output: Test execution report, coverage metrics\n- **GATE**: All tests must pass before proceeding\n\n## Phase 4: REFACTOR - Improve Code Quality\n\n### 7. Code Refactoring\n- Use Task tool with subagent_type=\"tdd-workflows::code-reviewer\"\n- Prompt: \"Refactor implementation for: $ARGUMENTS while keeping tests green. Apply SOLID principles, remove duplication, improve naming, and optimize performance. Run tests after each refactoring.\"\n- Output: Refactored code, refactoring report\n- Constraint: Tests must remain green throughout\n\n### 8. Test Refactoring\n- Use Task tool with subagent_type=\"unit-testing::test-automator\"\n- Prompt: \"Refactor tests for: $ARGUMENTS. Remove test duplication, improve test names, extract common fixtures, and enhance test readability. Ensure tests still provide same coverage.\"\n- Output: Refactored tests, improved test structure\n- Validation: Coverage metrics unchanged or improved\n\n## Phase 5: Integration and System Tests\n\n### 9. Write Integration Tests (Failing First)\n- Use Task tool with subagent_type=\"unit-testing::test-automator\"\n- Prompt: \"Write FAILING integration tests for: $ARGUMENTS. Test component interactions, API contracts, and data flow. Tests must fail initially.\"\n- Output: Failing integration tests\n- Validation: Tests fail due to missing integration logic\n\n### 10. Implement Integration\n- Use Task tool with subagent_type=\"backend-development::backend-architect\"\n- Prompt: \"Implement integration code for: $ARGUMENTS to make integration tests pass. Focus on component interaction and data flow.\"\n- Output: Integration implementation\n- Validation: All integration tests pass\n\n## Phase 6: Continuous Improvement Cycle\n\n### 11. Performance and Edge Case Tests\n- Use Task tool with subagent_type=\"unit-testing::test-automator\"\n- Prompt: \"Add performance tests and additional edge case tests for: $ARGUMENTS. Include stress tests, boundary tests, and error recovery tests.\"\n- Output: Extended test suite\n- Metric: Increased test coverage and scenario coverage\n\n### 12. Final Code Review\n- Use Task tool with subagent_type=\"comprehensive-review::architect-review\"\n- Prompt: \"Perform comprehensive review of: $ARGUMENTS. Verify TDD process was followed, check code quality, test quality, and coverage. Suggest improvements.\"\n- Output: Review report, improvement suggestions\n- Action: Implement critical suggestions while maintaining green tests\n\n## Incremental Development Mode\n\nFor test-by-test development:\n1. Write ONE failing test\n2. Make ONLY that test pass\n3. Refactor if needed\n4. Repeat for next test\n\nUse this approach by adding `--incremental` flag to focus on one test at a time.\n\n## Test Suite Mode\n\nFor comprehensive test suite development:\n1. Write ALL tests for a feature\u002Fmodule (failing)\n2. Implement code to pass ALL tests\n3. Refactor entire module\n4. Add integration tests\n\nUse this approach by adding `--suite` flag for batch test development.\n\n## Validation Checkpoints\n\n### RED Phase Validation\n- [ ] All tests written before implementation\n- [ ] All tests fail with meaningful error messages\n- [ ] Test failures are due to missing implementation\n- [ ] No test passes accidentally\n\n### GREEN Phase Validation\n- [ ] All tests pass\n- [ ] No extra code beyond test requirements\n- [ ] Coverage meets minimum thresholds\n- [ ] No test was modified to make it pass\n\n### REFACTOR Phase Validation\n- [ ] All tests still pass after refactoring\n- [ ] Code complexity reduced\n- [ ] Duplication eliminated\n- [ ] Performance improved or maintained\n- [ ] Test readability improved\n\n## Coverage Reports\n\nGenerate coverage reports after each phase:\n- Line coverage\n- Branch coverage\n- Function coverage\n- Statement coverage\n\n## Failure Recovery\n\nIf TDD discipline is broken:\n1. **STOP** immediately\n2. Identify which phase was violated\n3. Rollback to last valid state\n4. Resume from correct phase\n5. Document lesson learned\n\n## TDD Metrics Tracking\n\nTrack and report:\n- Time in each phase (Red\u002FGreen\u002FRefactor)\n- Number of test-implementation cycles\n- Coverage progression\n- Refactoring frequency\n- Defect escape rate\n\n## Anti-Patterns to Avoid\n\n- Writing implementation before tests\n- Writing tests that already pass\n- Skipping the refactor phase\n- Writing multiple features without tests\n- Modifying tests to make them pass\n- Ignoring failing tests\n- Writing tests after implementation\n\n## Success Criteria\n\n- 100% of code written test-first\n- All tests pass continuously\n- Coverage exceeds thresholds\n- Code complexity within limits\n- Zero defects in covered code\n- Clear test documentation\n- Fast test execution (\u003C 5 seconds for unit tests)\n\n## Notes\n\n- Enforce strict RED-GREEN-REFACTOR discipline\n- Each phase must be completed before moving to next\n- Tests are the specification\n- If a test is hard to write, the design needs improvement\n- Refactoring is NOT optional\n- Keep test execution fast\n- Tests should be independent and isolated\n\nTDD implementation for: $ARGUMENTS\n",{"name":5,"risk":38,"source":31,"date_added":39,"description":7},"unknown","2026-02-27","main","a50a3aa6b39fb0e1b7db88bef1bfc9c93606e126","modules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Ftdd-workflows-tdd-cycle",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":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add Sam-06060\u002Fjarvis-assistant --skill tdd-workflows-tdd-cycle",{"tool":54,"command":55},"bunx","bunx skills add Sam-06060\u002Fjarvis-assistant --skill tdd-workflows-tdd-cycle",{"tool":57,"command":58},"pnpm","pnpm dlx skills add Sam-06060\u002Fjarvis-assistant --skill tdd-workflows-tdd-cycle","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Ftdd-workflows-tdd-cycle\u002FSKILL.md",true,[],[63,74,89,116,135,162],{"skillNo":64,"name":65,"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":66,"categories":67,"keywords":71,"publishedAt":33},"01M6GDRVS6FXX3ESH0C9DW01C0","test_skill","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fscratch\u002Ftest_skill\u002FSKILL.md",[68],{"categoryNo":69,"categoryName":70,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[72,73],"Test Skill","test",{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":33},"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",[],[81,82,83,32,84,85,86,31,87,88],"zustand store ts","zustand","store","types","middleware","patterns","create","typescript",{"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":98,"publishedAt":33},"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",[95],{"categoryNo":96,"categoryName":97,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[99,100,101,102,103,104,105,106,107,108,109,110,111,112,31,113,114,115],"automation","zoom automation","zoom","first","Tools","search","MCP","via","meeting","automate","critical","creation","webinars","composio","recordings","management","tracking",{"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":123,"publishedAt":33},"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",[122],{"categoryNo":96,"categoryName":97,"taxonomyType":21,"taxonomyTypeDesc":22},[124,99,125,126,127,128,129,31,104,130,112,131,109,108,103,132,87,133,105,134],"crm automation","zoho crm","crm","zoho crm automation","zoho","leads","contacts","records","update","tasks","manage",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":144,"publishedAt":33},"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",[141],{"categoryNo":142,"categoryName":143,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[145,146,147,148,149,88,150,151,152,153,154,155,32,156,157,158,159,31,160,161],"expert","zod","zod validation expert","validation","react","safe","parsing","errors","schema validation","react hook form","hook","trpc","form","type","next","schema","Next.js",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":169,"publishedAt":33},"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",[168],{"categoryNo":96,"categoryName":97,"taxonomyType":21,"taxonomyTypeDesc":22},[170,171,172,173,174,175,176,177,31,178,179,180,181,182,183,184,185,186,187,105],"zeroize audit","audit","write","passwords","get","project","c++","activate","assembly","read","Bash","secrets","analysis","data","flow","verification","code","rust"]