methodological-rules SKILL.md skillA
methodological-rules 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/methodological-rules@git:20261106.ab6c96fPins git:20261106.ab6c96f 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/methodological-rules/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261106.ab6c96f, committed Nov 6, 2026
- First version recorded
- Feb 1, 2026
- Size
- 11,055 bytes
- Repository stars
- 21
- License
- a license file GitHub does not identify
This skill should be used when users mention 'generate rules', 'isolation rules', 'methodology preset', 'apply preset', 'saturation', 'am I saturated', 'branch', 'fork', 'explore alternative', 'team', 'add researcher', 'intercoder reliability', 'dashboard', 'show status', or after /qual-design completes.
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
> Script paths: `${CLAUDE_PLUGIN_ROOT}` below is this plugin's root folder, two levels above this skill's own folder. Claude Code fills it in. If you see it unfilled, still starting with a dollar sign (as in Codex, Copilot CLI or Kimi Code), put that folder's absolute path in its place before you run a command.
# Methodological Rules Skill
Comprehensive methodological support: isolation rules, strain detection, saturation tracking, workspace branching, multi-researcher collaboration, and visualization.
---
## When to Use This Skill
**Triggers:**
- "generate rules" / "create rules" / "isolation rules"
- "methodology preset" / "apply preset"
- "saturation" / "am I saturated" / "theoretical saturation"
- "branch" / "fork" / "explore alternative"
- "team" / "add researcher" / "intercoder reliability"
- "dashboard" / "show status" / "visualize"
- After `/qual-design` completes
- When research_design changes in config
**Auto-invoked:**
- By `PostPhaseTransition` hook when sandwich_status changes
- By `project-setup` skill after design configuration
---
## What This Skill Does
1. **Reads research design** from `config.json`
2. **Generates Claude Code rules** in `.claude/rules/`
…Read the whole file at its exact version.
How to install
mdr add linxule/interpretive-orchestration/methodological-rules@sha256:16192a3cd829fc0bThe line at the top of this page pins the label git:20261106.ab6c96f, 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_u6j4i3zzsnw47me5)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Feb 1, 2026 and Nov 6, 2026, about one every 70 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261106.ab6c96f latest | 2026-11-06 | ab6c96f | 11,055 B | A | view · diff |
| git:20261106.dc3b202 | 2026-11-06 | dc3b202 | 10,881 B | A | view · diff |
| git:20261106.fabdbaf | 2026-11-06 | fabdbaf | 10,726 B | A | view · diff |
| git:20261106.bb3d139 | 2026-11-06 | bb3d139 | 10,412 B | A | view · diff |
| git:20260201.0665adb | 2026-02-01 | 0665adb | 9,908 B | A | view |
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 (11055 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_u6j4i3zzsnw47me5 GET https://markdownregistry.com/api/v1/resolve?ref=linxule/interpretive-orchestration/methodological-rules GET https://markdownregistry.com/api/v1/blob/16192a3cd829fc0ba014a7404ef50de7f2b59add13a906f3c18b26fde111b275
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.