Categorize knowledge claims into facts, tests, assumptions, and beliefs.
npx skills add https://github.com/baphled/dotopencode --skill epistemic-rigor
Please help me install this Agent Skill. Skill: epistemic-rigor Source: https://github.com/baphled/dotopencode/tree/main/skills/epistemic-rigor Command: npx skills add https://github.com/baphled/dotopencode --skill epistemic-rigor
This Skill helps you maintain intellectual honesty by clearly distinguishing between facts, tests, assumptions, and beliefs, preventing decisions based on false confidence.
Use the epistemic rigor skill to analyze the certainty of the claim that 'the new caching layer will improve performance'.
High-intent search queries and answers about installing and using this skill.
To distinguish facts from assumptions in decision making, categorize knowledge claims by their epistemic state. This process clarifies whether confidence is proven by tests, inferred logically, or based on intuition, preventing decisions built on false confidence.
Intellectual honesty in knowledge management is the practice of naming epistemic states and admitting uncertainty. It matters because it mitigates risk by preventing teams from acting on unverified beliefs or untested assumptions during critical workflows.
Assess the certainty of a claim before deploying by testing before trusting. Identify if the claim's stability is a fact supported by tests, an assumption from logical inference, or a belief rooted in intuition, ensuring you only act on verified information.
Critical thinking frameworks help with debugging and code reviews by clarifying the basis and confidence level of information. They require naming epistemic states to separate tested facts from unverified assumptions, directly targeting hidden errors.
The best way to handle uncertainty in technical claims is to explicitly name epistemic states and require testing before trusting. This approach acknowledges unknowns directly, mitigating risk by preventing actions based on false confidence or untested intuition.
AgentientElicit stakeholder knowledge and define problems with epistemic tracking.
wojonsIdentifies, documents, and tests implicit assumptions in software artifacts.
whichguyGenerate candidate questions and estimate information value using decision theory.
vvieira010-pixelGuide learners through a three-step claim check for AI-generated content.
