Loading...
Loading...
Found 98 Skills
This skill should be used when the user asks to "build an agent with Google ADK", "use the Agent Development Kit", "create a Google ADK agent", "set up ADK tools", or needs guidance on Google's Agent Development Kit best practices, multi-agent systems, or agent evaluation.
Build and configure personal AI agents with memory, personality, and autonomy using OpenHanako on Electron.
Generates paste-ready Power Apps Canvas App YAML. Invoke when the user wants to replicate a UI mockup, improve an existing Canvas app screen, or build a new screen from a text description. Also invoke when the user asks to "improve", "redesign", or "generate YAML" for a Canvas app screen.
Orchestrate multiple specialized agents working in parallel to debug independent problems. Use when encountering 3+ unrelated bugs or test failures in isolated modules. Matches each problem to the right expert agent and launches them concurrently via the Agent tool with worktree isolation. Supports all available subagent types.
Invoke MassGen's multi-agent system. Use when the user wants multiple AI agents on a task: writing, code, review, planning, specs, research, design, or any task where parallel iteration beats working alone.
Design domain-specific agent teams, define specialized agents, and generate the skills they use. Use when you need to decompose a complex project into coordinated multi-agent teams, choose the right architecture pattern (pipeline, fan-out/fan-in, expert pool, producer-reviewer, supervisor, hierarchical delegation), generate .claude/agents/ and .claude/skills/ files, or validate and iterate on generated harnesses. Triggers on: harness, build a harness, design agent team, agent team architecture, multi-agent skill generation, set up harness, harness engineering, domain agent team, harness for this project.
어떤 주제/과제든 받아서 스스로 팀을 구성하고 조사·분석·검토·결과도출까지 처리하는 범용 에이전트 팀 오케스트레이터. "팀으로 분석해줘", "에이전트 팀으로 조사해줘", "다각도로 검토해줘", "심층 분석 부탁해", "여러 관점으로 봐줘", "think-team", "think team" 키워드로 트리거. 단순 질문이 아닌 복합적 판단, 조사, 전략 결정이 필요한 모든 상황에서 사용.
Use when a single agent demonstrably cannot handle the task and multi-agent coordination is justified.
어떤 주제/과제든 받아서 스스로 팀을 구성하고 조사·분석·검토·결과도출까지 처리하는 범용 에이전트 팀 오케스트레이터. "팀으로 분석해줘", "에이전트 팀으로 조사해줘", "다각도로 검토해줘", "심층 분석 부탁해", "여러 관점으로 봐줘", "think-team", "think team" 키워드로 트리거. 단순 질문이 아닌 복합적 판단, 조사, 전략 결정이 필요한 모든 상황에서 사용.
Use when adding capabilities to an existing agent project — memory, app integration, VPC, multi-agent, migration, model changes, browser, code interpreter, or resource removal. Triggers on: "add memory", "remember across sessions", "call agent from app", "invoke agent from code", "auth to call agent", "streaming responses", "VPC", "VPC connectivity", "VPC error", "can't reach from VPC", "multi-agent", "A2A", "A2A auth", "orchestrator not delegating", "specialist not called", "migrate Bedrock Agent", "after import", "migration issue", "framework for migration", "change model", "browser tool", "code interpreter", "delete agent", "tear down", "agentcore remove", "cross-account memory", "resource-based policy on memory". Not for connecting to external APIs via Gateway — use agents-connect. Not for scaffolding a new project — use agents-get-started. Not for CLI/dev server errors — use agents-debug. Strands vs LangGraph in a migration context routes here.
Guides architectural decisions for LangGraph applications. Use when deciding between LangGraph vs alternatives, choosing state management strategies, designing multi-agent systems, or selecting persistence and streaming approaches.
LangGraph workflow patterns for state management, routing, parallel execution, supervisor-worker, tool calling, checkpointing, human-in-loop, streaming, subgraphs, and functional API. Use when building LangGraph pipelines, multi-agent systems, or AI workflows.