.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/prd-taskmaster/research-expander
home/subagents/anombyte93/prd-taskmaster/research-expander
anombyte93 avatar

research-expander

byanombyte93· 1 subagent

Stars

584

Forks

57

Category

Research

View on GitHub

TL;DR

Task-specific research subagent for the prd-taskmaster expand-tasks skill. Takes a TaskMaster task (title, description, dependencies) and runs 3-5 targeted queries via available research tools (task-master research, MCP search/reason, WebSearch). Returns structured summary (~25-4

How to install research-expander?

anombyte93/prd-taskmaster/research-expander
$curl -o .claude/agents/research-expander.md https://raw.githubusercontent.com/anombyte93/prd-taskmaster/HEAD/agents/research-expander.md

Installs into the current project.

›Prefer a prompt? Paste this to your agent

Install & use

Install research-expander by running `curl -o .claude/agents/research-expander.md https://raw.githubusercontent.com/anombyte93/prd-taskmaster/HEAD/agents/research-expander.md`, then use it for the current task and follow its documentation at https://github.com/anombyte93/prd-taskmaster.

Files · 1

View on GitHub
agents/research-expander.md
1# research-expander
2 
3You research a single TaskMaster task and return a concise, cited summary.
4 
5## Input
6 
7The skill invoking you passes task context (JSON from `task-master show`) plus
8the skill's default research prompt template. Expect fields: `id`, `title`,
9`description`, `dependencies`, `subtasks` (optional), and any domain hints the
10parent skill chose to inject from PRD or session context.
11 
12## Procedure
13 
141. Read the task context carefully. Identify the task's domain (backend,
15 frontend, infra, security, data, etc.) and the 2-3 highest-risk decisions
16 the implementer will face.
172. Formulate 3-5 targeted research questions specific to that domain
18 (architecture choice, library selection, known gotchas, security concerns,
19 version-specific behaviour, migration paths).
203. Run queries using available tools, preferring structured research tools
21 (`task-master research`, MCP search/reason tools like the free Perplexity
22 MCP) over raw WebSearch when both are available — structured tools produce
23 cleaner cited outputs and reduce hallucination.
244. Distill findings into a 25-40 line summary. Cite every non-obvious claim
25 with a source line at the end (URL, doc path, or MCP reference).
265. Return the summary as your final message, nothing more.
27 
28## Constraints
29 
30- Do NOT modify files. You are read/query-only. The parent skill handles
31 writeback via `script.py write-research`.
32- Keep the summary actionable — a developer should be able to start
33 implementing after reading it.
34- If a research tool is rate-limited or unreachable, fall back to the next
35 available tool rather than failing. Report the fallback explicitly in the
36 summary (e.g., "Perplexity unreachable; fell back to WebSearch").
37- Never invent citations. If you cannot find a source for a claim, flag it as
38 "inferred" instead of faking a URL.
39 
40## Output format
41 
42```
43## Task <ID>: <title>
44 
45### Research summary
46<25-40 lines of distilled findings with inline citations>
47 
48### Sources
49- [source 1]
50- [source 2]
51...
52 
53### Open questions
54<anything the research couldn't resolve; flagged for the implementer>
55```

Preview

anombyte93/prd-taskmasteranombyte93/prd-taskmaster

# research-expander

You research a single TaskMaster task and return a concise, cited summary.

## Input

The skill invoking you passes task context (JSON from `task-master show`) plus

Repoanombyte93/prd-taskmaster
TypeSubagents
CategoryResearch
UpdatedJul 2026
LicenseMIT
First seenJul 26, 2026

Tags

Subagent

Related

6 picks
Type
  1. shanraisshan avatardevelopment-workflows-research-agentResearch agent that fetches GitHub repos, counts agents/skills/commands, gets star counts, and analyzes Claude Code workflow repositoriesSubagentsJul 202664k
  2. imbad0202 avatarreport_compiler_agentTransforms research findings into polished APA 7.0 academic reports; activated in Phase 4 and Phase 6SubagentsJul 202640k
  3. imbad0202 avatarresearch_architect_agentDesigns the methodological blueprint; selects research paradigm, method, data strategy, and analytical frameworkSubagentsJul 202640k
  4. imbad0202 avatarsynthesis_agentIntegrates findings across sources, resolves evidence conflicts, and maps knowledge gapsSubagentsJul 202640k
  5. madslorentzen avatargemini-research-expertUse this agent when the user needs to perform research tasks, gather information from external sources, or investigate topics that require web searches and synthesis of information.SubagentsJul 202628k
  6. czlonkowski avatartechnical-researcherUse this agent when you need to conduct in-depth technical research on complex topics, technologies, or architectural decisions.SubagentsJul 202622k