agentleFS
VercelKnown publishervercel/eve/apps/templates/eve-sre-agent-template/agent/skills/deep-investigation/SKILL.md

deep-investigation

Skill5.9k starsChanged 3 days agoApache-2.0View on GitHub

Investigate an operational problem to determine what happened, assess its impact, and recommend next steps using a hypothesis-backed approach.

2 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about vercel/eve

The biggest 5 of 57 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 57

Talked about on GitHub and Bluesky (57 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 7

2 more on Bluesky

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    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:

    Use available context first.

    line 22
  2. Distinctive:

    After identifying what went wrong, generate 2-4 plausible root-cause hypotheses.

    line 28
  3. Distinctive:

    Do not require a validated root cause.

    line 47
  4. Distinctive:

    Do not infer customer impact from an error or alert alone.

    line 60
  5. Distinctive:

    If the invoking prompt prescribes an exact output shape, follow it and fold the findings below into those sections rather than adding more …

    line 75
  6. Distinctive:

    Do not assume the request represents a declared incident.

    line 91
  7. Distinctive:

    Do not require a root cause before giving useful next steps.

    line 92
  8. Distinctive:

    If the task is to validate one specific hypothesis, do not generate new hypotheses.

    line 93

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Evidence-Backed Investigation

Investigate an operational problem using relevant evidence to explain what happened, assess the impact, and identify useful next steps.

Procedure

1. Understand the request

Scan the conversation for:

  • The reported symptom or unexpected behavior
  • The affected service, environment, region, or workflow
  • The relevant timestamps or time range
  • Links to external context
  • What the user needs to decide or do

Use available context first. Fetch additional context when it can change the conclusion or next action.

Perform a quick scan using available tools to determine if the problem is related to a recent, ongoing incident.

2. Generate hypotheses

After identifying what went wrong, generate 2-4 plausible root-cause hypotheses. Each must include:

  • A short label
  • Why the hypothesis is plausible based on the available context
  • The signals that can validate or invalidate it

Prioritize the most plausible hypotheses and the signals most likely to distinguish between them.

3. Validate hypotheses and determine what happened

Investigate each hypothesis using the hypothesis-validation skill. For each hypothesis, determine whether it is validated, invalidated, or inconclusive and explain the conclusion with specific evidence.

Establish:

  • What changed or failed
  • When it started
  • Whether it is ongoing, recovering, or resolved
  • Which explanation is best supported by the evidence

Do not require a validated root cause. Clearly distinguish observed facts, supported explanations, and unknowns.

Record findings as you validate. Follow the Evidence rules in the agent instructions. Call evidence_record, evidence_remove, and evidence_list as those rules say.

4. Assess the impact

Determine:

  • Which services, endpoints, regions, workflows, or users are affected
  • How severe and widespread the effect is
  • Whether the impact is increasing, stable, decreasing, or no longer present
  • Which important impact could not be confirmed

Do not infer customer impact from an error or alert alone.

5. Choose next steps

Recommend 1-4 concrete actions based on the evidence. Prioritize actions that:

  • Reduce current impact
  • Confirm an important unknown
  • Restore normal operation
  • Prevent an unsafe or premature change

State what each action is expected to accomplish. Do not recommend broad follow-up work unless it helps with the current decision.

Result

If the invoking prompt prescribes an exact output shape, follow it and fold the findings below into those sections rather than adding more headings. Otherwise, answer with:

What happened

A short explanation of the observed behavior, timeline, current state, and best-supported cause. State important unknowns. Include related or recurring incidents only when this turn's evidence shows them. Do not state that no related incident exists because you do not have complete incident history to search.

Impact

The confirmed scope and severity. Clearly identify impact that could not be confirmed.

Next steps

A ranked list of 1-4 concrete actions for the responder.

Boundaries

  • Do not assume the request represents a declared incident.
  • Do not require a root cause before giving useful next steps.
  • If the task is to validate one specific hypothesis, do not generate new hypotheses. Use the hypothesis-validation skill.

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.