plugins/decipon/skills/deep-research/SKILL.md
Use when asked for "deep research", "thorough analysis", "comprehensive report", "investigate", "due diligence", or when multiple sources are needed to answer complex questions. Produces well-sourced research reports through iterative refinement.
npx skillsauth add synaptiai/synapti-marketplace conducting-deep-researchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill uses an iterative methodology treating research as a diffusion process: start with noise (rough draft), apply guidance (research brief), denoise through cycles of critique → research → refine until quality converges.
Use TodoWrite to track these mandatory steps:
<required> 1. Clarify scope (if ambiguous) 2. Write research brief (guidance signal) 3. Generate initial draft from knowledge (noisy starting point) 4. Red team critique (identify noise) 5. Targeted web_search with reflection 6. Score sources and track contradictions 7. Refine draft (denoise) 8. Evaluate quality (score < 7? repeat 4-7, max 3 cycles) 9. Finalize </required>Ask me clarifying questions only if:
Skip for well-defined requests.
RESEARCH BRIEF
Topic: [Specific question]
Scope: [Included/excluded]
Key Questions:
1. [Primary]
2. [Secondary]
3. [Tertiary]
Constraints: [Limits]
Language: [Match user's language]
Write from existing knowledge only, marking gaps:
[NEEDS VERIFICATION] - uncertain claims[RESEARCH NEEDED] - missing information[CONFIDENCE: LOW/MED/HIGH] - flag uncertainty levelsThis draft intentionally contains "noise" - the refinement loop will denoise it.
Attack the draft for:
Rate each issue 1-10 severity. See references/critique-framework.md.
Search budget by complexity:
CRITICAL: Think after EVERY search. After each web_search, pause and reflect:
REFLECTION:
- What key facts did I find?
- What gaps remain?
- Do sources agree or conflict?
- Is another search needed, or do I have enough?
Parallel research triggers - pursue multiple threads when:
See references/search-patterns.md for query techniques.
Score each source (1-100 confidence):
| Source Type | Base Score | |-------------|------------| | Official documentation, peer-reviewed | 85-100 | | Government/institutional reports | 75-90 | | Established news outlets | 60-80 | | Industry publications | 50-75 | | Blogs, forums | 20-50 |
Adjust based on: recency, author credentials, citation quality.
Track facts with attribution:
FACT: [Statement]
SOURCE: [URL]
CONFIDENCE: [1-100]
DISPUTED: [Yes/No - conflicts with other sources?]
When sources contradict:
See references/source-evaluation.md for detailed guidance.
Refine by:
[NEEDS VERIFICATION] with sourced factsContext management: If accumulating too much research, compress raw notes into key findings before continuing. Discard redundant/low-value information.
Score 1-10 on:
Track across iterations:
QUALITY LOG:
Iteration 1: Comprehensiveness 5, Accuracy 4, Avg 4.5
Iteration 2: Comprehensiveness 7, Accuracy 6, Avg 6.5
Iteration 3: Comprehensiveness 8, Accuracy 8, Avg 8.0 ✓
If average < 7: Return to Step 4 (max 3 cycles). If score drops between iterations: Focus critique on what regressed.
# [Title]
## Executive Summary
[Key findings in 2-3 paragraphs]
## Findings
[Organized by research questions, with inline citations]
## Methodology
[Brief: sources consulted, confidence levels, any unresolved contradictions]
## Limitations
[Gaps, uncertainties, disputed claims]
## Sources
[Numbered list with confidence indicators]
See references/report-templates.md for format variants.
Input: "Research the current state of nuclear fusion energy"
Research Brief:
Topic: Current state of nuclear fusion energy
Key Questions:
1. What are the leading approaches and projects?
2. What milestones have been achieved recently?
3. What are realistic timelines for commercial fusion?
Constraints: Focus on scientific/engineering progress, not policy
Draft Excerpt (before research):
Nuclear fusion has made significant progress [CONFIDENCE: LOW].
The National Ignition Facility achieved ignition [NEEDS VERIFICATION].
Private companies like [RESEARCH NEEDED] are also pursuing fusion.
Post-search reflection:
REFLECTION after search 1 (NIF ignition):
- Found: NIF achieved ignition Dec 2022, 3.15 MJ from 2.05 MJ input
- Source: Lawrence Livermore (official) - Confidence 95
- Gap: Private sector landscape still unknown
- Next: Search for private fusion companies
Source tracking:
FACT: NIF achieved fusion ignition December 2022
SOURCE: llnl.gov/news/...
CONFIDENCE: 95
DISPUTED: No
Quality log:
Iteration 1: Comp 5, Acc 4 → Need private sector + timelines
Iteration 2: Comp 8, Acc 7 → Good coverage, strengthen citations
Iteration 3: Comp 9, Acc 8 → Done ✓
Use: Complex questions, comparisons, due diligence, state-of-art surveys Don't use: Simple lookups (use web_search directly), opinions, creative writing
Use the AskUserQuestion tool at key decision points throughout the deep research workflow:
Scope clarification (Step 1):
Topic: "Research renewable energy"
→ Use AskUserQuestion tool:
Question: "Renewable energy is broad. What aspect should I focus on?"
Options:
- "Current technology comparison (solar, wind, etc.)"
- "Economic viability and cost trends"
- "Policy and regulatory landscape"
- "Specific geography or market"
Research brief validation (Step 2):
After drafting research brief
→ Use AskUserQuestion tool:
Question: "Does this research brief capture your needs?"
Options:
- "Yes, proceed with research"
- "Adjust scope (I'll specify)"
- "Add specific questions to address"
- "Change constraints or focus"
Quality iteration decision (Step 8):
Iteration 2: Comprehensiveness 6, Accuracy 7, Avg 6.5
→ Use AskUserQuestion tool:
Question: "Quality at 6.5/10 after 2 iterations. Continue or finalize?"
Options:
- "Continue to iteration 3 (target 7+)" (Recommended)
- "Good enough, finalize now"
- "Focus on specific gaps: [describe]"
Source contradiction (Step 6):
Major sources disagree: Source A (confidence 85) says X, Source B (confidence 80) says Y
→ Use AskUserQuestion tool:
Question: "Authoritative sources conflict. How to resolve?"
Options:
- "Present both views with confidence levels"
- "Search for additional tiebreaker sources"
- "Favor more recent source"
- "Flag as unresolved, note in limitations"
Report depth selection (Step 9):
Research complete, ready for final report
→ Use AskUserQuestion tool:
Question: "What level of detail in the final report?"
Options:
- "Full report with all methodology details"
- "Executive summary with key findings"
- "Detailed findings, minimal methodology"
- "Just the sources with confidence ratings"
tools
Validate a FlowWorkflow YAML at `plugins/flow/workflows/<id>.workflow.yaml` against `schemas/v1/workflow.schema.json` AND cross-reference the referenced skills/agents exist + every Tier 3 action is confirm-gated + no native /goal or /loop dependency is declared. Use when /flow:workflow validate is invoked, when CI runs the workflow schema gates, or when a new workflow is being authored. This skill MUST be consulted because schema validation alone catches shape errors; cross-reference validation catches the silent-correctness failures (typo'd skill name, Tier 3 escape, /goal dependency) that would otherwise ship to users.
tools
Verify UI-facing changes by running a screenshot-analyze-verify loop across configured viewports, with a browser-tool priority cascade (Playwright MCP → Chrome DevTools MCP → CLI fallback → external skill fallback) and bounded iteration. Use after build/runtime verification passes and the diff includes `.tsx`/`.jsx`/`.vue`/`.html`/`.css`/`.scss`/`.svelte` files OR the acceptance criteria mention UI/page/render/display/visual. This skill MUST be consulted because UI changes that pass build and unit tests can still ship blank pages, render-blocking console errors, or broken responsive layouts that no other verification phase catches.
data-ai
Coordinate agent teams for adversarial review (paired skeptic/verifier per facet, challenge round with disposition vocabulary, consolidated findings with confidence) or parallel implementation (task sizing 5-6 per teammate, non-overlapping files). Enforces independent analysis before shared conclusions. Reference only (`disable-model-invocation: true`); loaded only when `agentTeams: true` in settings.
development
Conduct two-stage code review: Stage 1 verifies spec compliance (criterion-to-code mapping), Stage 2 evaluates security, correctness, performance, and maintainability across 6 parallel facets with P1/P2/P3 synthesis and deduplication by file:line. Use when reviewing code changes or pull requests. This skill MUST be consulted because reviewing quality on broken logic is wasted effort, and unmet acceptance criteria must block merge.