agentleFS
UsermuseUsermuse/em-plugin/skills/deep-dive/SKILL.md

deep-dive

Skill0 starsChanged 3 months agoMITView on GitHub

Dive deep into one topic the user cares about — first ask what's top-of-mind, then answer it with a quote-rich, source-linked brief grounded in real customer evidence from the Evermuse Mock Data corpus. Use when the user picks "Dive into a topic", runs find_skills:deep-dive, or says 'let's go deep on X', 'dig into discovery / onboarding / churn', 'tell me more about what customers say on Y', or 'I want to explore a topic'. Trigger terms: deep dive, dive into a topic, go deep on, explore a topic, dig into, what's top of mind, take a closer look.

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ralplan, deep-interview and 8 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.
  • ibahgatSkill

    ralplan

    Create a strict, quality-first execution plan with explicit gates and rollback-ready sequencing.

    Also in 4 projects that use this

  • klauswgSkill

    deep-interview

    在明确批准执行之前,通过数学化歧义门控进行苏格拉底式深度访谈

    Also in 3 projects that use this

  • thoughtbotSkill

    trace

    Run a scenario and record what actually happened.

    Also in 3 projects that use this

  • sahinSkill

    execute

    Also in 4 projects that use this

  • snarktankSkill

    ralph

    Convert PRDs to prd.json format for the Ralph autonomous agent system. Use when you have an existing PRD and need to convert it to Ralph's JSON format. Triggers on: convert this prd, turn this into ralph format, create prd.json from this, ralph json.

    Also in 3 projects that use this

  • nicolasestremSkill

    brainstorm

    Structured idea generation and solution exploration with systematic analysis.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the grounding greps come back sparse, say so — "only 2 mentions, both from one account" — rather than dressing a weak signal as a trend.

    line 55

“Common” is measured: kept by at least 6 in 10 of the 23 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 Dive (one topic, taken all the way down)

A focused counterpart to broad customer research: the user names one thing that's on their mind, and you take it all the way down into the evidence — returning not a plausible guess but a quote-rich, sourced brief drawn from real conversations. This skill is often reached right after the initial report, when a pattern caught the user's eye and they want to go deeper. The move is: ask what's top of mind, then ground the answer in what customers actually said.

Step 1 — Ask what's top of mind

Open by asking the user which topic is top-of-mind for them these days — the one thing they most want to understand right now. Keep it warm and singular; you're inviting one topic to go deep on, not a checklist. For example:

What's top of mind for you these days? Name the one topic you'd most like me to dig into — onboarding, discovery, churn, a specific feature, a segment — and I'll take it all the way down into what your customers have actually said.

Then stop and await their answer. Don't guess a topic and start searching — the whole point is to go deep on their topic. If the reply is too broad or genuinely ambiguous, ask one quick narrowing question (a decision it feeds, a segment, a time window) before grounding. Try to get at least a few relevant keywords so that search works correctly.

Step 2 — Ground the topic in the corpus (required)

Once you have the topic, follow using-evermuse skill's grounding mechanics to find the relevant evidence.

Step 3 — Deliver a cited brief

Cluster the evidence into themes, and for each: demand strength (mentions across distinct accounts), the sentiment split, who said it and when, and the sharpest verbatim quote. Represent dissenting voices — don't flatten disagreement into a false consensus. Keep evidence (what customers said) separate from any context (market) you pulled.

Lead with the answer, then themes with quote blocks:

**Short answer:** [1–2 sentences that directly answer the topic they raised.]

### Theme 1 — [name] ([N mentions / M accounts], mostly [sentiment])
> "[verbatim quote]" — [Name], [Meeting], [Date] [`1`](URL)
[one line of interpretation]

### Theme 2 — …

**Dissent / nuance:** [minority view, cited]

Honesty when evidence is thin

If the grounding greps come back sparse, say so — "only 2 mentions, both from one account" — rather than dressing a weak signal as a trend. Thin evidence is itself a finding, and on a deep dive it's often the cue to recommend an interview (find_skills:interview-script).

Hand off

Close by offering the natural next move: "Want a spec from this?" (find_skills:write-feature-spec), "Brainstorm solutions?" (find_skills:brainstorm-ideas), "Prep an interview to fill the gaps?" (find_skills:interview-script), or "See everything I can do?" (find_skills:list-capabilities).


Further reading

  • Grounding mechanics: using-evermuse and its references/search-patterns.md + references/citations.md. Companion to customer-research (broad synthesis) — this skill is the single-topic deep cut.

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.