Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Epistemology

ASecurity

Entry point for the epistemology toolkit. Routes to the right skill based on your situation. Use when you say 'what do I actually know here', 'is this knowable', 'how certain should I be', 'what would justify believing this', 'what kind of claim is this', 'am I confusing assumption with knowledge', 'what are the limits of what we can establish', or want philosophical rigor applied to questions of knowledge without knowing which specific tool fits.

19 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgoawstesting

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill epistemology --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Epistemology?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Epistemology
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-epistemology/badge)](https://www.skillsdirectory.com/skills/rondoflow-epistemology)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: epistemology
description: "Entry point for the epistemology toolkit. Routes to the right skill based on your situation. Use when you say 'what do I actually know here', 'is this knowable', 'how certain should I be', 'what would justify believing this', 'what kind of claim is this', 'am I confusing assumption with knowledge', 'what are the limits of what we can establish', or want philosophical rigor applied to questions of knowledge without knowing which specific tool fits."
---

# Epistemology

Applies philosophical analysis to the nature, structure, and limits of knowledge. Diagnoses what kind of epistemic work is needed and routes to the right tool.

Epistemology is the meta-layer: not "is this claim true?" but "what kind of truth could this claim even have? What would justify believing it? How certain can we actually be?" It's most useful when you've hit a wall with ordinary investigation — when more evidence-gathering won't settle things, when you're not sure what *kind* of knowing is in play, or when you want honest calibration rather than confident-sounding output.

## Which tool fits

| You need to... | Tool |
|---|---|
| Map what *kind* of knowing is in play | epistemology-knowledge-types |
| Work out what would actually *justify* believing something | epistemology-justification |
| Get honest calibration: what do I know vs. believe vs. assume vs. hope? | epistemology-epistemic-status |
| Find out what can't be known, and why — and what *can* be established | epistemology-limits |

## Routing Decision

- **"What kind of claim is this?" / "Am I reasoning from evidence, intuition, testimony, or something else?"** → knowledge-types (classify the epistemic mode before testing the claim)
- **"What would it take to actually know this?" / "What would justify believing X?"** → justification (map the justification structure and find the weakest link)
- **"How certain should I be?" / "Give me an honest read of what we know vs. assume"** → epistemic-status (calibrate and map confidence across a domain)
- **"Can this even be known?" / "We keep investigating and nothing settles it"** → limits (classify the type of limit and reframe into the answerable)
- **Unclear** → epistemic-status (starts with honest inventory of what's known, naturally surfaces which deeper question matters)

## Confirm Direction

After diagnosing which tool fits, use the `AskUserQuestion` tool to confirm direction. Construct the question dynamically to include your diagnosis:

- **Question:** "My read: **[diagnosed tool]** — [one sentence on why it fits]. How would you like to proceed?"
- **Header:** "Direction"
- **Options:**
  - **Yes, run that tool** — Execute the diagnosed skill immediately using the context already provided
  - **Show all options** — List every skill in this category with one-line descriptions
  - **Quick version** — Run a lighter-weight pass if one fits this situation
  - **Re-diagnose** — Revisit the situation description for a different read

Proceed based on their selection.

---

## Knowledge Types

*Map what kind of knowing is actually in play — before testing whether the claim is true.*

Identify the claim → classify what kind of knowing it invokes (a priori vs. a posteriori; propositional vs. procedural vs. acquaintance; sourced from perception, inference, testimony, or intuition) → assess what can and can't be established by that type. Different kinds of knowing have different standards of justification and different failure modes.

**Output:** Claim classified by knowledge type, with implications for what evidence is relevant and what the claim can and can't establish.

---

## Justification

*What would actually justify believing this?*

Identify the belief → ask what would need to be true for it to be justified → classify the justification structure (foundationalist, coherentist, or reliabilist) → identify the weakest link in the chain. A belief can feel well-supported while resting on an unjustified foundation — justification analysis makes the load-bearing structure visible.

**Output:** Justification map with the belief's foundational support structure, classification of the justification type, and the specific point where the chain is weakest.

---

## Epistemic Status

*Honest, rigorous calibration: what do you know vs. believe vs. assume vs. hope?*

Inventory all claims in a domain → assign each an epistemic status (known, reasonably believed, assumed, hoped, unknown) → trace dependencies: which high-confidence claims rest on lower-confidence foundations? Draws from the rationalist tradition of explicit epistemic labeling to replace confident-sounding vagueness with precise, honest calibration.

**Output:** Structured epistemic status map across the domain, with dependency chains flagged where confident claims rest on shakier ground.

---

## Limits

*What can't be known here, and why — and what *can* be established within those limits?*

Identify what you're trying to know → classify the type of limit if one exists (fundamental: Gödel-style, underdetermination, observer effects; practical: evidence unavailable, destroyed, or counterfactual; conceptual: the question may be malformed) → clarify what *can* be established within those limits → reframe the question into the answerable part. The point is not to conclude "we can't know" — it's to be precise about what kind of knowing is and isn't available.

**Output:** Limit classification, what remains establishable, and a reframed question targeting the knowable.

---

## What's Next

After delivering this output, use `AskUserQuestion` to offer the next move:

- **Question:** "Epistemology applied. What's next?"
- **Header:** "Next"
- **Options:**
  - `/investigation` — Apply practical investigation methods to what epistemology clarified
  - `/probability-confidence-calibration` — Calibrate your confidence given the epistemic analysis
  - `/logic-check` — Validate reasoning built on the epistemic foundations
  - **Done** — Wrap up and synthesise what we have so far

Attribution

rondoflowrondoflow
View sourceMore from rondoflow →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693621 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →