qual-characterize-patterns SKILL.md skillA
qual-characterize-patterns 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-characterize-patterns@git:20261106.76517b2Pins git:20261106.76517b2 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-characterize-patterns/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261106.76517b2, committed Nov 6, 2026
- First version recorded
- Nov 6, 2026
- Size
- 5,626 bytes
- Repository stars
- 21
- License
- a license file GitHub does not identify
Develop dimensional analysis of patterns through systematic characterization.
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.
# Pattern Characterization Command
This command guides you through dimensional analysis - moving from "what patterns exist" to understanding "how patterns vary" and "under what conditions."
## Overview
Pattern characterization is where your categories become theory. You're not just labeling data; you're understanding the structure, variation, and relationships within your patterns.
## What is Dimensional Analysis?
Dimensional analysis asks:
- **Properties:** What are the defining characteristics of this pattern?
- **Dimensions:** How do these properties vary?
- **Conditions:** Under what circumstances do patterns appear/vary?
- **Consequences:** What follows from different dimensional profiles?
- **Relationships:** How do patterns relate to each other?
## The Characterization Process
### Step 1: Select a Pattern to Characterize
…Read the whole file at its exact version.
How to install
mdr add linxule/interpretive-orchestration/qual-characterize-patterns@sha256:b4d0fbfe0d221cbfThe line at the top of this page pins the label git:20261106.76517b2, 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_war6zki45wu26rm2)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, all committed on Nov 6, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261106.76517b2 latest | 2026-11-06 | 76517b2 | 5,626 B | A | view · diff |
| git:20261106.fabdbaf | 2026-11-06 | fabdbaf | 5,647 B | A | view · diff |
| git:20261106.c8b5d8a | 2026-11-06 | c8b5d8a | 5,333 B | A | view · diff |
| git:20261106.bb3d139 | 2026-11-06 | bb3d139 | 5,331 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 (5626 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_war6zki45wu26rm2 GET https://markdownregistry.com/api/v1/resolve?ref=linxule/interpretive-orchestration/qual-characterize-patterns GET https://markdownregistry.com/api/v1/blob/b4d0fbfe0d221cbf2ef429c3331339f1e35cb7c1d6e779855c4eb80cf5d50574
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.