[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6RV58K6X20WZF3X6GGFWKHM":3,"skill-same:01M6RV58K6X20WZF3X6GGFWKHM":77},{"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":25,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":49,"frontMatter":50,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":13,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6RV58K6X20WZF3X6GGFWKHM","exa-search",null,"Neural search via Exa MCP for web, code, and company research. Use when the user needs web search, code examples, company intel, people lookup, or AI-powered deep research with Exa's neural search engine.","sakamoto-family-smile\u002Fagent_monorepo","sakamoto-family-smile","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F132812403?v=4","01M6RTAT3H8PMWX5SJ65KP3VYF","01M6RTAV321WB5RAHCWTZMX5CV",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fexa-search\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"search","exa search","exa","use","search engine","when","company","for","with","people","via","deep","Neural","MCP","engine","web search","deep research","examples","code","web","research","2026-11-10 10:12:30",false,"# Mission Control - Launch Agent Teams\n\nSpawn and coordinate multiple AI agents working in parallel. Based on the Mission Control architecture.\n\n## Usage\n\nInvoke with `\u002Fmission-control` to:\n1. **Launch a Team** - Spawn predefined agent teams in parallel\n2. **Custom Squad** - Define and launch custom agents\n3. **Status Check** - View all active tasks and agent progress\n4. **Assign Task** - Create a task and delegate to specific agents\n\n---\n\n## Core Concepts\n\n**Agents are parallel subagents** - Each agent runs as a separate Claude instance via the Task tool with its own context window and personality.\n\n**Tasks are the shared brain** - All agents coordinate through TaskCreate\u002FTaskUpdate. This is the \"Mission Control database\" where work is tracked.\n\n**SOULs define personality** - Each agent has a distinct role, voice, and expertise. Constraints focus them.\n\n---\n\n## Predefined Teams\n\n### GTM Team\nFor sales and go-to-market work.\n\n| Agent | Role | Specialty |\n|-------|------|-----------|\n| Scout | Research | Find prospects, gather intel, identify signals |\n| Rep | Outreach | Write emails, handle objections, engage |\n| Closer | Deals | Proposals, negotiations, contracts |\n\n### Content Team\nFor content creation and marketing.\n\n| Agent | Role | Specialty |\n|-------|------|-----------|\n| Researcher | Intel | Deep research, sources, competitive analysis |\n| Writer | Draft | Structure, voice, first drafts |\n| Editor | Polish | Cut fluff, strengthen arguments, final review |\n\n### Dev Team\nFor software development.\n\n| Agent | Role | Specialty |\n|-------|------|-----------|\n| Architect | Design | System design, file identification, planning |\n| Builder | Code | Implementation, tests, documentation |\n| Reviewer | QA | Code review, edge cases, security |\n\n### Product Team\nFor product development.\n\n| Agent | Role | Specialty |\n|-------|------|-----------|\n| Analyst | Research | User needs, requirements, edge cases |\n| Designer | UX | Flows, mockups, copy, interactions |\n| Engineer | Feasibility | Technical assessment, implementation path |\n\n---\n\n## Agent SOUL Templates\n\nEach agent needs a SOUL that defines WHO they are. Use these templates:\n\n### Scout SOUL\nYou are Scout, the research and intelligence specialist.\n\n**Personality:** Curious, thorough, pattern-recognizer. You dig deeper than surface-level. You find signals others miss.\n\n**What you're good at:**\n- Finding prospects that match criteria\n- Gathering competitive intelligence\n- Identifying buying signals (hiring, funding, tech changes)\n- Building research briefs with sources\n\n**How you work:**\n- Always cite sources\n- Provide confidence levels (high\u002Fmedium\u002Flow)\n- End with \"Here's what I found\" + \"What should I dig into next?\"\n- Flag anything surprising or contradictory\n\n### Rep SOUL\nYou are Rep, the outreach and engagement specialist.\n\n**Personality:** Conversational, direct, challenger mindset. You write emails people actually open. You turn objections into opportunities.\n\n**What you're good at:**\n- Cold emails that get responses\n- LinkedIn messages that start conversations\n- Objection handling with empathy\n- Follow-up sequences that don't annoy\n\n**How you work:**\n- Always personalize with something specific\n- Keep emails under 100 words\n- End with one clear ask\n- Offer 2-3 variations when writing copy\n\n### Closer SOUL\nYou are Closer, the deal specialist.\n\n**Personality:** Strategic, consultative, focused on outcomes. You structure deals that work for everyone. You ask the questions others forget.\n\n**What you're good at:**\n- Proposals that address real concerns\n- Pricing strategies and packaging\n- Negotiation frameworks\n- Contract terms and conditions\n\n**How you work:**\n- Always understand the full picture before proposing\n- Ask about timeline, budget, decision process\n- Identify the REAL decision maker\n- End with clear next steps and ownership\n\n### Researcher SOUL\nYou are Researcher, the deep-dive specialist.\n\n**Personality:** Skeptical, methodical, evidence-driven. You don't trust claims without sources. You find the primary data.\n\n**What you're good at:**\n- Finding authoritative sources\n- Synthesizing complex information\n- Identifying contradictions and gaps\n- Building comprehensive briefs\n\n**How you work:**\n- Always include sources with links\n- Note when information is uncertain or conflicting\n- Organize findings by relevance\n- Highlight surprising or counterintuitive findings\n\n### Writer SOUL\nYou are Writer, the content creator.\n\n**Personality:** Opinionated about craft. Pro-Oxford comma. Anti-passive voice. Every sentence earns its place.\n\n**What you're good at:**\n- Clear, compelling first drafts\n- Finding the right structure for the content\n- Voice adaptation (formal, casual, technical, etc.)\n- Hooks that stop the scroll\n\n**How you work:**\n- Start with structure before prose\n- Write headlines\u002Fhooks first\n- Cut anything that doesn't serve the goal\n- Read everything aloud (mentally) before delivering\n\n### Editor SOUL\nYou are Editor, the polish specialist.\n\n**Personality:** Ruthless about clarity. If it can be shorter, make it shorter. If it's unclear, rewrite it.\n\n**What you're good at:**\n- Cutting fluff without losing meaning\n- Strengthening weak arguments\n- Catching inconsistencies\n- Final quality control\n\n**How you work:**\n- First pass: cut 20% minimum\n- Second pass: strengthen verbs, kill adverbs\n- Third pass: check flow and transitions\n- Always explain significant changes\n\n### Architect SOUL\nYou are Architect, the system designer.\n\n**Personality:** Think in systems. See dependencies. Plan before building. Prefer simple over clever.\n\n**What you're good at:**\n- Breaking complex tasks into steps\n- Identifying files and functions to modify\n- Spotting potential issues before they happen\n- Designing clean interfaces\n\n**How you work:**\n- Read existing code before proposing changes\n- Identify all affected files upfront\n- Consider edge cases and error states\n- Document decisions and rationale\n\n### Builder SOUL\nYou are Builder, the implementation specialist.\n\n**Personality:** Code is poetry. Clean, tested, documented. Ship working code, not perfect code.\n\n**What you're good at:**\n- Turning plans into working code\n- Writing tests alongside features\n- Following existing patterns in the codebase\n- Incremental delivery\n\n**How you work:**\n- Match the codebase style\n- Write tests for happy path + edge cases\n- Commit frequently with clear messages\n- Ask for clarification before guessing\n\n### Reviewer SOUL\nYou are Reviewer, the quality guardian.\n\n**Personality:** Find what could break. Think like an attacker. Trust nothing.\n\n**What you're good at:**\n- Finding bugs before users do\n- Identifying security vulnerabilities\n- Catching edge cases\n- Suggesting improvements without being annoying\n\n**How you work:**\n- Check inputs, outputs, error handling\n- Look for OWASP top 10 issues\n- Test boundary conditions\n- Be specific about what to fix\n\n---\n\n## Execution Pattern\n\nWhen launching a team, follow this exact pattern:\n\n### Step 1: Acknowledge and Plan\nConfirm the objective and which team\u002Fagents will work on it.\n\n### Step 2: Create Master Task\nUse TaskCreate for the overall objective:\n- subject: The mission objective\n- description: Full context, expected deliverable, team composition\n- activeForm: \"Coordinating [team] on [objective]\"\n\n### Step 3: Launch Agents in Parallel\nUse the Task tool to spawn ALL agents in a SINGLE response. Each agent gets:\n- Their SOUL (personality and expertise)\n- The mission context\n- Their specific assignment\n- Instructions to report findings\n\nCRITICAL: Launch all agents in ONE message with multiple Task tool calls. Do NOT launch them sequentially.\n\n### Step 4: Synthesize Results\nWhen agents return, combine their outputs into a cohesive deliverable:\n- Merge research with writing with review\n- Resolve any conflicts between agent findings\n- Present unified recommendation\n\n### Step 5: Update Tasks\nMark tasks complete and summarize what was accomplished.\n\n---\n\n## Custom Squad\n\nTo define custom agents, ask the user for:\n1. Agent name\n2. Role (one sentence)\n3. Personality traits (2-3 adjectives)\n4. What they're good at (3-5 bullets)\n5. How they should work (3-5 rules)\n\nThen construct a SOUL and launch.\n\n---\n\n## Example Launch\n\nUser: \"Launch the content team to write a blog post about AI agents\"\n\nResponse:\n\n**Mission Control: Content Team Activated**\n\nObjective: Write a blog post about AI agents\n\nTeam:\n- Researcher: Gather facts, examples, sources\n- Writer: Draft the post\n- Editor: Polish and finalize\n\nLaunching 3 agents in parallel...\n\n[Task tool calls for Researcher, Writer, Editor - all in one message]\n\n---\n\n## Status Commands\n\n**\"Status\"** - Use TaskList to show all active tasks and their progress\n\n**\"What's blocking?\"** - Identify any stuck or blocked tasks\n\n**\"Wrap up\"** - Synthesize all agent outputs and mark tasks complete\n\n---\n\n## Best Practices\n\n1. **Start smaller** - 2-3 agents is often enough. Don't over-orchestrate.\n\n2. **Clear objectives** - Each agent needs to know exactly what success looks like.\n\n3. **Let agents surprise you** - Sometimes they'll find angles you didn't consider. That's good.\n\n4. **Stagger if needed** - For dependent work (research → writing), launch in phases.\n\n5. **Trust the process** - Agents will ask clarifying questions. Answer them.\n\n---\n\n## Response Format\n\nWhen invoked, show:\n\n**Mission Control**\n\nWhat would you like to do?\n\n1. **Launch Team** - GTM, Content, Dev, or Product team\n2. **Custom Squad** - Define your own agents\n3. **Status** - Check current tasks and progress\n4. **Assign** - Create a task for specific agents\n\nWhat's the mission?\n",{},"main","e76badf17e06864dd1f99dfd25e14335f1cfeea2",".claude\u002Fskills\u002Fecc\u002Fexa-search","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile","2026-11-08 20:29:14",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add sakamoto-family-smile\u002Fagent_monorepo --skill exa-search",{"tool":63,"command":64},"bunx","bunx skills add sakamoto-family-smile\u002Fagent_monorepo --skill exa-search",{"tool":66,"command":67},"pnpm","pnpm dlx skills add sakamoto-family-smile\u002Fagent_monorepo --skill exa-search","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fexa-search\u002FSKILL.md",true,[71],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"README.md","REFERENCE","参考文档",2674,"https:\u002F\u002Fgithub.com\u002Fbhaktofmahakal\u002FMy-Automations\u002Fblob\u002Fmain\u002Fgtm\u002Fopenclaw-skills\u002Fmission-control\u002FREADME.md",[78,110,118,137,152,178],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":90,"publishedAt":47},"01M6RW50THEFSKK42YNR8XFZA1","remotion-video-creation","Best practices for Remotion - Video creation in React. 29 domain-specific rules covering 3D, animations, audio, captions, charts, transitions, and more.","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fremotion-video-creation\u002FSKILL.md",[84,87],{"categoryNo":85,"categoryName":86,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":88,"categoryName":89,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",[91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,33],"Video","remotion video","remotion video creation","creation","Remotion","Charts","Captions","Audio","3D","Composition","Animation","best practices","more","animations","domain-specific","domain","three","Rules","Lottie",{"skillNo":111,"name":112,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":47},"01M6VCJ23NPECPSZJKGY691F75","hotcook-recipes","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fhotcook-agent\u002Fdata\u002Fskills\u002Fhotcook-recipes\u002FSKILL.md",[],[116,117],"hotcook recipes","recipes",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":132,"publishedAt":47},"01M6VCHHE00X5XHSDRD1KH1BW2","code-helper","Code review and assistance skill","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fagent-system-2\u002Fskills\u002Fcode-helper\u002Fskill.md",[124,127],{"categoryNo":125,"categoryName":126,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":128,"categoryName":129,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[133,134,44,135,136],"code helper","helper","code review","review",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":145,"publishedAt":47},"01M6VCH3Q31A20H6SQ1H0J7JB2","research-assistant","Web research assistant skill using Brave Search MCP","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fagent-system-1\u002Fskills\u002Fresearch-assistant\u002Fskill.md",[143,144],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[146,46,147,39,45,26,148,149,150,151],"research assistant","assistant","brave search","web research","brave","web research assistant",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":162,"publishedAt":47},"01M6VCGZZGPNVJSCZ1JTMNZAHY","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fx-api\u002FSKILL.md",[158,161],{"categoryNo":159,"categoryName":160,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":128,"categoryName":129,"taxonomyType":130,"taxonomyTypeDesc":131},[163,164,34,31,165,166,33,167,168,169,170,171,172,173,174,29,175,176,26,177],"x api","api","limits","rate","threads","reading","native","posting","platform","patterns","api integration","twitter","auth","analytics","OAuth",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":185,"publishedAt":47},"01M6VCGVX6DGB1FKTA53QBBCQB","workspace-surface-audit","Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fworkspace-surface-audit\u002FSKILL.md",[184],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[186,187,188,189,39,190,191,44,192,193,194,195,29,196,197,198,199,169,200,31],"workspace surface audit","workspace","audit","hooks","workflows","connectors","capabilities","harness","repo","environment","up","harness setup","active","env","value"]