agentsclimarketplace

Assumption excavation

Skill markoblogo/abvx-agent-skills/skills/assumption-excavation

Reviewable capability layer for coding agents. Portable skills, delivery gates, workflow patterns, and verification-first engineering.

Install
npx -y skills add markoblogo/abvx-agent-skills --skill assumption-excavation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Surface hidden assumptions in plans, specs, AGENTS.md, SKILL.md, SET bundles, and workflow contracts before implementation or handoff. Use when an artifact looks plausible but may rely on unstated environment, dependency, behavioral, temporal, or success assumptions.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.1 KB, as published. Nobody here has run it

Assumption Excavation

Find what the artifact takes for granted before those assumptions become implementation bugs.

Use When

  • reviewing PRDs, specs, plans, or issue slices before work starts;
  • reviewing AGENTS.md, SKILL.md, SET bundles, proof-loop contracts, or workflow docs;
  • a proposal sounds confident but depends on unclear prerequisites;
  • you need a lightweight pre-implementation review lens.

Workflow

  1. Identify the artifact and its intended consumer.
  2. Read for implicit assumptions, not prose quality.
  3. Classify assumptions:
    • environment: tools, services, files, auth, OS, network;
    • dependency: upstream state, input shape, prior checks;
    • behavioral: what humans, agents, or systems are expected to do;
    • temporal: what must remain stable over time;
    • success: what the artifact counts as done or safe.
  4. Rank the assumptions by fragility:
    • high: likely to break or expensive if wrong;
    • medium: plausible risk with manageable fallout;
    • low: visible but not blocking.
  5. Mark partially surfaced assumptions as PARTIAL.
  6. Recommend what must be clarified, tested, or accepted before implementation.

Output Shape

Use:

  • verdict: EXAMINED or UNEXAMINED;
  • top assumptions, ranked;
  • fragility score or severity per item;
  • missing evidence;
  • smallest clarification or verification step.

Guardrails

  • Do not rewrite the artifact unless asked.
  • Do not treat assumptions as errors by default; some are deliberate.
  • Do not block on low-risk assumptions.
  • State uncertainty as text-based inference, not mind reading.

Provenance

Adapted from the assumption-excavator pattern in aself101/agents-and-pipelines, compressed for ABVX skill use and broader repo-contract review.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.