[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71RYE7TRB0EXKWF17G452C4":3,"skill-same:01M71RYE7TRB0EXKWF17G452C4":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":14,"categories":15,"keywords":16,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":12,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M71RYE7TRB0EXKWF17G452C4","conductor-setup",null,"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\u002Fconductor-setup\u002FSKILL.md",[],[17,18,19],"setup","conductor setup","conductor","2026-11-10 13:02:02",false,"---\nname: conductor-setup\ndescription: \"Initialize project with Conductor artifacts (product definition,\"\n  tech stack, workflow, style guides)\nmetadata:\n  argument-hint: \"[--resume]\"\nrisk: unknown\nsource: community\n---\n\n# Conductor Setup\n\nInitialize or resume Conductor project setup. This command creates foundational project documentation through interactive Q&A.\n\n## Use this skill when\n\n- Working on conductor setup tasks or workflows\n- Needing guidance, best practices, or checklists for conductor setup\n\n## Do not use this skill when\n\n- The task is unrelated to conductor setup\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. Check if `conductor\u002F` directory already exists in the project root:\n   - If `conductor\u002Fproduct.md` exists: Ask user whether to resume setup or reinitialize\n   - If `conductor\u002Fsetup_state.json` exists with incomplete status: Offer to resume from last step\n\n2. Detect project type by checking for existing indicators:\n   - **Greenfield (new project)**: No .git, no package.json, no requirements.txt, no go.mod, no src\u002F directory\n   - **Brownfield (existing project)**: Any of the above exist\n\n3. Load or create `conductor\u002Fsetup_state.json`:\n   ```json\n   {\n     \"status\": \"in_progress\",\n     \"project_type\": \"greenfield|brownfield\",\n     \"current_section\": \"product|guidelines|tech_stack|workflow|styleguides\",\n     \"current_question\": 1,\n     \"completed_sections\": [],\n     \"answers\": {},\n     \"files_created\": [],\n     \"started_at\": \"ISO_TIMESTAMP\",\n     \"last_updated\": \"ISO_TIMESTAMP\"\n   }\n   ```\n\n## Interactive Q&A Protocol\n\n**CRITICAL RULES:**\n\n- Ask ONE question per turn\n- Wait for user response before proceeding\n- Offer 2-3 suggested answers plus \"Type your own\" option\n- Maximum 5 questions per section\n- Update `setup_state.json` after each successful step\n- Validate file writes succeeded before continuing\n\n### Section 1: Product Definition (max 5 questions)\n\n**Q1: Project Name**\n\n```\nWhat is your project name?\n\nSuggested:\n1. [Infer from directory name]\n2. [Infer from package.json\u002Fgo.mod if brownfield]\n3. Type your own\n```\n\n**Q2: Project Description**\n\n```\nDescribe your project in one sentence.\n\nSuggested:\n1. A web application that [does X]\n2. A CLI tool for [doing Y]\n3. Type your own\n```\n\n**Q3: Problem Statement**\n\n```\nWhat problem does this project solve?\n\nSuggested:\n1. Users struggle to [pain point]\n2. There's no good way to [need]\n3. Type your own\n```\n\n**Q4: Target Users**\n\n```\nWho are the primary users?\n\nSuggested:\n1. Developers building [X]\n2. End users who need [Y]\n3. Internal teams managing [Z]\n4. Type your own\n```\n\n**Q5: Key Goals (optional)**\n\n```\nWhat are 2-3 key goals for this project? (Press enter to skip)\n```\n\n### Section 2: Product Guidelines (max 3 questions)\n\n**Q1: Voice and Tone**\n\n```\nWhat voice\u002Ftone should documentation and UI text use?\n\nSuggested:\n1. Professional and technical\n2. Friendly and approachable\n3. Concise and direct\n4. Type your own\n```\n\n**Q2: Design Principles**\n\n```\nWhat design principles guide this project?\n\nSuggested:\n1. Simplicity over features\n2. Performance first\n3. Developer experience focused\n4. User safety and reliability\n5. Type your own (comma-separated)\n```\n\n### Section 3: Tech Stack (max 5 questions)\n\nFor **brownfield projects**, first analyze existing code:\n\n- Run `Glob` to find package.json, requirements.txt, go.mod, Cargo.toml, etc.\n- Parse detected files to pre-populate tech stack\n- Present findings and ask for confirmation\u002Fadditions\n\n**Q1: Primary Language(s)**\n\n```\nWhat primary language(s) does this project use?\n\n[For brownfield: \"I detected: Python 3.11, JavaScript. Is this correct?\"]\n\nSuggested:\n1. TypeScript\n2. Python\n3. Go\n4. Rust\n5. Type your own (comma-separated)\n```\n\n**Q2: Frontend Framework (if applicable)**\n\n```\nWhat frontend framework (if any)?\n\nSuggested:\n1. React\n2. Vue\n3. Next.js\n4. None \u002F CLI only\n5. Type your own\n```\n\n**Q3: Backend Framework (if applicable)**\n\n```\nWhat backend framework (if any)?\n\nSuggested:\n1. Express \u002F Fastify\n2. Django \u002F FastAPI\n3. Go standard library\n4. None \u002F Frontend only\n5. Type your own\n```\n\n**Q4: Database (if applicable)**\n\n```\nWhat database (if any)?\n\nSuggested:\n1. PostgreSQL\n2. MongoDB\n3. SQLite\n4. None \u002F Stateless\n5. Type your own\n```\n\n**Q5: Infrastructure**\n\n```\nWhere will this be deployed?\n\nSuggested:\n1. AWS (Lambda, ECS, etc.)\n2. Vercel \u002F Netlify\n3. Self-hosted \u002F Docker\n4. Not decided yet\n5. Type your own\n```\n\n### Section 4: Workflow Preferences (max 4 questions)\n\n**Q1: TDD Strictness**\n\n```\nHow strictly should TDD be enforced?\n\nSuggested:\n1. Strict - tests required before implementation\n2. Moderate - tests encouraged, not blocked\n3. Flexible - tests recommended for complex logic\n```\n\n**Q2: Commit Strategy**\n\n```\nWhat commit strategy should be followed?\n\nSuggested:\n1. Conventional Commits (feat:, fix:, etc.)\n2. Descriptive messages, no format required\n3. Squash commits per task\n```\n\n**Q3: Code Review Requirements**\n\n```\nWhat code review policy?\n\nSuggested:\n1. Required for all changes\n2. Required for non-trivial changes\n3. Optional \u002F self-review OK\n```\n\n**Q4: Verification Checkpoints**\n\n```\nWhen should manual verification be required?\n\nSuggested:\n1. After each phase completion\n2. After each task completion\n3. Only at track completion\n```\n\n### Section 5: Code Style Guides (max 2 questions)\n\n**Q1: Languages to Include**\n\n```\nWhich language style guides should be generated?\n\n[Based on detected languages, pre-select]\n\nOptions:\n1. TypeScript\u002FJavaScript\n2. Python\n3. Go\n4. Rust\n5. All detected languages\n6. Skip style guides\n```\n\n**Q2: Existing Conventions**\n\n```\nDo you have existing linting\u002Fformatting configs to incorporate?\n\n[For brownfield: \"I found .eslintrc, .prettierrc. Should I incorporate these?\"]\n\nSuggested:\n1. Yes, use existing configs\n2. No, generate fresh guides\n3. Skip this step\n```\n\n## Artifact Generation\n\nAfter completing Q&A, generate the following files:\n\n### 1. conductor\u002Findex.md\n\n```markdown\n# Conductor - [Project Name]\n\nNavigation hub for project context.\n\n## Quick Links\n\n- Product Definition\n- Product Guidelines\n- Tech Stack\n- Workflow\n- Tracks\n\n## Active Tracks\n\n\u003C!-- Auto-populated by \u002Fconductor:new-track -->\n\n## Getting Started\n\nRun `\u002Fconductor:new-track` to create your first feature track.\n```\n\n### 2. conductor\u002Fproduct.md\n\nTemplate populated with Q&A answers for:\n\n- Project name and description\n- Problem statement\n- Target users\n- Key goals\n\n### 3. conductor\u002Fproduct-guidelines.md\n\nTemplate populated with:\n\n- Voice and tone\n- Design principles\n- Any additional standards\n\n### 4. conductor\u002Ftech-stack.md\n\nTemplate populated with:\n\n- Languages (with versions if detected)\n- Frameworks (frontend, backend)\n- Database\n- Infrastructure\n- Key dependencies (for brownfield, from package files)\n\n### 5. conductor\u002Fworkflow.md\n\nTemplate populated with:\n\n- TDD policy and strictness level\n- Commit strategy and conventions\n- Code review requirements\n- Verification checkpoint rules\n- Task lifecycle definition\n\n### 6. conductor\u002Ftracks.md\n\n```markdown\n# Tracks Registry\n\n| Status | Track ID | Title | Created | Updated |\n| ------ | -------- | ----- | ------- | ------- |\n\n\u003C!-- Tracks registered by \u002Fconductor:new-track -->\n```\n\n### 7. conductor\u002Fcode_styleguides\u002F\n\nGenerate selected style guides from `$CLAUDE_PLUGIN_ROOT\u002Ftemplates\u002Fcode_styleguides\u002F`\n\n## State Management\n\nAfter each successful file creation:\n\n1. Update `setup_state.json`:\n   - Add filename to `files_created` array\n   - Update `last_updated` timestamp\n   - If section complete, add to `completed_sections`\n2. Verify file exists with `Read` tool\n\n## Completion\n\nWhen all files are created:\n\n1. Set `setup_state.json` status to \"complete\"\n2. Display summary:\n\n   ```\n   Conductor setup complete!\n\n   Created artifacts:\n   - conductor\u002Findex.md\n   - conductor\u002Fproduct.md\n   - conductor\u002Fproduct-guidelines.md\n   - conductor\u002Ftech-stack.md\n   - conductor\u002Fworkflow.md\n   - conductor\u002Ftracks.md\n   - conductor\u002Fcode_styleguides\u002F[languages]\n\n   Next steps:\n   1. Review generated files and customize as needed\n   2. Run \u002Fconductor:new-track to create your first track\n   ```\n\n## Resume Handling\n\nIf `--resume` argument or resuming from state:\n\n1. Load `setup_state.json`\n2. Skip completed sections\n3. Resume from `current_section` and `current_question`\n4. Verify previously created files still exist\n5. If files missing, offer to regenerate\n\n## Error Handling\n\n- If file write fails: Halt and report error, do not update state\n- If user cancels: Save current state for future resume\n- If state file corrupted: Offer to start fresh or attempt recovery\n","# Conductor Setup\n\nInitialize or resume Conductor project setup. This command creates foundational project documentation through interactive Q&A.\n\n## Use this skill when\n\n- Working on conductor setup tasks or workflows\n- Needing guidance, best practices, or checklists for conductor setup\n\n## Do not use this skill when\n\n- The task is unrelated to conductor setup\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. Check if `conductor\u002F` directory already exists in the project root:\n   - If `conductor\u002Fproduct.md` exists: Ask user whether to resume setup or reinitialize\n   - If `conductor\u002Fsetup_state.json` exists with incomplete status: Offer to resume from last step\n\n2. Detect project type by checking for existing indicators:\n   - **Greenfield (new project)**: No .git, no package.json, no requirements.txt, no go.mod, no src\u002F directory\n   - **Brownfield (existing project)**: Any of the above exist\n\n3. Load or create `conductor\u002Fsetup_state.json`:\n   ```json\n   {\n     \"status\": \"in_progress\",\n     \"project_type\": \"greenfield|brownfield\",\n     \"current_section\": \"product|guidelines|tech_stack|workflow|styleguides\",\n     \"current_question\": 1,\n     \"completed_sections\": [],\n     \"answers\": {},\n     \"files_created\": [],\n     \"started_at\": \"ISO_TIMESTAMP\",\n     \"last_updated\": \"ISO_TIMESTAMP\"\n   }\n   ```\n\n## Interactive Q&A Protocol\n\n**CRITICAL RULES:**\n\n- Ask ONE question per turn\n- Wait for user response before proceeding\n- Offer 2-3 suggested answers plus \"Type your own\" option\n- Maximum 5 questions per section\n- Update `setup_state.json` after each successful step\n- Validate file writes succeeded before continuing\n\n### Section 1: Product Definition (max 5 questions)\n\n**Q1: Project Name**\n\n```\nWhat is your project name?\n\nSuggested:\n1. [Infer from directory name]\n2. [Infer from package.json\u002Fgo.mod if brownfield]\n3. Type your own\n```\n\n**Q2: Project Description**\n\n```\nDescribe your project in one sentence.\n\nSuggested:\n1. A web application that [does X]\n2. A CLI tool for [doing Y]\n3. Type your own\n```\n\n**Q3: Problem Statement**\n\n```\nWhat problem does this project solve?\n\nSuggested:\n1. Users struggle to [pain point]\n2. There's no good way to [need]\n3. Type your own\n```\n\n**Q4: Target Users**\n\n```\nWho are the primary users?\n\nSuggested:\n1. Developers building [X]\n2. End users who need [Y]\n3. Internal teams managing [Z]\n4. Type your own\n```\n\n**Q5: Key Goals (optional)**\n\n```\nWhat are 2-3 key goals for this project? (Press enter to skip)\n```\n\n### Section 2: Product Guidelines (max 3 questions)\n\n**Q1: Voice and Tone**\n\n```\nWhat voice\u002Ftone should documentation and UI text use?\n\nSuggested:\n1. Professional and technical\n2. Friendly and approachable\n3. Concise and direct\n4. Type your own\n```\n\n**Q2: Design Principles**\n\n```\nWhat design principles guide this project?\n\nSuggested:\n1. Simplicity over features\n2. Performance first\n3. Developer experience focused\n4. User safety and reliability\n5. Type your own (comma-separated)\n```\n\n### Section 3: Tech Stack (max 5 questions)\n\nFor **brownfield projects**, first analyze existing code:\n\n- Run `Glob` to find package.json, requirements.txt, go.mod, Cargo.toml, etc.\n- Parse detected files to pre-populate tech stack\n- Present findings and ask for confirmation\u002Fadditions\n\n**Q1: Primary Language(s)**\n\n```\nWhat primary language(s) does this project use?\n\n[For brownfield: \"I detected: Python 3.11, JavaScript. Is this correct?\"]\n\nSuggested:\n1. TypeScript\n2. Python\n3. Go\n4. Rust\n5. Type your own (comma-separated)\n```\n\n**Q2: Frontend Framework (if applicable)**\n\n```\nWhat frontend framework (if any)?\n\nSuggested:\n1. React\n2. Vue\n3. Next.js\n4. None \u002F CLI only\n5. Type your own\n```\n\n**Q3: Backend Framework (if applicable)**\n\n```\nWhat backend framework (if any)?\n\nSuggested:\n1. Express \u002F Fastify\n2. Django \u002F FastAPI\n3. Go standard library\n4. None \u002F Frontend only\n5. Type your own\n```\n\n**Q4: Database (if applicable)**\n\n```\nWhat database (if any)?\n\nSuggested:\n1. PostgreSQL\n2. MongoDB\n3. SQLite\n4. None \u002F Stateless\n5. Type your own\n```\n\n**Q5: Infrastructure**\n\n```\nWhere will this be deployed?\n\nSuggested:\n1. AWS (Lambda, ECS, etc.)\n2. Vercel \u002F Netlify\n3. Self-hosted \u002F Docker\n4. Not decided yet\n5. Type your own\n```\n\n### Section 4: Workflow Preferences (max 4 questions)\n\n**Q1: TDD Strictness**\n\n```\nHow strictly should TDD be enforced?\n\nSuggested:\n1. Strict - tests required before implementation\n2. Moderate - tests encouraged, not blocked\n3. Flexible - tests recommended for complex logic\n```\n\n**Q2: Commit Strategy**\n\n```\nWhat commit strategy should be followed?\n\nSuggested:\n1. Conventional Commits (feat:, fix:, etc.)\n2. Descriptive messages, no format required\n3. Squash commits per task\n```\n\n**Q3: Code Review Requirements**\n\n```\nWhat code review policy?\n\nSuggested:\n1. Required for all changes\n2. Required for non-trivial changes\n3. Optional \u002F self-review OK\n```\n\n**Q4: Verification Checkpoints**\n\n```\nWhen should manual verification be required?\n\nSuggested:\n1. After each phase completion\n2. After each task completion\n3. Only at track completion\n```\n\n### Section 5: Code Style Guides (max 2 questions)\n\n**Q1: Languages to Include**\n\n```\nWhich language style guides should be generated?\n\n[Based on detected languages, pre-select]\n\nOptions:\n1. TypeScript\u002FJavaScript\n2. Python\n3. Go\n4. Rust\n5. All detected languages\n6. Skip style guides\n```\n\n**Q2: Existing Conventions**\n\n```\nDo you have existing linting\u002Fformatting configs to incorporate?\n\n[For brownfield: \"I found .eslintrc, .prettierrc. Should I incorporate these?\"]\n\nSuggested:\n1. Yes, use existing configs\n2. No, generate fresh guides\n3. Skip this step\n```\n\n## Artifact Generation\n\nAfter completing Q&A, generate the following files:\n\n### 1. conductor\u002Findex.md\n\n```markdown\n# Conductor - [Project Name]\n\nNavigation hub for project context.\n\n## Quick Links\n\n- Product Definition\n- Product Guidelines\n- Tech Stack\n- Workflow\n- Tracks\n\n## Active Tracks\n\n\u003C!-- Auto-populated by \u002Fconductor:new-track -->\n\n## Getting Started\n\nRun `\u002Fconductor:new-track` to create your first feature track.\n```\n\n### 2. conductor\u002Fproduct.md\n\nTemplate populated with Q&A answers for:\n\n- Project name and description\n- Problem statement\n- Target users\n- Key goals\n\n### 3. conductor\u002Fproduct-guidelines.md\n\nTemplate populated with:\n\n- Voice and tone\n- Design principles\n- Any additional standards\n\n### 4. conductor\u002Ftech-stack.md\n\nTemplate populated with:\n\n- Languages (with versions if detected)\n- Frameworks (frontend, backend)\n- Database\n- Infrastructure\n- Key dependencies (for brownfield, from package files)\n\n### 5. conductor\u002Fworkflow.md\n\nTemplate populated with:\n\n- TDD policy and strictness level\n- Commit strategy and conventions\n- Code review requirements\n- Verification checkpoint rules\n- Task lifecycle definition\n\n### 6. conductor\u002Ftracks.md\n\n```markdown\n# Tracks Registry\n\n| Status | Track ID | Title | Created | Updated |\n| ------ | -------- | ----- | ------- | ------- |\n\n\u003C!-- Tracks registered by \u002Fconductor:new-track -->\n```\n\n### 7. conductor\u002Fcode_styleguides\u002F\n\nGenerate selected style guides from `$CLAUDE_PLUGIN_ROOT\u002Ftemplates\u002Fcode_styleguides\u002F`\n\n## State Management\n\nAfter each successful file creation:\n\n1. Update `setup_state.json`:\n   - Add filename to `files_created` array\n   - Update `last_updated` timestamp\n   - If section complete, add to `completed_sections`\n2. Verify file exists with `Read` tool\n\n## Completion\n\nWhen all files are created:\n\n1. Set `setup_state.json` status to \"complete\"\n2. Display summary:\n\n   ```\n   Conductor setup complete!\n\n   Created artifacts:\n   - conductor\u002Findex.md\n   - conductor\u002Fproduct.md\n   - conductor\u002Fproduct-guidelines.md\n   - conductor\u002Ftech-stack.md\n   - conductor\u002Fworkflow.md\n   - conductor\u002Ftracks.md\n   - conductor\u002Fcode_styleguides\u002F[languages]\n\n   Next steps:\n   1. Review generated files and customize as needed\n   2. Run \u002Fconductor:new-track to create your first track\n   ```\n\n## Resume Handling\n\nIf `--resume` argument or resuming from state:\n\n1. Load `setup_state.json`\n2. Skip completed sections\n3. Resume from `current_section` and `current_question`\n4. Verify previously created files still exist\n5. If files missing, offer to regenerate\n\n## Error Handling\n\n- If file write fails: Halt and report error, do not update state\n- If user cancels: Save current state for future resume\n- If state file corrupted: Offer to start fresh or attempt recovery\n",{},"release\u002Fv4.2.11-panel-pro","a92ea02bcf7e2b3dbaf46d49696c29a3cb490d4f",".github\u002Fskills\u002Fconductor-setup","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-","https:\u002F\u002Fgithub.com\u002Fjaviertarazon","2026-07-12 07:10:45",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add javiertarazon\u002Fide-agente-free-jt7- --skill conductor-setup",{"tool":37,"command":38},"bunx","bunx skills add javiertarazon\u002Fide-agente-free-jt7- --skill conductor-setup",{"tool":40,"command":41},"pnpm","pnpm dlx skills add javiertarazon\u002Fide-agente-free-jt7- --skill conductor-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fconductor-setup\u002FSKILL.md",true,[],[46,78,105,125,140,162],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":57,"publishedAt":20},"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",[52],{"categoryNo":53,"categoryName":54,"taxonomyType":55,"taxonomyTypeDesc":56},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76,77],"zustand","store","zustand store ts","community","middleware","implementing","use","react state management","when","unknown","react","with","state","create","state management","typescript","action","management","separation","global",{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":87,"publishedAt":20},"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",[84],{"categoryNo":85,"categoryName":86,"taxonomyType":55,"taxonomyTypeDesc":56},"01JBSEEDCAT000000000000023","Skill与智能体开发",[88,89,90,61,91,92,93,94,95,67,96,97,98,99,100,101,102,103,75,104],"zoom automation","zoom","automation","creation","for","search","schemas","MCP","first","via","meeting","search tools","tracking","webinars","composio","recordings","Tools",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":112,"publishedAt":20},"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",[111],{"categoryNo":85,"categoryName":86,"taxonomyType":55,"taxonomyTypeDesc":56},[113,114,90,115,116,117,61,118,119,92,120,93,94,121,95,67,122,123,124,71],"crm automation","zoho crm automation","crm","zoho crm","zoho","leads","manage leads","manage","records","convert","tasks","contacts",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":132,"publishedAt":20},"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",[131],{"categoryNo":85,"categoryName":86,"taxonomyType":55,"taxonomyTypeDesc":56},[133,90,134,61,92,93,94,95,135,67,123,136,137,96,97,138,99,102,104,139],"zendesk automation","zendesk","organizations","replies","users","tickets","automate",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":20},"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",[],[147,148,149,150,151,152,153,154,155,90,156,67,157,158,159,160,161,139],"zapier make patterns","zapier","patterns","make","No-Code","complexity","writing","spawner","business","workflow","code","integromat","apache","processes","but",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":171,"publishedAt":20},"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",[168],{"categoryNo":169,"categoryName":170,"taxonomyType":55,"taxonomyTypeDesc":56},"01JBSEEDCAT000000000000016","图像与多媒体",[172,173,174,175,61,176,177,178,179,180,181,182,157,183,184,185,186,187,188,189],"summarizer","youtube","youtube summarizer","Video","content-analysis","frameworks","copilot","2025","github-copilot","extract transcripts","analysis","codex","cli","summaries","github","generate","summarization","2026"]