deep-research

Research problem domains via web search and save structured, source-grounded notes.

Updated Jul 15, 2026
One-click install
npx skills add https://github.com/Kurorz2004/alphaz-coral --skill deep-research-kurorz2004
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-research
Source: https://github.com/Kurorz2004/alphaz-coral/tree/main/vrp/evidence/full/full-s1/.coral/public/skills/deep-research
Command: npx skills add https://github.com/Kurorz2004/alphaz-coral --skill deep-research-kurorz2004

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Starting a coding or optimization task without domain knowledge leads to weak first attempts and repeated dead ends. This Skill structures the pre-coding research phase: it guides broad-to-focused web searches, preserves raw sources for verification, and produces synthesized research notes with an index so findings persist across sessions. ## Core Features & Use Cases - Structured research workflow: Survey 3+ approaches, compare 2-4 candidates on evidence and complexity, then commit to one before writing code. - Immutable raw source archive: Capture web articles, papers, GitHub repos, videos, threads, docs, and chat logs into notes/raw/ with per-type frontmatter conventions. - Failure-mode recovery: Diagnose and recover from blocked WebFetch calls, empty search results, contradictory sources, stale notes, and underexplored topics. - Grounding verification: Optionally spawn a Synthesis Reviewer subagent that verdicts every claim in a note as grounded, partially-grounded, inferred, contradicted, or unverifiable against its cited sources. - Use Case: Before implementing a CVRP solver, use this Skill to survey state-of-the-art heuristics, save the key papers to notes/raw/, write a comparison note in notes/research/, and pick an approach backed by benchmark evidence. ## Quick Start Ask the agent to research the problem domain before coding, saving raw sources and writing structured research notes with an updated index.

Frequently Asked Questions about deep-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I research a problem domain before writing code?

Run 3-5 focused web searches starting broad (surveys, state of the art) then narrowing to specific techniques and implementations. Save each useful source to a raw notes directory, compare 2-4 candidate approaches on evidence and complexity, then write a synthesized research note before coding.

How do I save web sources so research notes stay verifiable?

Fetch each source and store the full content as an immutable file in a raw/ directory with frontmatter recording URL, type, and capture date. Research notes link back to these raw files, so claims can be re-verified even if summaries drift.

What should I do when WebFetch fails or returns an empty page?

Try the URL through web.archive.org, search the document title for mirrors, or look for RSS/API endpoints on JavaScript-rendered pages. For paywalled papers, search title plus author plus pdf to find free preprints; never fabricate an unreachable source.

How do I handle sources that contradict each other?

Read the methods sections of both sources to find the scope difference, such as dataset, scale, or definitions. Document the contradiction explicitly in the research note with the conditions under which each claim holds rather than silently picking one side.

How can I verify a research note is grounded in its sources?

Spawn the Synthesis Reviewer subagent, which reads the note alongside its linked raw sources and returns a per-claim verdict of grounded, partially-grounded, inferred, contradicted, or unverifiable in a JSON report. It also flags unused sources and confidence mismatches.

When should I update an existing research note instead of creating a new one?

Always update the existing note when a new source covers the same topic; never fork a v2 file. Re-synthesize from all linked sources, append the new reference, and mark superseded claims rather than deleting the file to preserve the audit trail.