agentleFS
eduardoweberai-cloudeduardoweberai-cloud/claude-skills/skills/deep-research/SKILL.md

deep-research

Skill0 starsChanged 59 days agoMITView on GitHub

Deep, mode-specialized research with Memory Vault integration. Modes: deep (default — topic mastery), stack (repo/tutorial discovery), automation (process mapping + tool comparison). Saves to $MEMORY_VAULT/wiki/research/<YYYY-MM-DD>-<slug>.md with applied lens (vault auto-link, money angle, next actions, stack shortlist). Dashboard via Obsidian Dataview. Use this skill when the user invokes `/deep-research [mode] <query>` or asks for a deep, structured research with citations that should be saved to the vault for future reference.

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

  • xfstudioSkill

    micro-saas-launcher

    Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.

    Also in 5 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

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

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 5 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 178 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If QUERY is empty, prompt the user: "What do you want to research?

    line 30
  2. Very specific:

    If file missing: ABORT with veto VETO_MODE_UNKNOWN.

    line 33
  3. Distinctive:

    Check if bootstrap was run on this vault.

    line 38
  4. Very specific:

    If missing: run node scripts/bootstrap.js automatically (idempotent.

    line 40
  5. Very specific:

    Run npm install once in the skill folder before the first run.

    line 41
  6. Distinctive:

    No ETL service dependency.

    line 212
  7. Very specific:

    No Bash subshells beyond gh api for stack enrichment.

    line 213
  8. Distinctive:

    No vector store. The vault is markdown-only.

    line 215
  9. Very specific:

    No multi-vault. Assumes single $MEMORY_VAULT.

    line 217
  10. Distinctive:

    No production code generation.

    line 218

“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

Mode-specialized research pipeline. Outputs to Memory Vault. Compounds knowledge instead of consuming it.

Quick Start

/deep-research como automatizar emissao NFS-e 100% via Claude Code           # default: deep
/deep-research automation como automatizar emissao NFS-e 100% via Claude Code  # explicit automation mode
/deep-research stack saas multi-tenant boilerplate next.js supabase 2026       # explicit stack mode
/deep-research deep estado da arte de agentes autonomos 2026                   # explicit deep mode

Activation

  1. Parse $ARGUMENTS:
    • First whitespace-separated token: if ∈ {deep, stack, automation}, that's the MODE; the rest is QUERY.
    • Else MODE = deep (default), QUERY = entire $ARGUMENTS string.
    • If QUERY is empty, prompt the user: "What do you want to research? (mode default: deep)".
  2. Load modes/<MODE>.yaml via js-yaml.
    • If file missing: ABORT with veto VETO_MODE_UNKNOWN. List valid modes from modes/*.yaml minus _template.yaml.
  3. Resolve the vault: $MEMORY_VAULT if set, otherwise ~/research-vault. Below, $MEMORY_VAULT means this resolved path. If it does not exist yet, step 4 creates it (fresh vault).
  4. Check if bootstrap was run on this vault.
    • Marker: $MEMORY_VAULT/wiki/research/.gitkeep exists AND ## Research section in index.md.
    • If missing: run node scripts/bootstrap.js automatically (idempotent; creates the vault if needed). Run npm install once in the skill folder before the first run. Surface a one-line notice "Bootstrapping vault for first run." to the user.
  5. Execute the 7-phase pipeline (see below).
  6. On success, output to user:
    • File path
    • TL;DR (first paragraph of synthesis)
    • Obsidian deep-link
    • Stats: waves, sources, coverage, money angles

SKILL DEFINITION

skill:
  name: Deep Research
  id: deep-research
  version: 0.1.0

veto_conditions:
  - id: VETO_VAULT_OFFLINE
    trigger: "Resolved vault path cannot be created or written"
    action: "STOP + Report: 'Vault path not writable. Set $MEMORY_VAULT to a folder you own.'"

  - id: VETO_MODE_UNKNOWN
    trigger: "First argument matches no mode YAML in modes/"
    action: "STOP + Report: 'Unknown mode <X>. Valid: deep, stack, automation. Use /deep-research <query> for default (deep).'"

  - id: VETO_IMPLEMENTATION_REQUEST
    trigger: "User asks to implement, code, create agent/skill, or deploy"
    action: "REDIRECT: 'Implementation is not my scope. Hand it off to your implementation workflow.'"
    keywords:
      - "implementa"
      - "cria o agent"
      - "cria a skill"
      - "faz o codigo"
      - "escreve o codigo"
      - "desenvolve"
      - "deploy"
      - "implement"
      - "build this"
      - "code this"

  - id: VETO_NO_RESULTS
    trigger: "All workers return empty sources, both waves"
    action: "STOP + Report: 'No results found. Reformulate query or check internet/proxy.'"

  - id: VETO_FORBIDDEN_PATH
    trigger: "Attempt to write outside $MEMORY_VAULT/wiki/research/, index.md, log.md, or the .bak/CLAUDE.md (during bootstrap)"
    action: "BLOCK + Error."

constraints:
  forbidden_actions:
    - NEVER implement code, agents, skills, or production artifacts
    - NEVER write to wiki/_state/, wiki/notes/, wiki/concepts/, raw/, or anywhere outside research scope
    - NEVER modify $MEMORY_VAULT/CLAUDE.md except via bootstrap.js (which backs up first)

tool_hierarchy:
  search:
    1_preferred: "Exa MCP (mcp__exa__web_search_exa)"
    2_preferred: "Context7 MCP for library-specific queries"
    3_fallback: "WebSearch (always available)"
    detection: "Try preferred first. On 401/429/503 or error, fall back to next."
  docs:
    1_preferred: "Context7 (mcp__context7__resolve-library-id + query-docs)"
    2_fallback: "WebSearch site:<docs-domain>"
  deep_read:
    only: "WebFetch with prompts/search-worker.md WebFetch prompt"
  workers:
    type: "general-purpose"
    model: "haiku"
    max_parallel: 5
    max_deep_reads_per_worker: 3
    timeout_per_worker_sec: 90

workflow:
  phases:
    0_mode_bootstrap:
      tier: MAIN_INLINE
      task: Parse args, load mode YAML, verify vault, idempotent bootstrap if needed.
    1_vault_load:
      tier: SCRIPT
      task: See tasks/01-vault-load.md
      script: scripts/vault-load.js
    2_decompose:
      tier: MAIN_ULTRATHINK
      task: See tasks/02-decompose.md
      prompt: prompts/decompose.md
    3_parallel_search:
      tier: HAIKU_VIA_TASK
      task: See tasks/03-parallel-search.md
      prompt: prompts/search-worker.md
    4_evaluate_coverage:
      tier: HAIKU_VIA_TASK
      task: See tasks/04-evaluate-coverage.md
    5_synthesize:
      tier: MAIN
      task: See tasks/05-synthesize.md
      prompt: prompts/synthesize-<mode>.md
    6_applied_lens:
      tier: MAIN_PLUS_SCRIPT
      task: See tasks/06-applied-lens.md
      prompt: prompts/applied-lens.md
      script: scripts/vault-link-projects.js
    7_document:
      tier: SCRIPT
      task: See tasks/07-document.md
      scripts: [scripts/slug-generator.js, scripts/update-index.js]

security:
  - Never expose API keys, tokens, CPFs, R$ amounts, or other secrets in research docs
  - Sanitize URLs that contain auth tokens before storing
  - NEVER write outside $MEMORY_VAULT/wiki/research/ + index.md + log.md (plus one-shot CLAUDE.md patch via bootstrap)

scope_boundaries:
  allowed_paths:
    - "$MEMORY_VAULT/wiki/research/**"
    - "$MEMORY_VAULT/index.md"
    - "$MEMORY_VAULT/log.md"
    - "$MEMORY_VAULT/CLAUDE.md (only during bootstrap, with .bak)"
    - "$MEMORY_VAULT/research-dashboard.md (only during bootstrap)"
  forbidden_paths:
    - "$MEMORY_VAULT/wiki/_state/**"
    - "$MEMORY_VAULT/wiki/notes/**"
    - "$MEMORY_VAULT/wiki/concepts/**"
    - "$MEMORY_VAULT/wiki/projects/**"
    - "$MEMORY_VAULT/wiki/clients/**"
    - "$MEMORY_VAULT/raw/**"
    - ".claude/agents/"
    - ".claude/skills/ (other than this skill)"
    - "app/, lib/, src/, packages/"
  exception: "Code examples within research markdown are allowed for DOCUMENTATION only — never executed."

Execution Flow (visual)

Query → Mode Bootstrap → Vault Load (SCRIPT)
                                 |
                                 ▼
                           Decompose (MAIN+ultrathink)
                                 |
                  ┌──────────────┼──────────────┐
                  ▼              ▼              ▼
              Haiku worker  Haiku worker  Haiku worker  ... (max 5)
                  |              |              |
                  └──────────────┴──────────────┘
                                 |
                          Aggregate (MAIN)
                                 |
                          Evaluate Coverage (HAIKU)
                                 |
                          (coverage OK?) ── NO ──→ [Wave 2, max 2 total]
                                 | YES
                                 |
                          Synthesize (MAIN, mode-template)
                                 |
                          Applied Lens (MAIN + vault-link-projects.js)
                                 |
                          Document (SCRIPTS: slug + update-index, atomic)
                                 |
                          Output: path + TL;DR + Obsidian URI

What this skill does NOT do

  • No ETL service dependency.
  • No Bash subshells beyond gh api for stack enrichment.
  • No Python.
  • No vector store. The vault is markdown-only.
  • Dashboard is Obsidian Dataview only.
  • No multi-vault. Assumes single $MEMORY_VAULT.
  • No production code generation. Veto enforces this.

Output structure

$MEMORY_VAULT/wiki/research/<YYYY-MM-DD>-<slug>.md   # the research entry
$MEMORY_VAULT/index.md                                # auto-updated with new entry row
$MEMORY_VAULT/log.md                                  # auto-appended with timestamp + summary
$MEMORY_VAULT/research-dashboard.md                   # auto-aggregated via Dataview (no code change)

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.