foundry-research

AI-powered research skill with five workflows - chat (single-model conversation), consensus (multi-model synthesis), thinkdeep (systematic investigation), ideate (creative brainstorming), and deep (multi-phase web research). Supports persistent threads and research sessions. TRIGGER when: user asks for research, consultation, brainstorming, investigation, or deep research. Always route through this skill — never call mcp__plugin_foundry_foundry-mcp__research directly. DO NOT TRIGGER when: a <command-name> tag is present in the current turn (skill already loaded), called from a subagent, simple factual questions answerable from context, or codebase exploration (use Explore agent instead).

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "foundry-research" with this command: npx skills add tylerburleigh/claude-foundry/tylerburleigh-claude-foundry-foundry-research

Research Skill

Overview

  • Purpose: AI-powered research with multiple reasoning strategies
  • Scope: Five workflows, persistent thread and session management
  • Entry: Skill(foundry:foundry-research) or user invocation

Flow

[x?]=decision (GATE)=user approval =sequence

- **Entry** → [route?]
  - [explicit?] → Dispatch → Execute → Persist thread → Response + thread_id
  - [thread-id?] → Resume → Dispatch → Execute → Persist thread → Response + thread_id
  - [research-id?] → SessionMgmt
  - [sessions?] → ListSessions
  - [no args?] → (GATE: choose workflow) → AutoRoute → Dispatch → Execute → Persist thread → Response + thread_id
  - [deep research?] → (GATE: confirm query + params) → Start → Poll → Report (background execution)

CRITICAL for deep research workflow: Read references/deep-research-workflow.md before execution. Contains required polling strategy and MCP parameters.

Deep Research Status Monitoring

Call deep-research-status with long-poll (wait=true). The server blocks until progress occurs or timeout elapses.

  1. Report progress to user when each call returns.
  2. Repeat until status is completed or failed.
  3. If 2 consecutive responses return "changed": false, offer user options via AskUserQuestion (keep waiting, cancel, narrow query).

CRITICAL — Do NOT supplement deep research with your own searches. While deep research is running, do NOT call WebSearch, WebFetch, tavily_search, tavily_extract, or any other web/research tools. The deep research workflow handles all source gathering internally. Only use external search tools if the user explicitly asks you to search independently. When deep research is in the SUPERVISION phase and progress seems slow, this is normal — report status and keep polling. Do not interpret normal processing time as a failure that needs workaround.

MCP Tooling

RouterActions
researchchat, consensus, thinkdeep, ideate, deep-research, deep-research-status, deep-research-report, deep-research-list, deep-research-delete, deep-research-evaluate, thread-list, thread-get, thread-delete, node-execute, node-record, node-status, node-findings

MCP Contract

ActionRequiredOptionalErrors
chatpromptthread_id, provider_idTHREAD_NOT_FOUND
consensuspromptproviders, strategyNO_MODELS_AVAILABLE
thinkdeeppromptthread_id, depthMAX_DEPTH_EXCEEDED
ideatepromptthread_id, phaseINVALID_PHASE
deep-researchquerymax_iterations, max_sub_queries, max_sources_per_query, follow_linksRESEARCH_TIMEOUT
deep-research-statusresearch_id-RESEARCH_NOT_FOUND
deep-research-reportresearch_id-RESEARCH_NOT_FOUND
deep-research-list-limit, completed_only-
deep-research-deleteresearch_id-RESEARCH_NOT_FOUND
deep-research-evaluateresearch_id-RESEARCH_NOT_FOUND
thread-*thread_idlimitTHREAD_NOT_FOUND
node-statusspec_id, research_node_id-NODE_NOT_FOUND
node-executespec_id, research_node_idpromptNODE_NOT_FOUND, INVALID_TYPE
node-recordspec_id, research_node_id, resultsummary, key_insights, recommendations, confidenceNODE_NOT_FOUND
node-findingsspec_id, research_node_id-NODE_NOT_FOUND, NO_FINDINGS

Workflow Selection

SignalWorkflow
Follow-up, iterationchat
Multiple perspectivesconsensus
Complex problemthinkdeep
Brainstormingideate
Comprehensive research, multiple sourcesdeep research

User Gates

  • No args: workflow selection
  • Ambiguous: clarify before auto-route
  • Consensus: strategy selection
  • Ideate: phase transition
  • Deep: pre-launch query confirmation, then progress updates during background execution

Output Formats

WorkflowResponse
chat{response, thread_id, model}
consensus{responses[], synthesis, strategy}
thinkdeep{findings[], confidence, thread_id}
ideate{ideas[], phase, selected[]}
deep research{research_id, status, report{summary, findings[], sources[], topic_research_results[], contradictions[], content_fidelity, evaluation}}

References

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

foundry-review

No summary provided by upstream source.

Repository SourceNeeds Review
General

foundry-spec

No summary provided by upstream source.

Repository SourceNeeds Review
General

foundry-implement

No summary provided by upstream source.

Repository SourceNeeds Review
General

foundry-setup

No summary provided by upstream source.

Repository SourceNeeds Review