deep-research/skills/using-deep-research/SKILL.md
This skill should be used when the user asks 'how do I do deep research', 'show me research skills', 'help me research a topic', 'what research methodology should I use', or at the start of any structured web research task. Provides the index of all deep research principle skills and the /research command.
npx skillsauth add oborchers/fractional-cto using-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.
Structured deep research transforms ad-hoc web searches into a repeatable, hallucination-resistant research pipeline. Without deliberate structure, research agents gravitate toward the first sources found, fail to verify claims, and produce confident reports built on unreliable foundations.
This plugin provides 4 methodology skills and the /deep-research:research command for orchestrated multi-agent research sessions.
Use the Skill tool to invoke any skill by name. When invoked, follow the skill's guidance directly.
| Skill | Triggers On |
|-------|-------------|
| deep-research:research-methodology | Starting any research task — query analysis, decomposition strategies, effort scaling, dynamic replanning, stopping criteria |
| deep-research:source-evaluation | Evaluating sources — credibility ranking (T1-T6 tiers), multi-provider search strategy, SEO spam detection, domain-specific source selection |
| deep-research:hallucination-prevention | Any research output — hallucination taxonomy, citation verification rules, circuit breaker patterns, confidence scoring, cascading prevention |
| deep-research:synthesis-and-reporting | Combining findings — deduplication, conflict resolution, narrative construction, citation formatting, report quality assessment |
Invoke a skill when there is even a small chance the work touches one of these areas:
research-methodology to plan decomposition and effort scalingsource-evaluation to assess what you findhallucination-prevention to verify before statingsynthesis-and-reporting to merge and cite properlyFor full orchestrated research sessions, use /deep-research:research. The command:
research-worker agents (Sonnet) — each writes findings with a Verifiable Claims Tableresearch-verifier agents (Sonnet) — each re-fetches sources and checks claims independentlyresearch-synthesizer agent (Opus) — applies corrections, merges findings, writes final document with Confidence AssessmentAll research skills rest on three foundations:
Every claim needs a source — No unsourced assertions. If it cannot be cited, it cannot be stated as fact. Flag uncertainty explicitly.
Source quality determines output quality — 57% of research errors originate in early retrieval. Front-load high-quality sources. Prefer primary sources (T1-T2) over secondary sources.
Verify before synthesizing — Treat each agent's output as untrusted input. Cross-reference claims between sources. Use deterministic validation where possible.
tools
This skill should be used when the user invokes any /plan-* command from the planning-tools plugin (/plan-context, /plan-master, /plan-open-questions, /plan-verify, /plan-tick, /plan-progress, /plan-delete), asks how Claude Code's plan files work, asks where plans are stored, asks to author or audit a multi-phase master planning document, asks how to walk through a plan's Open Questions interactively, asks how to write progress entries, or mentions ~/.claude/plans/ or .claude/planning-tools.local.md. Provides the index of planning-tools commands, the master-plan workflow lifecycle, the v0.3.0+ list-shape mandate (phases and questions as headings + bulleted scope items, never tables), the v0.3.2+ plain-bullet shape (no `- [ ]` checkboxes — heading emoji is the sole tick signal), the progress-entry methodology, and the mechanics of Claude Code's plan-mode file storage.
testing
This skill should be used when the user is adjusting spacing, padding, margins, content density, section gaps, vertical rhythm, or separation between elements. Also applies when reviewing whether a design feels cramped or too sparse, choosing between borders and whitespace for separation, or defining a spacing system. Covers the 4px/8px spacing system, macro vs micro whitespace, content density spectrum, separation techniques (whitespace > background shifts > borders), and vertical rhythm.
development
This skill should be used when the user is defining brand personality in design, choosing between illustration and photography, adding motion or animation, creating visual motifs, ensuring layout variety, customizing CSS framework defaults, or calibrating the level of creative expression for a given context. Covers Lavie & Tractinsky's expressive aesthetics, the expression spectrum (restrained to bold), brand personality translation, illustration systems, photography direction, and template independence.
development
This skill should be used when the user is establishing visual importance, designing headings, creating focal points, designing CTAs or buttons, arranging label-data relationships, implementing scanning patterns (F-pattern, Z-pattern), or ensuring one dominant element per screen. Covers the three levers of hierarchy (size, weight, color), three-tier information architecture, the 'emphasize by de-emphasizing' principle, CTA design, and label-data relationships.