agentleFS
zerniezernie/vigiles/.claude/skills/deep-research/SKILL.md

deep-research

Skill15 starsChanged 5 months agoMITView on GitHub

Use when the user asks to research a topic in depth, map a competitive/market landscape, run a multi-source investigation, or "fan out" parallel research agents — anything where many findings must be gathered and then NOT lost. Enforces durable, detail-preserving research (write full findings to disk; keep a full appendix beside the synthesis).

196 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use community-led-growth, ph-community-outreach and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • W-MoorerSkill

    academic-paper-reviewer

    Multi-perspective academic paper review with dynamic reviewer personas. Simulates 5 independent reviewers (EIC + 3 peer reviewers + Devil's Advocate) with field-specific expertise. Supports full review, re-review (verification), quick assessment, methodology focus, Socratic guided, and calibration modes. Triggers on: review paper, peer review, manuscript review, referee report, review my paper, critique paper, simulate review, editorial review, calibrate reviewer, reviewer calibration, measure reviewer accuracy.

    Also in 11 projects that use this

  • W-MoorerSkill

    academic-pipeline

    Orchestrator for the full academic research pipeline: research -> write -> integrity check -> review -> revise -> re-review -> re-revise -> final integrity check -> finalize. Coordinates deep-research, academic-paper, and academic-paper-reviewer into a seamless 10-stage workflow with mandatory integrity verification, two-stage peer review, and reproducible quality gates. Triggers on: academic pipeline, research to paper, full paper workflow, paper pipeline, end-to-end paper, research-to-publication, complete paper workflow.

    Also in 10 projects that use this

  • stophobiaSkill

    surprise-me

    Create a delightful, unexpected "wow" experience for the user by dynamically discovering and creatively combining other enabled skills. Triggers when the user says "surprise me" or any request expressing a desire for an unexpected creative showcase. Also triggers when the user is bored, wants inspiration, or asks for "something interesting".

    Also in 4 projects that use this

  • HK-hubSkill

    consulting-analysis

    Use this skill when the user requests to generate, create, or write professional research reports including but not limited to market analysis, consumer insights, brand analysis, financial analysis, industry research, competitive intelligence, investment due diligence, or any consulting-grade analytical report. This skill operates in two phases — (1) generating a structured analysis framework with chapter skeleton, data query requirements, and analysis logic, and (2) after data collection by other skills, producing the final consulting-grade report with structured narratives, embedded charts, and strategic insights.

    Also in 5 projects that use this

  • +5 more from nicepkg
  • +1 more from W-Moorer

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 178 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every nontrivial research effort produces, and SAVES to disk:

    line 17
  2. Distinctive:

    If the saved synthesis is dramatically smaller than what was gathered, the appendix is how you reconcile that — the detail must land …

    line 23
  3. Distinctive:

    Mandate write-to-disk in the subagent prompt: Every research subagent must WRITE its full findings to a durable file (e.g.

    line 31
  4. Distinctive:

    NOT rely on the agent's returned summary as the record — it is trimmed by construction and its transcript is ephemeral.

    line 34
  5. Distinctive:

    When in doubt which, ask — but never let "unsure where" become "saved nowhere."

    line 53
  6. Distinctive:

    Don't present a one-paragraph chat summary as the deliverable for a 15-agent fan-out.

    line 57
  7. Very specific:

    Don't trim sources/URLs/dates to make the brief shorter — that detail goes in the appendix.

    line 58
  8. Distinctive:

    Don't leave the only full copy in an ephemeral transcript or scratchpad you didn't commit.

    line 59

“Common” is measured: kept by at least 6 in 10 of the 178 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Deep research — gather wide, lose nothing

The failure mode this skill exists to prevent: a big parallel research fan-out gathers 80–100K tokens of detail, each subagent returns a trimmed summary, the orchestrator compresses again into a short brief, and the raw findings live only in ephemeral agent transcripts (scratchpad task outputs) that vanish when the container is reclaimed. Net: expensive research → a thin artifact, detail gone. Don't do that.

The rule: two durable artifacts, never just one

Every nontrivial research effort produces, and SAVES to disk:

  1. A synthesis — the brief / answer (tables, thesis, recommendation).
  2. A full appendix — the per-source / per-company / per-angle DETAIL (raw numbers, funding histories, surfaces, dates, verbatim source URLs) the synthesis compressed.

If the saved synthesis is dramatically smaller than what was gathered, the appendix is how you reconcile that — the detail must land somewhere durable, not only in chat or a transcript. "I summarized it in chat" is not saved.

Running a fan-out

  1. Plan the angles — one subagent per distinct angle (company, source class, sub-question). Tell the user which model each runs on and why (the subagent-model-note rule).
  2. Mandate write-to-disk in the subagent prompt. Every research subagent must WRITE its full findings to a durable file (e.g. the session scratchpad dir, one file per angle) with sources verbatim, and return only a short pointer + the headline findings. Do NOT rely on the agent's returned summary as the record — it is trimmed by construction and its transcript is ephemeral.
  3. Capture sources verbatim — every claim carries [number] [source URL] [date] [reported vs estimate]. URLs are the first thing lost in compression; keep them.
  4. Synthesize from the files, not from memory — read back the written files to build the synthesis, so nothing silently drops.
  5. Save both artifacts before declaring done — commit/write the synthesis AND the appendix. Then it's saved.

Where to save

  • Technical research about shipped behaviour → a docs/ page if a user needs it to act, otherwise a contributor note cited from CLAUDE.md (a file() ref where the decision it informs is written — not a new keyFiles entry, the field is deprecated) so it isn't an orphan doc. Which tier is decided by public-vs-internal-docs and doc-tiers.
  • Competitive, market, pricing, go-to-market or roadmap research → not into this repository, in any directory. This repo is public and no-product-strategy-here is unconditional: a deleted file stays in history and on other branches. Hand the findings back in the answer and let the human place them somewhere private.
  • When in doubt which, ask — but never let "unsure where" become "saved nowhere."

Don't

  • Don't present a one-paragraph chat summary as the deliverable for a 15-agent fan-out.
  • Don't trim sources/URLs/dates to make the brief shorter — that detail goes in the appendix.
  • Don't leave the only full copy in an ephemeral transcript or scratchpad you didn't commit.
<!-- vigiles:ignore-test — project-local workflow skill, not a shipped vigiles surface -->

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.