Claude Skill

research

Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download gongyijie85-mattpocock-skills-dsh-skills_research-cddeded.zip · 0 KB

gongyijie85/mattpocock-skills-dsh 15 0 forks MIT Updated 14d ago

Part of gongyijie85/mattpocock-skills-dsh — 25 skills

Install

skills CLI npx skills add https://github.com/gongyijie85/mattpocock-skills-dsh/tree/main/skills/research

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install gongyijie85-mattpocock-skills-dsh@llmmart

Git git clone https://github.com/gongyijie85/mattpocock-skills-dsh.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole gongyijie85/mattpocock-skills-dsh collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Spin up a background agent to do the research, so you keep working while it reads.

Its job:

Investigate the question against primary sources (official docs, source code, specs, first-party APIs), not a secondary write-up of them. Follow every claim back to the source that owns it.
Write the findings to a single Markdown file, citing each claim's source.
Save it where the repo already keeps such notes; match the existing convention, and if there is none, put it somewhere sensible and say where.

Files (mattpocock-skills-dsh)

SKILL.md 794 B

---
name: research
description: Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
---

Spin up a **background agent** to do the research, so you keep working while it reads.

Its job:

1. Investigate the question against **primary sources** (official docs, source code, specs, first-party APIs), not a secondary write-up of them. Follow every claim back to the source that owns it.
2. Write the findings to a single Markdown file, citing each claim's source.
3. Save it where the repo already keeps such notes; match the existing convention, and if there is none, put it somewhere sensible and say where.