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.
In this repository79 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- abuseipdb-apiSkill
- achSkill
- campaign-trackingSkill
- carding-financial-fraudSkill
- censys-apiSkill
- china-cyber-espionageSkill
- claim-extractionSkill
- confidence-levelsSkill
- control-coverage-mappingSkill
- crowdstrike-apiSkill
- cti-hyperloopSkill
- cti-orchestratorSkill
- cti-setupSkill
- darkweb-collectionSkill
- devils-advocacySkill
- domain-investigationSkill
- dprk-cyber-espionageSkill
- feedback-loopsSkill
- greynoise-apiSkill
- hacktivismSkill
- hash-investigationSkill
- horizon-scanningSkill
- indicator-pivotingSkill
- infostealersSkill
- initial-access-brokersSkill
- intelligence-sharingSkill
- intelligence-writingSkill
- ioc-enrichment-workflowSkill
- ioc-exportSkill
- ip-investigationSkill
- iran-cyber-espionageSkill
- kql-writingSkill
- likelihood-languageSkill
- lookup-abuseipdbSkill
- lookup-censysSkill
- lookup-crowdstrikeSkill
- lookup-greynoiseSkill
- lookup-liberty91Skill
- lookup-mispSkill
- lookup-openctiSkill
- lookup-otxSkill
- lookup-ransomwareliveSkill
- lookup-reversinglabsSkill
- lookup-sentinelSkill
- lookup-shodanSkill
- lookup-urlscanSkill
- lookup-virustotalSkill
- malware-analysisSkill
- maturity-assessmentSkill
- mitre-attackSkill
- osint-methodologySkill
- otx-apiSkill
- phishing-social-engineeringSkill
- pir-managementSkill
- quality-controlSkill
- quality-of-information-checkSkill
- ransomware-ecosystemSkill
- reversinglabs-apiSkill
- The first 60 shown.
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
- Distinctive: line 11
Every analytical judgment rests on assumptions — often unstated.
- Distinctive: line 16
Write the current assessment or conclusion in one clear sentence.
- Very specific: line 41
Every assessment and attribution claim with load_bearing: true gets a row in the matrix, even when the assumption looks safe.
- Distinctive: line 43
Do not regrade claims here.
- Distinctive: line 56
High: If wrong, the conclusion changes significantly
- Distinctive: line 57
Medium: If wrong, the conclusion weakens but may still hold
- Distinctive: line 58
Low: If wrong, the conclusion is largely unaffected
- Distinctive: line 72
Should the confidence level of the overall assessment be lowered?
≈ “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.
Files
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 table | How the analysis uses it | Assumption to record |
assessment | Stated as fact, or as a premise for a further judgement | That the source's judgement about intent, capability or future behaviour is correct |
attribution | Actor named without the source's hedge | That the attribution holds. Quote stated_confidence verbatim |
actor_claim | Scale, victim or data figures repeated as fact | That the actor is telling the truth |
Any type, flagged caveats_dropped_in_chain | Outlet's stronger wording used | That the claim is as strong as the outlet made it, not as the primary wrote it |
Any type, flagged single_source or with corroboration unchecked | Relied on without qualification | That the one primary is right |
Any type, flagged stale or superseded | Used as current | That nothing has changed since publication |
Rules:
- Every
assessmentandattributionclaim withload_bearing: truegets a row in the matrix, even when the assumption looks safe. - Carry the
claim_idinto 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
| Assumption | Claim | Importance | Confidence | Status |
| [Assumption 1] | C01 | High | High | Validated |
| [Assumption 2] | C04 | High | Low | FLAG |
| [Assumption 3] | none | Medium | Medium | Monitor |
| [Assumption 4] | C02, C06 | Low | High | Accepted |
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]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
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.

