Skip to content
Agentmart
Submit a tool

deep-research

Use when the task needs investigation first, especially to compare code paths, trace behavior, or synthesize findings before implementation.

Skill by Threat-Vector-Security

IndexedApache-2.0★ 13
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/threat-vector-security-deep-research

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when the task needs investigation first, especially to compare code paths, trace behavior, or synthesize findings before implementation.

Use cases: research, productivity

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/deep-research

What's inside

Skill name
deep-research
Description
Use when the task needs investigation first, especially to compare code paths, trace behavior, or synthesize findings before implementation.
License
Apache-2.0
Instructions
26 lines in SKILL.md · view on GitHub

Files (3)

  • SKILL.md
  • skill.json
  • research-brief.md · templates/

SKILL.md (first lines)

# Deep Research

Use this skill when the task needs investigation before implementation.

Workflow:
1. Define the exact question being answered.
2. Inspect the smallest relevant file and symbol set first.
3. Compare competing code paths, old vs new behavior, or proposal vs implementation.
4. Produce a concise synthesis: what is true, what is inferred, what is still unknown.

Guardrails:
- Do not start editing until the research question is answered.
- Keep notes compact and decision-oriented.
- If the investigation branches, summarize each branch separately before merging conclusions.

## Gotchas

- Do not drift from investigation into implementation just because a likely fix becomes obvious.
- Do not mix confirmed observations and inferred conclusions into one bullet list.
- Do not read the whole repo when a narrow symbol/file comparison can answer the question.

## Template

- Use `templates/research-brief.md` when the findings need to be handed off or saved as a durable brief.

From Threat-Vector-Security/guardian-agent, Apache-2.0.

More from Threat-Vector-Security/guardian-agent

Signals

Stars
13
Forks
3
Open issues
0
Last commit (this folder)
Mar 18, 2026 (7 months ago)
Last release
Sep 9, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from Threat-Vector-Security

Cite this page

deep-research skill. Agent Mart. https://agentmart.dev/skills/threat-vector-security-deep-research (last updated 2026-10-24)