[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71TDYPBVF16S76RY6T13MD2":3,"skill-same:01M71TDYPBVF16S76RY6T13MD2":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":13,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M71TDYPBVF16S76RY6T13MD2","tdd-workflows-tdd-cycle",null,"Use when working with tdd workflows tdd cycle","javiertarazon\u002Fide-agente-free-jt7-","javiertarazon","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F153141207?v=4","01M71R52TB3S9HXKH6WSNT8A7V","01M71R52VG5KS2DKDDH4GDQ30A",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Ftdd-workflows-tdd-cycle\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33],"tdd","workflows","cycle","tdd cycle","tdd workflows tdd cycle","tdd workflows","use","community","with","unknown","when","2026-11-10 13:02:02",false,"---\nname: tdd-workflows-tdd-cycle\ndescription: \"Use when working with tdd workflows tdd cycle\"\nrisk: unknown\nsource: community\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":32,"source":30,"description":7},"release\u002Fv4.2.11-panel-pro","a92ea02bcf7e2b3dbaf46d49696c29a3cb490d4f",".github\u002Fskills\u002Ftdd-workflows-tdd-cycle","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-","https:\u002F\u002Fgithub.com\u002Fjaviertarazon","2026-07-12 07:10:45",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add javiertarazon\u002Fide-agente-free-jt7- --skill tdd-workflows-tdd-cycle",{"tool":51,"command":52},"bunx","bunx skills add javiertarazon\u002Fide-agente-free-jt7- --skill tdd-workflows-tdd-cycle",{"tool":54,"command":55},"pnpm","pnpm dlx skills add javiertarazon\u002Fide-agente-free-jt7- --skill tdd-workflows-tdd-cycle","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Ftdd-workflows-tdd-cycle\u002FSKILL.md",true,[],[60,85,112,132,147,169],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":69,"publishedAt":34},"01M71TQ7Q6Z10VWF3C2H5X1KW9","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[66],{"categoryNo":67,"categoryName":68,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[70,71,72,30,73,74,29,75,33,32,76,31,77,78,79,80,81,82,83,84],"zustand","store","zustand store ts","middleware","implementing","react state management","react","state","create","state management","typescript","action","management","separation","global",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":94,"publishedAt":34},"01M71TQ5EAR40G6W0MV5ZDVEZT","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\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[91],{"categoryNo":92,"categoryName":93,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[95,96,97,30,98,99,100,101,102,32,103,104,105,106,107,108,109,110,82,111],"zoom automation","zoom","automation","creation","for","search","schemas","MCP","first","via","meeting","search tools","tracking","webinars","composio","recordings","Tools",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":119,"publishedAt":34},"01M71TQ29B1EYBCEAP1ZBGXQ1A","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\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[118],{"categoryNo":92,"categoryName":93,"taxonomyType":20,"taxonomyTypeDesc":21},[120,121,97,122,123,124,30,125,126,99,127,100,101,128,102,32,129,130,131,78],"crm automation","zoho crm automation","crm","zoho crm","zoho","leads","manage leads","manage","records","convert","tasks","contacts",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":139,"publishedAt":34},"01M71TPZPMN60DH0XV58KVHY23","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[138],{"categoryNo":92,"categoryName":93,"taxonomyType":20,"taxonomyTypeDesc":21},[140,97,141,30,99,100,101,102,142,32,130,143,144,103,104,145,106,109,111,146],"zendesk automation","zendesk","organizations","replies","users","tickets","automate",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":34},"01M71TPXDWKHKG4N6TVEPXWD0N","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity ...","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[154,155,156,157,158,159,160,161,162,97,163,32,164,165,166,167,168,146],"zapier make patterns","zapier","patterns","make","No-Code","complexity","writing","spawner","business","workflow","code","integromat","apache","processes","but",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":178,"publishedAt":34},"01M71TPT5T10WXNKW9G7ZXZ27W","youtube-summarizer","Extract transcripts from YouTube videos and generate comprehensive, detailed summaries using intelligent analysis frameworks","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fyoutube-summarizer\u002FSKILL.md",[175],{"categoryNo":176,"categoryName":177,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",[179,180,181,182,30,183,184,185,186,187,188,189,164,190,191,192,193,194,195,196],"summarizer","youtube","youtube summarizer","Video","content-analysis","frameworks","copilot","2025","github-copilot","extract transcripts","analysis","codex","cli","summaries","github","generate","summarization","2026"]