Automated summary
Launches a coordinated research team with Fetcher, BrainStorm, and an optional specialist agent to investigate a topic in depth.
Strengths
- Clearly separates fact gathering, idea generation, and domain expertise.
- Produces persistent deliverables: indexed sources, a study file, brainstorming, and specialist analysis.
- Requires source attribution and a minimum number of references.
- Supports an optional specialist agent for targeted domain review.
Limitations
- Assumes a specific repository layout with Library/Sources, Dashboard/Work_Space, and agent identity files.
- Relies on the Task tool and sub-agent execution, which can increase cost and latency.
- True parallel execution depends on the runtime and requires coordination across agents.
Use it for deep, multi-angle research that benefits from sources, creative exploration, and expert review.
Avoid it for simple questions, quick lookups, or repositories that lack the expected agent and workspace structure.
Security analysis
CautionThe skill is a legitimate research orchestration workflow, but it grants powerful tools such as Bash and network access along with file writes and subagent spawning. No abusive or destructive behavior is instructed, so risk is limited, but the broad permissions warrant a caution rating rather than safe.
- •Allows broad tool access including Bash, Write, Edit, WebFetch, and WebSearch, plus subagent spawning via Task.
- •Instructs web research and writing files to Library/Sources and Dashboard/Work_Space, but contains no destructive commands, secret exfiltration, or obfuscated payloads.
Examples
/summon-team-research WebSocket vs SSE for real-time updates/summon-team-research EU AI Act compliance requirements specialist=legal/summon-team-research Competitor analysis of Cursor IDE specialist=galname: summon-team-research description: Launch a research team (Fetcher + BrainStorm + specialist) for deep investigation allowed-tools:
- Task
- Read
- Write
- Edit
- Bash
- Glob
- Grep
- WebFetch
- WebSearch
/summon-team-research - Research Team
Launch a coordinated research team: Fetcher gathers sources, BrainStorm generates ideas, and a specialist agent provides domain expertise — working in parallel.
Usage
/summon-team-research <topic> [specialist=<agent>]
If no specialist is specified, Orca (you, the Team Lead) fills the synthesis role.
Examples
/summon-team-research WebSocket vs SSE for real-time updates
/summon-team-research Hebrew NLP libraries specialist=builder
/summon-team-research EU AI Act compliance requirements specialist=legal
/summon-team-research Competitor analysis of Cursor IDE specialist=gal
Instructions
When invoked, you are the Team Lead (Orca). Spawn teammates to research the given topic.
Step 1: Parse the Request
- Extract the research topic
- Identify the specialist agent (default: none, you synthesize)
- Check
Library/Sources/for existing research on this topic
Step 2: Spawn Teammates
Launch teammates using the Task tool.
Teammate 1: Fetcher
You are Fetcher — The Researcher.
READ FIRST:
- Your identity: Library/Fetcher/Fetcher_Identity.md
- Your knowledge: Library/Knowledge/Fetcher/README.md
- CLAUDE.md is auto-loaded (shared protocols)
YOUR TASK:
Research: [TOPIC]
DELIVERABLE:
1. Save source files to Library/Sources/[topic-slug]/
- One .md file per source (clean, attributed, dated)
- README.md index of all sources gathered
2. Create a study file at Dashboard/Work_Space/[Topic]_Study.md
- Executive summary
- Key findings organized by theme
- Source attribution for every claim
GUIDELINES:
- Use WebSearch and WebFetch to gather information
- Respect robots.txt and rate limits
- Prefer official documentation, reputable sources
- Minimum 3 sources, aim for 5-8
- After delivering, update Library/Knowledge/[requesting-agent]/README.md with links to new sources
COORDINATION:
- BrainStorm will use your research to generate ideas
- [Specialist] will provide domain-specific analysis
- Focus on FACTS and SOURCES — leave the creative thinking to BrainStorm
Teammate 2: BrainStorm
You are BrainStorm — The Creative.
READ FIRST:
- Your identity: AgenTeam/BrainStorm/BrainStorm_Identity.md
- Your knowledge: Library/Knowledge/BrainStorm/README.md
- CLAUDE.md is auto-loaded (shared protocols)
YOUR TASK:
Generate ideas and insights about: [TOPIC]
Start by reading any existing sources in Library/Sources/ related to this topic. When Fetcher's research arrives at Dashboard/Work_Space/[Topic]_Study.md, incorporate those findings.
DELIVERABLE:
Write to Dashboard/Work_Space/BRAINSTORM_[topic].md
Include:
- At least 5 distinct ideas or approaches
- Pros/cons for each
- "What if..." explorations
- Connections to AutoMates and our current projects
- Recommended direction with reasoning
COORDINATION:
- Fetcher is gathering the facts — build on them
- [Specialist] will evaluate from their domain
- Be bold — this is the place for creative thinking
Teammate 3: Specialist (if specified)
You are [Specialist Agent] — [Role].
READ FIRST:
- Your identity: [identity path]
- Your knowledge: Library/Knowledge/[Agent]/README.md
- CLAUDE.md is auto-loaded (shared protocols)
YOUR TASK:
Provide [domain] analysis of: [TOPIC]
Read Fetcher's research when available at Dashboard/Work_Space/[Topic]_Study.md.
Read BrainStorm's ideas when available at Dashboard/Work_Space/BRAINSTORM_[topic].md.
DELIVERABLE:
Write to Dashboard/Work_Space/[AGENT]_Analysis_[topic].md
Include:
- Domain-specific assessment of the research findings
- Feasibility analysis of BrainStorm's ideas
- Risks and concerns from your [domain] perspective
- Recommendations
COORDINATION:
- Fetcher gathered the sources
- BrainStorm generated creative ideas
- Your job is the expert evaluation from a [domain] lens
Step 3: Synthesize
When all teammates finish, create a synthesis:
=== RESEARCH TEAM COMPLETE ===
TOPIC: [topic]
SOURCES: [count] sources gathered by Fetcher
Location: Library/Sources/[topic-slug]/
IDEAS: [count] ideas generated by BrainStorm
Location: Dashboard/Work_Space/BRAINSTORM_[topic].md
SPECIALIST: [Agent]'s assessment
Location: Dashboard/Work_Space/[Agent]_Analysis_[topic].md
KEY FINDINGS:
1. [finding 1]
2. [finding 2]
3. [finding 3]
RECOMMENDED DIRECTION:
[synthesis of research + ideas + specialist input]
NEXT STEPS:
- [what to do with this research]
===============================
Notes
- Fetcher starts immediately (no dependencies)
- BrainStorm can start independently but should incorporate Fetcher's work when available
- Specialist waits for both Fetcher and BrainStorm when possible
- All deliverables go to
Dashboard/Work_Space/for team visibility - Library/Sources/ gets the permanent research files
- The user decides what to do with the findings (Pilot-in-Command)
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/summon-research-team-mrwakbeo/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/summon-research-team-mrwakbeo' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/summon-research-team-mrwakbeo/download' --output '.skill-downloads/summon-research-team-mrwakbeo/SKILL.md.part' && mv '.skill-downloads/summon-research-team-mrwakbeo/SKILL.md.part' '.skill-downloads/summon-research-team-mrwakbeo/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/summon-research-team-mrwakbeo/SKILL.md' && test -s '.skill-downloads/summon-research-team-mrwakbeo/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/summon-team-research' && cp -R '.skill-downloads/summon-research-team-mrwakbeo' '.claude/skills/summon-team-research'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/summon-research-team-mrwakbeo'openskills read 'summon-research-team-mrwakbeo'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/summon-research-team-mrwakbeo/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Create Interactive Maps with kepler.gl
Data & AI
Create interactive map visualizations and export standalone HTML using the keplergl Python package. Use to plot geospatial data from DataFrames, GeoJSON, or CSV.
Agent-Driven Parameter Optimization
Data & AI
Guide for optimizing configurable systems with a measurable objective, using bounded trials and evidence-based recommendations.
ICP Visitor Outreach
Data & AI
Identify signed-up users matching the ideal customer profile but stalled, and draft personalized outreach to re-engage them.