uncertainty-blindspot-audit
Skill2 starsChanged 2 months agoNo licenceView on GitHub
You MUST use this skill for substantive analysis, research, planning, decisions, forecasts, diagnoses, code reviews, strategy work, and any request to evaluate, critique, review, stress-test, challenge assumptions, find risks, identify missing factors, or explain what may be wrong or overlooked. Trigger it even when the user does not name this skill, including natural requests such as "what am I least certain about", "what is the biggest blind spot", "what are we missing", or "what could invalidate this plan". After completing the main task, identify the highest-impact uncertainties and blind spots, distinguish verified facts from inferences, and provide minimal validation actions. Do not trigger for casual conversation, simple translation, routine formatting, or straightforward lookups unless the user explicitly asks for an audit.
In this repository7 other files it gives its agents.
- course-outline-to-obsidianSkill
- dependency-setupSkill
- first-principleSkill
- inno-packagerSkill
- oq-governanceSkill
- question-makerSkill
- reference-first-devSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 17 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈17
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.