qual-examine-assumptions SKILL.md skillA
qual-examine-assumptions 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/qual-examine-assumptions@git:20261106.bb3d139Pins git:20261106.bb3d139 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/qual-examine-assumptions/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261106.bb3d139, committed Nov 6, 2026
- Size
- 12,091 bytes
- Repository stars
- 21
- License
- a license file GitHub does not identify
Surface epistemic foundations through Socratic questioning and coherence checking.
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
# /qual-examine-assumptions - Surface Your Epistemic Foundations ## Purpose Use reflexive Socratic questioning to examine the ontological and epistemological assumptions underlying your analytical work. This is philosophical archaeology - excavating the invisible foundations of your thinking. --- ## When to Use This ### Perfect For: - **Beginning a project** - clarify your philosophical stance before coding - **Feeling philosophical confusion** - sense something's off but can't articulate what - **After major analytical decisions** - check if choice aligns with your declared stance - **Before manuscript writing** - ensure claims match your epistemology - **When mixing methodologies** - validate philosophical compatibility - **Regular philosophical hygiene** - monthly assumption check ### Signals You Need This: - Using words like "discover" when your stance is constructivist - Claiming objectivity when your method is interpretive - Mixing Glaserian and Charmaz language unconsciously - Reviewers questioning your philosophical coherence - YOU questioning your philosophical coherence - Feeling incoherent without knowing why --- ## What This Command Does …
Read the whole file at its exact version.
How to install
mdr add linxule/interpretive-orchestration/qual-examine-assumptions@sha256:4afa787f35bff8c7The line at the top of this page pins the label git:20261106.bb3d139, 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_ncepzhmwae7tjsyl)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Nov 6, 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 (12091 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_ncepzhmwae7tjsyl GET https://markdownregistry.com/api/v1/resolve?ref=linxule/interpretive-orchestration/qual-examine-assumptions GET https://markdownregistry.com/api/v1/blob/4afa787f35bff8c73cb9dc8cf84555e2974bd01546c302888eea8ae5573c7602
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.