coherence-check SKILL.md skillA
coherence-check from linxule/interpretive-orchestration is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add linxule/interpretive-orchestration/coherence-check@git:20260201.0665adbPins git:20260201.0665adb in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- linxule/interpretive-orchestration
- Path
plugin/skills/coherence-check/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260201.0665adb, committed Feb 1, 2026
- Size
- 4,981 bytes
- Repository stars
- 21
- License
- a license file GitHub does not identify
This skill should be used when users question their philosophical stance, their language contradicts their declared epistemology, they are moving between stages and want to verify coherence, mentions 'assumptions', 'examine', 'coherent', 'consistent', or something feels 'off' about their analytical approach.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# coherence-check Examine philosophical assumptions and check for methodological coherence. Ensures alignment between ontology, epistemology, and analytical practice. ## When to Use Use this skill when: - User questions their philosophical stance - User's language contradicts their declared epistemology - Moving between stages and wanting to verify coherence - User mentions "assumptions", "examine", "coherent" - Something feels "off" about the analytical approach - User asks "am I being consistent?" ## What It Checks ### 1. Language Coherence Are you using language consistent with your philosophical stance? | Stance | Appropriate | Avoid | |--------|-------------|-------| | Constructivist | construct, interpret, build | discover, find, extract | | Objectivist | discover, identify, find | construct, create | | Critical Realist | uncover, reveal, understand | construct (pure form) | ### 2. Method-Epistemology Alignment Does your analytical approach match your epistemology? | Epistemology | Aligned Method | Tension Flag | |--------------|----------------|--------------| | Co-constructive | Reflexive journaling, positionality | Claiming objectivity | …
Read the whole file at its exact version.
How to install
mdr add linxule/interpretive-orchestration/coherence-check@sha256:12d9166f0080307fThe line at the top of this page pins the label git:20260201.0665adb, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_mfceb6ilqsieb6so)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Feb 1, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4981 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
linxule/interpretive-orchestration · 21 stars · license a license file GitHub does not identify · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mfceb6ilqsieb6so GET https://markdownregistry.com/api/v1/resolve?ref=linxule/interpretive-orchestration/coherence-check GET https://markdownregistry.com/api/v1/blob/12d9166f0080307f359c4051550ccd71162bc4bf8deb04e5d0f443bf2086e89f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.