CtrlK
BlogDocsLog inGet started
Tessl Logo

epistemic-protocols

github.com/jongwony/epistemic-protocols

SkillAddedReview
apportion

merismos/skills/apportion/SKILL.md

Use when the user is about to hand one goal to an autonomous run, or asks for it to be planned for one, and no plan yet says when each unit is done. The user takes a plan of units with checks, accepted gaps and held judgments, seeing what needed settling first and what returns at the end.

50

bound

horismos/skills/bound/SKILL.md

Use when what a task needs decided is not yet visible — which decisions it turns on, what to keep or entrust, and with whom — before work proceeds on that undrawn boundary; not where the direction a source gives already settles it, or nothing would await the user. The user can then see each decision, what rests on it, its cost if wrong, what settled it, and what stays open and with whom.

44

conduct

hyphegesis/skills/conduct/SKILL.md

Use before work that needs several lines of thinking whose order, independence, combination, stopping point or destination is not obvious; scale or budget alone is no reason. The user can then say how the lines order, combine, stop and where results go, what they entrusted and kept, and own the method.

40

contextualize

epharmoge/skills/contextualize/SKILL.md

Use when a result, this session's or one brought in, may not fit where it lands or may leave out what was asked, or when the user asks to check that fit; opened without the user's call only where a mismatch has actually been detected, saying so. The user sees each misfit found, settled or withdrawn, and the fixes carried out and reread until nothing is open.

48

elicit

euporia/skills/elicit/SKILL.md

Use when the request itself does not say what result the user wants — it names an area or a wish, such as 'fix this up' or 'make it better', but not what should change; judged from the request, before files or context are looked at to guess it, even where they would suggest a plausible reading. Not where the user's words already settle it. The user can then say 'this is my intent, aligned enough', each value in their own words, what they left open carried.

49

encapsulation

.claude/skills/encapsulation/SKILL.md

This skill should be used when the user asks to "audit plugin encapsulation", "check self-containment semantics", "find contributor-knowledge assumptions", or invokes /encapsulation. Reviews LLM-facing prose in this project's plugin SKILL.md files and plugin description metadata for Plugin Encapsulation compliance: prose that assumes contributor documentation knowledge or rephrases banned references to bypass deterministic checks. Project-local contributor tooling.

64

formal-review

.claude/skills/formal-review/SKILL.md

This skill should be used when the user asks to "formal review", "formal lens review", or invokes /formal-review. A fixed-lens PR review for this repository's formally-structured protocol changes: it pins a Category Theory / Type Theory / Operational Semantics lens panel over only the files changed in a PR, analyzes each lens in isolation, adversarially cross-verifies the findings, and posts the survivors as a single consolidated PR comment. Project-local contributor tooling.

68

gate-check

epistemic-cooperative/skills/gate-check/SKILL.md

Advisor-checked decision gates. Freezes a drafted option set, has an independent external advisor rule it genuine / collapsed / malformed, then verifies the cited grounds before it reaches the user.

49

grasp

katalepsis/skills/grasp/SKILL.md

Use when the user signals they want to understand something already in play — a result, a document, a file, work done for them — that they cannot follow yet or nod along to unsure; not for an unrelated question or an account that already shows understanding. The user can then say their understanding serves their purpose, on a map checked with them.

49

ground

analogia/skills/ground/SKILL.md

Use when a framework, analogy, earlier design or sibling structure is to be carried to a case, or an abstraction tested against its own cases, and what it licenses there is still open — judged from the request, before either side is read and compared; not where what the mapping licenses is already settled, or the user only wants an explanation. The user can then say what carries each conclusion, what would break it, and whether it holds, is blocked, or is open.

46

ideate

heuresis/skills/ideate/SKILL.md

Use when the user asks to widen, open or rethink a field of ideas that is empty, narrowed too early, or thin; a field merely looking narrow does not start it. The user can then see one map from their words and what they name — frames, branches, idea origins, the unexplored — and take it, nothing chosen.

50

induce

periagoge/skills/induce/SKILL.md

Use when the user senses that cases at hand share something no one has named yet, or that a name in use no longer says what its cases show, and wants it named; applying a fixed meaning to a disputed case is not this. The user can then name it, say which cases it takes in and leaves out, and recognize it as serving their goal.

48

inquire

aitesis/skills/inquire/SKILL.md

Use before gathering context — opening a link or issue, reading records, threads, documents, files or state to establish what is the case, a status check or a claim the user makes in passing included — even where the agent could gather it itself; not for a command whose targets are named or already in context and that claims nothing beyond them. The user can then recognize what was settled and from where, what rests on weak or unreached ground, and what only they decide.

51

onboard

epistemic-cooperative/skills/onboard/SKILL.md

Quick protocol recommendation from recent sessions, or quest-based learning through scenario, trial, and quiz.

53

outcome

.claude/skills/outcome/SKILL.md

This skill should be used when the user asks to "run the outcome eval", "paired bare vs protocol", "which decisions did the protocol surface", "count what the AI asked or presented", "does /inquire surface what the request left out", or wants to see, from transcripts, which decisions reached the user as a question or something to recognize instead of having to be written into the opening prompt. Project-local contributor tooling.

68

preview

proplasma/skills/preview/SKILL.md

Use when the user is about to commit to one of several directions they cannot judge from descriptions — a choice deferred to a principle, the options reworked instead of chosen, or 'I'd have to see it'. The user can then say what each means for their purpose, on what ground, and which one they take.

48

probe

epistemic-cooperative/skills/probe/SKILL.md

Something feels off and the user cannot name what is stuck: the user can then say what it is — a shown candidate, their own words, or none shown — having seen what each rests on and what rules it out.

47

realize

.claude/skills/realize/SKILL.md

This skill should be used when the user asks to "run the eval", "test whether the protocol actually works at runtime", "check type realization", "measure protocol fulfillment", "run the type-realization suite", "does the gate actually stop", or wants runtime evidence that a protocol's formal transition contract is realized rather than an assessment of downstream artifact quality. Invoke explicitly with /realize and a skill argument.

61

recollect

anamnesis/skills/recollect/SKILL.md

Use when the user reaches for something past they cannot name or locate — a discussion, line of work, topic, session or settled concept — by a vague time, an existence claim without a locator, or visible recall effort; not when they give an exact reference or seek new information. Finds it in past records so the user recognizes it in a story, knowing it took place, not that it still holds.

52

rederive

.claude/skills/rederive/SKILL.md

This skill should be used when a contributor names a skill whose Lean contract is to be re-derived — a core protocol, a utility skill, or a contributor skill whose formal block is or becomes Lean — or invokes /rederive. Runs the per-skill flow: gather the pre-understanding, derive the skill's epistemic solution and fuse it with the contributor's horizon, then read the current contract against it, through sketch, edit and rehearsal, to the fusion of the contributor's horizon on the rehearsal result. Project-local contributor tooling.

53