Use when a decision-relevant question needs multi-source search, claim-level citations, contradiction handling, uncertainty, or a durable wiki handoff.
npx skills add https://github.com/Mark393295827/third-brain-v7-skills --skill deep-research
<skill_contract>
<input>Decision-relevant question, audience, scope, recency, source and privacy boundaries, budget, and required deliverable.</input>
<output>An answer-first synthesis with source and claim ledgers, citations, contradictions, uncertainty, and durable handoff.</output>
<done>Decision-critical claims are traceable and adversarially checked, unresolved gaps are explicit, and the stop rule is met.</done>
<non_goals>Link collection, uncited material claims, privacy leakage, exhaustive search, or autonomous high-impact experiments.</non_goals>
Research is an evidence loop, not a volume contest. Define the decision, gather the minimum diverse evidence, maintain source and claim ledgers, attack the synthesis, then stop when additional search no longer changes the answer.
Provide: research question, audience/decision, scope, recency, allowed/excluded sources, privacy boundary, budget, output format, and wiki destination if durable. Load references/research-ledgers.md for ledger schemas.
<intake>
Choose one mode: evidence brief, knowledge curation, recency pulse, domain intelligence, scientific-method audit, or heavy research. Convert the question into 3-7 information requirements, decision criteria, interruption points, and a source-access plan.
</intake>
<unknowns_gate>
If the decision, recency window, private-data authority, or source boundary materially changes the result, return NEEDS_INPUT. Record known, probeable, testable, and inaccessible unknowns. Do not treat inaccessible sources as supporting evidence.
</unknowns_gate>
<execute>
wiki-ingest rather than writing source claims directly into governed concepts.For high-stakes conclusions, use independent review. Obtain approval before accessing private systems, publishing, or launching experiments. Any durable write needs a diff-based rollback path.
</execute>
<evaluate>
Audit every material claim against the ledger. Check citation entailment, source independence, freshness, contradiction coverage, privacy, and whether the recommendation changes under plausible uncertainty. Stop when new searches repeat known evidence or cannot change the decision.
</evaluate>
<retry_policy>
max_attempts: 3 research passes: discovery, gap-fill, adversarial. A retry must target a named gap with a changed query/source class. Stop on duplicate evidence, repeated access failure, or NO_PROGRESS.
</retry_policy>
<state_contract>
Persist {run_id, status, attempt, budget, evidence, unknowns, last_error, next_action} plus question version, mode, information requirements, source/claim ledgers, search trace, contradictions, privacy decisions, approval, draft version, and rollback/write receipts.
</state_contract>
NEEDS_INPUT: scope, decision, privacy, or freshness boundary is ambiguous.INSUFFICIENT_EVIDENCE: sources cannot support the requested confidence or recommendation.BLOCKED_PERMISSION: private or restricted evidence is unavailable; exclude it explicitly.VERIFY_FAILED: citation does not entail the claim or key contradiction is unresolved.NO_PROGRESS: a changed pass yields no decision-relevant evidence.BUDGET_STOP: synthesize covered scope and list gaps. max_attempts: 3.Return status, result (answer-first synthesis and recommendation), evidence (claim/source ledgers and citations), unknowns, and next_action including approval or wiki handoff.
</skill_contract>
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.
Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.
Efficient database search tool for bioRxiv preprint server. Use this skill when searching for life sciences preprints by keywords, authors, date ranges, or categories, retrieving paper metadata, downloading PDFs, or conducting literature reviews.
Query and analyze scholarly literature using the OpenAlex database. This skill should be used when searching for academic papers, analyzing research trends, finding works by authors or institutions, tracking citations, discovering open access publications, or conducting bibliometric analysis across 240M+ scholarly works. Use for literature searches, research output analysis, citation analysis, and academic database queries.
Access USPTO APIs for patent/trademark searches, examination history (PEDS), assignments, citations, office actions, TSDR, for IP analysis and prior art searches.
Multiagent AI system for scientific research assistance that automates research workflows from data analysis to publication. This skill should be used when generating research ideas from datasets, developing research methodologies, executing computational experiments, performing literature searches, or generating publication-ready papers in LaTeX format. Supports end-to-end research pipelines with customizable agent orchestration.
Automated LLM-driven hypothesis generation and testing on tabular datasets. Use when you want to systematically explore hypotheses about patterns in empirical data (e.g., deception detection, content analysis). Combines literature insights with data-driven hypothesis testing. For manual hypothesis formulation use hypothesis-generation; for creative ideation use scientific-brainstorming.
Take mark393295827/deep-research from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.