agentleFS
VercelKnown publishervercel/eve/apps/templates/eve-sre-agent-template/agent/skills/hypothesis-validation/SKILL.md

hypothesis-validation

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

Given a hypothesis, take the necessary investigation steps to validate, invalidate, or reach an inconclusive result for the hypothesis.

1 other project uses a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 7 mentionsJul 2026: 12 mentionsAug 2026: 6 mentionsSep 2026: 10 mentionsOct 2026: 17 mentionsNov 2026: 4 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the vercel/eve repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about vercel/eve

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

See all 56

Talked about on GitHub and Bluesky (56 times).

On GitHub · 49

44 more on GitHub

On Bluesky · 7

2 more on Bluesky

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    After identifying possibly relevant context, dig deep into the most relevant pieces of context to gather enough evidence to validate, …

    line 26
  2. Distinctive:

    After gathering enough evidence, draw a final conclusion about the hypothesis.

    line 32
  3. Distinctive:

    Do not use this skill to run a full investigation.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Hypothesis Validation

Investigate the related context for a given hypothesis holistically. Record evidence and conclude whether the hypothesis is validated, invalidated, or inconclusive.

Procedure

1: Context hydration

Scan the conversation for:

  • alert or incident metadata
  • service names, environment names, region hints
  • timestamps or time ranges
  • symptoms (errors, latency, downtime)
  • links to external pieces of context

The goal here is getting a quick hydration of possibly relevant context for the hypothesis before doing a deeper dive.

2: Dig deep

After identifying possibly relevant context, dig deep into the most relevant pieces of context to gather enough evidence to validate, invalidate, or reach an inconclusive result for the hypothesis.

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

3: Draw conclusions

After gathering enough evidence, draw a final conclusion about the hypothesis. The conclusion for the hypothesis should be "validated", "invalidated", or "inconclusive". Include a description that cites the most important pieces of evidence used to draw the conclusion.

Result

A synthesized conclusion for the hypothesis.

Boundaries

  • Do not use this skill to run a full investigation. Use the deep investigation 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.