wide-research
暂无简介
- License 许可
- CC0-1.0
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
02 资源文件 1
- 参考文档skill.yaml260 B
03 SKILL.md 正文
Wide Research
Purpose
Coordinate one manager subagent that fans out the same research task across many independent inputs and returns a single normalized result set.
When to Use
- The task can be split into many independent subtasks (for example, one company/person/topic per input).
- Each subtask should return the same structured fields.
- The user asks for "wide research", "parallel research", or high-volume lookup/screening.
Do not use this workflow for single-item tasks or when subtasks depend on each other.
Tooling
Use exactly one manager subagent for the overall operation.
Manager input contract:
operation_brief: one concise sentence.inputs: one independent item per element.output_schema: required fields and allowed types.worker_prompt_template: per-input instructions.completion_format: exact JSON object shape for the manager's final response.
Manager output contract:
totalsuccess_countfailure_countresultsfailuresnotes
Operating Rules
- Deduplicate and normalize the input list before spawning the manager.
- Keep the output schema minimal and explicit; avoid optional or free-form fields unless the user asked for them.
- Use one manager coordinator for one user goal; do not fan out multiple sibling root-level subagents.
- Instruct the manager to assign one worker per input and keep each worker scoped to its own item.
- If completeness matters and some inputs fail, retry only the failed inputs, once, when feasible.
- Reply to the user immediately that wide research has started; do not block on completion.
- In the final user-facing output, always report coverage (
success_count/total) and unresolved gaps.
Available connectors
-
This skill uses native tools and does not require an account connector.
-
Use
muse.connector_searchto find other connectors andmuse.skill_searchto find related skills. -
If nothing here fits, look on the web for a maintained API or MCP server and set it up with Custom Connectors and MCPs, or build a custom connector.
04 同仓库更多 Skills
model-council
暂无简介
writing-style
Draft or edit writing in the user's voice for the person who will read it and where it will appear. Use for messages, emails, documents or slides written on their behalf, not for your own replies.
write-page
Create or edit requested Page/Space content, or use for prose you have already decided to save as a standalone Markdown file, only if the user did not explicitly request a Markdown file. Honor established formats, destinations, and repository documentation. A selected Page alone does not authorize a write.
software-engineering
For use only in threads for this proactive personal assistant. Investigate software issues; inspect, write, review, or test code; work on a repository or local engineering file; or create, fix, or monitor a pull request or CI run. Use for actual engineering or product QA work, not a general programming explanation.
slides-artifact
Use when the user asks to create, edit, or review slides or a presentation (PowerPoint or Google Slides), including when the task clearly calls for an audience-ready slide deck. Also use to answer questions that require inspecting an existing deck; not for general presentation advice or a chat-only outline.
slack
Use when reading Slack conversations, deciding when to respond, or sending messages, files, and reactions in Slack.