deep-research-framework
Framework for deep research reports: define the question and tier sources first, cross-verify, then write conclusion-first reports with explicit uncertainty…
Skill by alapha888
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/alapha888-deep-research-framework
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: documents, writing, research
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/deep-research-framework
What's inside
- Skill name
deep-research-framework- Description
- Framework for deep research reports: define the question and tier sources first, cross-verify, then write conclusion-first reports with explicit uncertainty statements. Use when the user asks for a research report, topic investigation, or competitive analysis.
- License
- MIT
- Instructions
- 55 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# Deep Research Report Framework
Produce a report whose "conclusions are trustworthy, process is traceable, and the unknowns are explicitly marked." The quality floor of research is set by its sources, not its prose.
## Workflow
1. **Define the question**: write in one sentence what the report must answer. Add at most 3 sub-questions. Starting before the question is clear guarantees the research will sprawl.
2. **Tier your sources** (tier before you search, so you don't believe whatever you find first):
- Primary: official docs, original papers, original filings, protocol/legal texts, measured data.
- Secondary: reputable press, industry reports, expert interviews.
- Tertiary: social-media posts, forum threads, aggregator sites — leads only, never evidence.
3. **Cross-verify**: key conclusions need two or more independent sources. Two sources quoting the same origin don't count as independent. If no second source exists, downgrade the conclusion to "single-source claim" and mark it as such.
4. **Writing structure** (conclusion first):
- Opening: 3–5 lines stating the core conclusions.
- Body: one section per sub-question, each in "conclusion → evidence → sources" order.
- Closing: uncertainty statement — "what wasn't found, what's speculation, under what conditions the conclusions change."
5. **Timestamps**: date every key fact ("as of Sep 2026"). Undated information is treated as "possibly stale" by default.
## Rules
- Mark speculation as speculation. Use "may", "likely", "unverified" — never dress speculation up with "clearly" or "it is well known".
- No tertiary source supports a core conclusion. A forum thread can point a direction, never serve as evidence.
- Every number in the report has a source. A number without a source is deleted, not rewritten.
- Give "what you don't know" its own explicit uncertainty statement (Workflow step 4, closing section) — never bury the unknowns inside confident prose.
## Minimal example (report outline template)
```markdown
# Research Report: <Topic> (example outline)
**Core conclusions** (3–5 lines): …
## 1. Sub-question one
- Conclusion: …
- Evidence: … (source: primary/secondary, as of …)
- Evidence: … (second independent source)
## 2. Sub-question two
…
## Uncertainty statement
- Not found: …
- Single-source claims: … (one source only, pending verification)
- Invalidation conditions: if … changes, conclusion X in this report needs reassessment.
```
## Anti-patterns
- ❌ Single-source verdicts: one social-media post becomes "research shows".
- ❌ Speculation as fact: "clearly" and "it is well known" are the most dangerous words in a research report.
- ❌ Undated facts: 2023 data presented as the current state; the conclusion quietly expires.
- ❌ Evidence pile with no conclusion: 20 sources listed, and the reader still can't tell what the author believes.
- ❌ Hiding the unknowns: burying what wasn't found makes the report look omniscient and plants landmines.From alapha888/agent-skills-en, MIT.
More from alapha888/agent-skills-en
- 0.587score
meeting-notes
alapha888
Turns raw meeting notes into structured minutes: conclusion first, then decisions / action items / open questions; every action item must have an owner and a…
SkillAFreshness: A★ 1Claude Code +9 - 0.587score
code-review-checklist
alapha888
Five-axis code review checklist (correctness, security, readability, performance, test coverage) producing actionable comments instead of style nitpicks.
SkillAFreshness: A★ 1Claude Code +9 - 0.587score
git-commit-message
alapha888
Generates conventional-commit messages from staged changes: type prefix + English imperative subject (≤50 chars) + optional body explaining why.
SkillAFreshness: A★ 1Claude Code +9 - 0.587score
tech-writing-proofread
alapha888
Proofreads English technical writing for typos, grammar slips, punctuation, terminology consistency, jargon, and structure; returns an itemized Original →…
SkillAFreshness: A★ 1Claude Code +9
Signals
- Stars
- 1
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Oct 16, 2026 (13 days ago)
- Last release
- Oct 16, 2026 (13 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/alapha888/agent-skills-en
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from alapha888
- 0.587score
meeting-notes
alapha888
Turns raw meeting notes into structured minutes: conclusion first, then decisions / action items / open questions; every action item must have an owner and a…
SkillAFreshness: A★ 1Claude Code +9 - 0.587score
code-review-checklist
alapha888
Five-axis code review checklist (correctness, security, readability, performance, test coverage) producing actionable comments instead of style nitpicks.
SkillAFreshness: A★ 1Claude Code +9 - 0.587score
git-commit-message
alapha888
Generates conventional-commit messages from staged changes: type prefix + English imperative subject (≤50 chars) + optional body explaining why.
SkillAFreshness: A★ 1Claude Code +9 - 0.587score
tech-writing-proofread
alapha888
Proofreads English technical writing for typos, grammar slips, punctuation, terminology consistency, jargon, and structure; returns an itemized Original →…
SkillAFreshness: A★ 1Claude Code +9
Cite this page
deep-research-framework skill. Agent Mart. https://agentmart.dev/skills/alapha888-deep-research-framework (last updated 2026-10-24)