agentleFS
Liberty91LTDLiberty91LTD/cti-skills/skills/key-assumptions-check/SKILL.md

key-assumptions-check

Skill35 starsChanged 46 days agoMITView on GitHub

Use when surfacing the assumptions underlying an analytical judgment, the user asks "what are we assuming?" / "are these assumptions still valid?", or before publishing a high-impact assessment. Standard SAT applied during major assessments.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every analytical judgment rests on assumptions — often unstated.

    line 11
  2. Distinctive:

    Write the current assessment or conclusion in one clear sentence.

    line 16
  3. Very specific:

    Every assessment and attribution claim with load_bearing: true gets a row in the matrix, even when the assumption looks safe.

    line 41
  4. Distinctive:

    Do not regrade claims here.

    line 43
  5. Distinctive:

    High: If wrong, the conclusion changes significantly

    line 56
  6. Distinctive:

    Medium: If wrong, the conclusion weakens but may still hold

    line 57
  7. Distinctive:

    Low: If wrong, the conclusion is largely unaffected

    line 58
  8. Distinctive:

    Should the confidence level of the overall assessment be lowered?

    line 72

≈ “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

Key Assumptions Check

Every analytical judgment rests on assumptions — often unstated. This technique surfaces them and evaluates whether the analysis holds if assumptions are wrong.

Procedure

Step 1: State the Analytical Line

Write the current assessment or conclusion in one clear sentence.

Step 2: List All Assumptions

Brainstorm every assumption underlying the assessment. Include:

  • Assumptions about threat actor intent or capability
  • Assumptions about data completeness or accuracy
  • Assumptions about the relevance of historical patterns
  • Assumptions about the target environment
  • Assumptions about timing or sequencing

Step 3: Walk the Claim Table (when one exists)

If the assessment was built on graded evidence items from /quality-of-information-check, go through the claim table row by row. Assumptions are usually hiding in judgements that the analysis treats as observations. If there is no claim table, skip this step and leave the Claim column as "n/a".

For each claim, compare its claim_type with how the analytical line uses it:

In the claim tableHow the analysis uses itAssumption to record
assessmentStated as fact, or as a premise for a further judgementThat the source's judgement about intent, capability or future behaviour is correct
attributionActor named without the source's hedgeThat the attribution holds. Quote stated_confidence verbatim
actor_claimScale, victim or data figures repeated as factThat the actor is telling the truth
Any type, flagged caveats_dropped_in_chainOutlet's stronger wording usedThat the claim is as strong as the outlet made it, not as the primary wrote it
Any type, flagged single_source or with corroboration uncheckedRelied on without qualificationThat the one primary is right
Any type, flagged stale or supersededUsed as currentThat nothing has changed since publication

Rules:

  • Every assessment and attribution claim with load_bearing: true gets a row in the matrix, even when the assumption looks safe.
  • Carry the claim_id into the matrix. One claim can produce more than one assumption, and an assumption can rest on several claims.
  • Do not regrade claims here. The grade informs the Confidence column: claim support tentative or worse on a claim used as fact is Low or Medium confidence, never High.
  • Assumptions from Step 2 that trace to no claim are kept, with "none" in the Claim column. These have no evidence behind them at all, which is worth stating.

Step 4: Evaluate Each Assumption

AssumptionClaimImportanceConfidenceStatus
[Assumption 1]C01HighHighValidated
[Assumption 2]C04HighLowFLAG
[Assumption 3]noneMediumMediumMonitor
[Assumption 4]C02, C06LowHighAccepted

Importance: How much does the conclusion depend on this assumption?

  • High: If wrong, the conclusion changes significantly
  • Medium: If wrong, the conclusion weakens but may still hold
  • Low: If wrong, the conclusion is largely unaffected

Confidence: How sure are we this assumption is correct?

  • High: Strong evidence supports it
  • Medium: Some evidence, but not fully validated
  • Low: Little or no evidence; assumed by default

Step 5: Flag Critical Assumptions

Any assumption that is High Importance + Low Confidence is critical. These are the assumptions most likely to invalidate your analysis.

Step 6: Determine Impact

For each flagged assumption:

  • What would the conclusion be if this assumption is wrong?
  • Can this assumption be validated through additional collection?
  • Should the confidence level of the overall assessment be lowered?

Output Template

## Key Assumptions Check: [Assessment Title]

### Analytical Line
[The assessment being checked]

### Assumptions Matrix
| # | Assumption | Claim | Claim type | Access level | Claim support | Importance | Confidence | Status |
|---|-----------|:---:|:---:|:---:|:---:|:---:|:---:|:---:|
| 1 | ... | C04 | attribution | indirect | tentative | H/M/L | H/M/L | ... |

### Flagged Assumptions (High Importance + Low/Medium Confidence)
1. **[Assumption]** (C04): If wrong, [impact on conclusion]. Collection gap: [what would validate this].

### Impact on Assessment
[Does the assumptions check change the confidence level? Should the conclusion be qualified?]

### Recommended Actions
- [Validate assumption X through Y collection]
- [Lower confidence from High to Moderate because of assumption Z]

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.