qual-memo SKILL.md skillA
qual-memo 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-memo@git:20261106.c8b5d8aPins git:20261106.c8b5d8a 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-memo/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261106.c8b5d8a, committed Nov 6, 2026
- First version recorded
- Nov 6, 2026
- Size
- 5,192 bytes
- Repository stars
- 21
- License
- a license file GitHub does not identify
Write analytical memos to capture emerging insights during manual coding.
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
# Analytical Memo Writing This command guides you through writing analytical memos - the essential practice that transforms coding from labeling into theorizing. ## What is an Analytical Memo? Analytical memos are written records of your thinking as you code. They capture: - Emerging patterns and hunches - Questions and puzzles - Connections and contradictions - Methodological decisions - Reflexive observations Memos are where theory develops. They're not optional documentation - they're the engine of qualitative analysis. ## When to Write Memos Write memos: - **During coding:** When you notice something interesting - **After each document:** To consolidate observations - **When stuck:** To work through analytical challenges - **At interpretive pauses:** Every 5 documents (our methodology) - **When surprised:** Data that contradicts expectations ## Types of Memos ### Code Memos Document the development of specific codes: - What does this code capture? - What are its boundaries? - How is it similar to or different from related codes? - What variations have you seen? ### Theoretical Memos Develop conceptual insights: - What patterns are emerging? …
Read the whole file at its exact version.
How to install
mdr add linxule/interpretive-orchestration/qual-memo@sha256:330cbfb5747b4debThe line at the top of this page pins the label git:20261106.c8b5d8a, 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_chfwfzcrd5xdoats)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Nov 6, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261106.c8b5d8a latest | 2026-11-06 | c8b5d8a | 5,192 B | A | view · diff |
| git:20261106.bb3d139 | 2026-11-06 | bb3d139 | 5,190 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 (5192 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_chfwfzcrd5xdoats GET https://markdownregistry.com/api/v1/resolve?ref=linxule/interpretive-orchestration/qual-memo GET https://markdownregistry.com/api/v1/blob/330cbfb5747b4deb65b46623b13285e37aac7e694d3288499c8dfed38a2f38c3
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.