// Research technical solutions by searching the web, examining GitHub repos, and gathering evidence. Use when exploring implementation options or evaluating technologies.
| name | ark-research |
| description | Research technical solutions by searching the web, examining GitHub repos, and gathering evidence. Use when exploring implementation options or evaluating technologies. |
Research technical solutions and gather evidence before implementation.
Always start with web search to find:
GitHub raw content is often blocked. Clone repos to examine them:
cd /tmp
git clone https://github.com/owner/repo.git
cat /tmp/repo/README.md
Look for:
If a website cannot be loaded:
Example prompt:
"I found a relevant resource at [URL] but cannot access it. Could you paste the key content or provide the PDF?"
Store findings in ./scratch/research/ for review:
mkdir -p ./scratch/research
Save:
Minimum 2-3 datapoints required before recommending a solution:
If insufficient evidence, ask for guidance:
"I found only one reference to this approach. Can you point me to additional resources or clarify the requirements?"
Always back up findings with sources:
## Research: [Topic]
### Option 1: [Solution Name]
- **Source**: [URL or repo link]
- **Pros**: ...
- **Cons**: ...
- **Evidence**: [What confirms this works]
### Option 2: [Solution Name]
...
### Recommendation
Based on [N] sources, I recommend [Option] because...
### Sources
- [Title](URL)
- [Repo](GitHub URL) - cloned and examined
- [Spec](URL) - user provided
User: "Research options for terminal recording in an MCP server"