assumptions
Skill64 starsChanged 5 months agoMITView on GitHub
Manage the assumption registry — track, verify, and query assumptions about external dependencies and system behavior. Prevents costly rediscovery of known failures.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- rory660/lookout-skillstheir own version, first seen Oct 11, 2026
- dimitritholen/1337-claudetheir own version, first seen Sep 23, 2026
- Usermuse/em-plugintheir own version, first seen Jul 31, 2026
- Teycir/Assumptionstheir own version, first seen Jul 26, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- Teycir/Assumptions★ 19same name
- rory660/lookout-skills★ 1same name
- dimitritholen/1337-claude★ 0same name
- Usermuse/em-plugin★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository102 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- assumptionsSkill
- capture-learningSkill
- Codex-opus-4-6-promptingSkill
- Codex-promptSkill
- mcp-code-modeSkill
- deploy-team-hubSkill
- diagramSkill
- distillSkill
- effect-tsSkill
- escalateSkill
- evalSkill
- experimentSkill
- hddSkill
- hub-auditSkill
- hub-collabSkill
- implementSkill
- knowledgeSkill
- peer-notebook-delivery-guardSkill
- research-taskSkill
- session-reviewSkill
- source-command-hdd-decideSkill
- source-command-hdd-hddSkill
- source-command-hdd-researchSkill
- source-command-hdd-stage-adrSkill
- source-command-hdd-validateSkill
- statusSkill
- supabaseSkill
- synthesizeSkill
- tasteSkill
- teamSkill
- test-suiteSkill
- theseus-protocolSkill
- thoughtbox:debugSkill
- thoughtbox:decisionSkill
- thoughtbox:evolutionSkill
- thoughtbox:knowledge-querySkill
- thoughtbox:onboardSkill
- thoughtbox:refactorSkill
- thoughtbox:researchSkill
- thoughtbox:session-reviewSkill
- thoughtbox-teamSkill
- ulc-loopSkill
- ulysses-protocolSkill
- workflow-brainstormingSkill
- workflow-ideationSkill
- workflow-reflectionSkill
- workflow-revisionSkill
- workflows-compoundSkill
- workflowSkill
- workflows-planSkill
- workflows-reviewSkill
- workflows-workSkill
- workflow-tournamentSkill
- capture-learningSkill
- claude-opus-4-6-promptingSkill
- claude-promptSkill
- mcp-code-modeSkill
- deploy-team-hubSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Read all .assumptions/*.jsonl files
- Very specific: line 24
Create a new assumption record in .assumptions/registry.jsonl:
- Distinctive: line 44
Read the assumption record by ID
- Very specific: line 46
Update last_verified timestamp and confidence score
- Very specific: line 47
If verification fails, add to failure_history and reduce confidence
- Very specific: line 48
If confidence drops below 0.3, mark status as suspect and warn
- Distinctive: line 51
Read all assumption records
- Distinctive: line 88
Always end with a summary:
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Manage assumptions: $ARGUMENTS
Commands
Parse the first word of $ARGUMENTS to determine the command:
list — Show all tracked assumptions
- Read all
.assumptions/*.jsonlfiles - Parse each line as a JSON record
- Display sorted by confidence (lowest first) or staleness (oldest verification first)
- Format as a table: ID | Category | Claim | Confidence | Last Verified | Status
add — Register a new assumption
Parse remaining arguments for: --category, --claim, --evidence, --source
Create a new assumption record in .assumptions/registry.jsonl:
{
"id": "<category>-<short-slug>",
"category": "<api|dependency|behavior|environment|tooling>",
"claim": "<what we assume to be true>",
"evidence": "<what supports this assumption>",
"source": "<where this was discovered>",
"confidence": 0.8,
"created": "<ISO 8601>",
"last_verified": "<ISO 8601>",
"verification_method": "<how to test this>",
"failure_history": [],
"status": "active",
"blast_radius": "<what breaks if this assumption is wrong>"
}verify — Re-verify an assumption
- Read the assumption record by ID
- Execute the verification method (may involve web search, API calls, or code checks)
- Update
last_verifiedtimestamp andconfidencescore - If verification fails, add to
failure_historyand reduce confidence - If confidence drops below 0.3, mark status as
suspectand warn
stale — Show assumptions that need re-verification
- Read all assumption records
- Filter to those where
last_verifiedis more than 14 days ago - Sort by blast_radius (highest first)
- Display with suggested verification actions
seed — Seed registry from MEMORY.md gotchas
- Read MEMORY.md
- Extract entries from "Gotchas", "Known Bugs", and "MCP Knowledge API Gotchas" sections
- For each entry, create an assumption record with:
- category: inferred from content (api, dependency, behavior, etc.)
- claim: the gotcha statement
- evidence: "Discovered empirically" + date from MEMORY.md
- confidence: 0.9 (verified by experience)
- verification_method: suggested test
Schema
Each assumption record:
| Field | Type | Required | Description |
| id | string | yes | Unique identifier (category-slug format) |
| category | enum | yes | api, dependency, behavior, environment, tooling |
| claim | string | yes | What we assume to be true |
| evidence | string | yes | What supports this claim |
| source | string | yes | Where this was discovered (session, test, docs) |
| confidence | float | yes | 0.0 to 1.0 confidence score |
| created | string | yes | ISO 8601 creation timestamp |
| last_verified | string | yes | ISO 8601 last verification timestamp |
| verification_method | string | no | How to re-test this assumption |
| failure_history | array | no | Past verification failures with timestamps and details |
| status | enum | yes | active, suspect, retired, verified |
| blast_radius | string | no | What breaks if this assumption is wrong |
| dependencies | array | no | Other assumptions this depends on |
Output
Always end with a summary:
## Assumption Registry Status
Total: {N} assumptions
Active: {N} | Suspect: {N} | Retired: {N}
Stale (>14 days): {N}
Highest blast radius unverified: {assumption_id}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.

