Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Deep Research Framework

ASecurity

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.

47,142 stars
0 votes
0 copies
0 views
Added 10/1/2026
ai-agentsrustgogit

Works with

cursor

Security Analysis

A100/100

Scanned 10/1/2026

$npx -y skills add sickn33/agentic-awesome-skills --skill deep-research-framework --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Deep Research Framework?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Deep Research Framework
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sickn33-deep-research-framework/badge)](https://www.skillsdirectory.com/skills/sickn33-deep-research-framework)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
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."
category: research
risk: safe
source: https://github.com/alapha888/agent-skills-en
source_repo: alapha888/agent-skills-en
source_type: community
date_added: "2026-10-01"
author: alapha888
tags: [research-reports, source-verification, analysis]
tools: [claude, cursor, gemini, codex]
license: MIT
license_source: https://github.com/alapha888/agent-skills-en/blob/main/LICENSE
---

# 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.

## When to Use

- Use when the user asks for a research report, topic investigation, or competitive analysis.
- Use when sources need tiering and cross-verification before writing conclusions.

## 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.
- State "what you don't know" before "what you know" — honest uncertainty beats pretty certainty.

## 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.
```

## Limitations

- Source quality is the ceiling of the report. Declared "primary sources" cannot be verified for authenticity by this skill; it only enforces the tiering and cross-verification discipline.
- Independent-source requirements are a judgment call. Two outlets quoting the same wire story or press release count as one origin, and the skill cannot detect shared-origin syndication automatically.
- Web access is required for source-backed research. Without search or fetch tools the skill stops rather than writing a report from memory, or marks every external fact `[UNVERIFIED]` and warns on the cover.
- Recency claims expire. A dated fact ("as of Sep 2026") is only valid until the underlying source changes; the skill does not re-verify older reports.

## 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.

Attribution

sickn33sickn33
View sourceSee grades on GitHubMore from sickn33 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →