S4h Epistemology Knowledge Types logo

S4h Epistemology Knowledge Types

Organization
human-avatar
s4h-epistemology-knowledge-types

Maps what kind of knowing is actually in play for a claim or question. Distinguishes a priori from a posteriori knowledge; propositional (knowing that) from procedural (knowing how) from acquaintance (knowing of); and knowledge sourced from perception, inference, testimony, intuition, or memory. Use when you say 'what kind of claim is this', 'is this something we can reason our way to or do we need evidence', 'they're treating this as obvious but I don't think it is', 'is this really an empirical question', or when you need to assess what standards of justification apply before testing whether a claim is true.

Overview

Publisherhuman-avatar
Repositoryskills-for-humanity
Skill names4h-epistemology-knowledge-types
Stars
234
Forks
24
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by human-avatar on GitHub. Read the source before you install it.

Installation

Install the S4h Epistemology Knowledge Types AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/human-avatar/skills-for-humanity/tree/main/skills/s4h-epistemology-knowledge-types
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/human-avatar/skills-for-humanity.git /tmp/skills-for-humanity
mkdir -p .claude/skills
cp -r /tmp/skills-for-humanity/skills/s4h-epistemology-knowledge-types .claude/skills/s4h-epistemology-knowledge-types
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable S4h Epistemology Knowledge Types in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads S4h Epistemology Knowledge Types on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so S4h Epistemology Knowledge Types is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Epistemology: Knowledge Types

Before you can test whether a claim is justified, you need to know what kind of claim it is — because different kinds of knowing have different justification standards, different failure modes, and different evidentiary requirements. Mixing up knowledge types is a recurring source of bad reasoning: treating empirical claims as if they're matters of pure logic, treating intuitions as if they're perceptions, treating testimony as if it's first-hand knowledge.

This skill classifies the kind of knowing in play, then draws out what that classification implies for how the claim can be established or challenged.


Your Process

Step 1: Extract the Claim State the claim being made as precisely as possible. Strip away rhetorical packaging. What exactly is being asserted?

Framing check: Confirm the specific claim before continuing. State what you've identified — the actual claim being analyzed and the context in which it is being made — in one sentence, then use AskUserQuestion:

  • Question: "I'm reading this as: [your one-sentence framing of the specific claim and context]. Is that right?"
  • Header: "Framing"
  • Options:
    • Yes — proceed — framing is correct
    • Adjust — one element is off; user will correct it before you continue
    • Reframe — different situation than read; incorporate the correction before proceeding

Step 2: Classify Along the Primary Axis — A Priori vs. A Posteriori

  • A priori — can be known through reason alone, independent of experience. True by definition, logical necessity, or mathematical proof. Examples: "all bachelors are unmarried," "2+2=4," "if A>B and B>C then A>C."

    • Test: could this be false if the world were different? If no, it's a priori.
    • Failure mode: confusing definitional truths with empirical claims ("free markets are efficient" can be made a priori by definition, but that makes it empty rather than powerful).
  • A posteriori — requires experience and evidence. Could be false; the world could have been otherwise. Examples: "water boils at 100°C at sea level," "this product's NPS is 42."

    • Test: would we need to investigate the world to know if it's true? If yes, it's a posteriori.
    • Failure mode: treating empirical claims as if they've been established when they've only been assumed.

Step 3: Classify the Form of Knowing

  • Propositional (knowing that) — a fact or state of affairs. "The conversion rate dropped." "Keynes believed X." Most analytical claims are propositional. Can be true or false; can be supported by evidence; can be transmitted by testimony.

  • Procedural (knowing how) — a skill or capacity. "Knowing how to ride a bicycle." "Knowing how to negotiate." Cannot be fully reduced to propositions — you can know all the facts about cycling and still not know how to ride. Failure mode: confusing explanation (propositional) with competence (procedural). Particularly relevant in organizations: knowing about a process is not the same as being able to execute it.

  • Acquaintance (knowing of) — direct familiarity through experience. "Knowing Paris." "Knowing what grief feels like." Richer than testimony but harder to transmit. Failure mode: assuming shared acquaintance when the other person only has propositional knowledge (talking about a difficult customer as if the other person knows what it's like to manage them).

Step 4: Classify the Source

SourceWhat it providesKey vulnerability
PerceptionDirect sensory evidenceObservation errors, selection effects, limited perspective
InferenceConclusions drawn from other knowledgeDepends on validity of chain and truth of premises
TestimonyKnowledge passed from othersReliability of the source, transmission errors, motivated reporting
IntuitionFast, pattern-based judgmentHard to articulate; may encode bias; often reliable in expert domains
MemoryRetained past experienceReconstructive, not reproductive; degrades; subject to post-hoc editing

Step 5: Assess the Epistemic Implications

Given what kind of knowing is in play:

  • What evidence is actually relevant to this claim?
  • What evidence is irrelevant but being treated as relevant?
  • What can this kind of knowing establish — and what does it categorically not establish?
  • Is the person making the claim aware of the limits of their knowledge type?

Step 6: Identify the Type Confusion (if any)

The most common errors:

  • Treating a posteriori claims as if they were a priori — "obviously," "of course," or "any reasonable person would agree" applied to empirical claims.
  • Treating testimony as if it were perception — "I heard that..." treated with the same weight as "I saw that..."
  • Treating procedural knowledge as if it were propositional — assuming that explaining a skill is equivalent to conferring it.
  • Treating intuitions as evidence — strong feeling that X used as if it were observation of X.

Human Check-in

Before proceeding, use the AskUserQuestion tool. State your interpretation of the situation in 1–2 sentences — what is being analyzed and what the core question is — then ask:

  • Question: "My read: [your 1–2 sentence interpretation]. How do you want to proceed?"
  • Header: "Scope"
  • Options:
    • Full classification — Complete all steps with the epistemic implications drawn out
    • Type and implications only — Classify quickly and flag what follows, skip full source analysis
    • Identify the confusion — Focus on what knowledge-type error is being made, skip full taxonomy
    • Refine the claim — Sharpen what we're analyzing before starting

Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis.


Output Format

The Claim

[Exact claim being analyzed]

Primary Classification

A priori / A posteriori: [Classification + one sentence justification]

Form of Knowing

Type: Propositional / Procedural / Acquaintance Notes: [Why this classification matters here]

Source Analysis

Source in PlayWeight GivenAssessment
[Perception / Inference / Testimony / Intuition / Memory]High / Medium / Low[Is this appropriate? Any vulnerabilities?]

Epistemic Implications

What this kind of knowing can establish:

  • [Point 1]
  • [Point 2]

What it cannot establish:

  • [Limit 1]
  • [Limit 2]

Type Confusion (if any)

Confusion identified: [Specific error] Effect on the argument: [What this means for the claim's validity]

Upshot

[One clear paragraph: what is the person actually dealing with here, and what follows for how they should reason about or act on this claim?]


Notes

Use epistemology-justification when you've classified the knowledge type and now want to test whether the belief is actually justified. Use epistemology-epistemic-status when you need to calibrate confidence across a whole domain rather than analyze one claim. Use logic-check when the issue is inference validity rather than knowledge-type misclassification.


What's Next

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

  • Question: "Knowledge types classified. What's next?"
  • Header: "Next"
  • Options:
    • /s4h-epistemology-epistemic-status — Assign epistemic status to each knowledge type
    • /s4h-decision-criteria-weighting — Weight decision criteria by the type and reliability of knowledge
    • /s4h-investigation-evidence-audit — Audit evidence quality for each knowledge type
    • Done — Wrap up and synthesise what we have so far

Frequently asked questions

What does the S4h Epistemology Knowledge Types AI skill do?

Maps what kind of knowing is actually in play for a claim or question. Distinguishes a priori from a posteriori knowledge; propositional (knowing that) from procedural (knowing how) from acquaintance (knowing of); and knowledge sourced from perception, inference, testimony, intuition, or memory. Use when you say 'what kind of claim is this', 'is this something we can reason our way to or do we need evidence', 'they're treating this as obvious but I don't think it is', 'is this really an empirical question', or when you need to assess what standards of justification apply before testing whet...

Why use S4h Epistemology Knowledge Types on TypingMind?

Because you install it once and use it with any model. S4h Epistemology Knowledge Types is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install S4h Epistemology Knowledge Types in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/human-avatar/skills-for-humanity/tree/main/skills/s4h-epistemology-knowledge-types. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use S4h Epistemology Knowledge Types?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with S4h Epistemology Knowledge Types?

As many as you like. As long as a model supports skills, you can use S4h Epistemology Knowledge Types with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the S4h Epistemology Knowledge Types AI skill free?

Yes. It is published on GitHub by human-avatar under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇