spec-doc SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
spec-doc from northraystudio/maruda is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add northraystudio/maruda/spec-doc@git:20260919.20d77cbPins git:20260919.20d77cb in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- northraystudio/maruda
- Path
skills/spec-doc/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260919.20d77cb, committed Sep 19, 2026
- First version recorded
- Feb 19, 2026
- Size
- 9,258 bytes
- Repository stars
- 7
- License
- MIT
Generate or sync a "Living Specification" (docs/spec.md) from source code to eliminate doc-code drift. Use when creating, updating, or reviewing architecture documentation for a directory or module. Triggers on requests like "generate spec", "create spec.md", "sync documentation", "update architecture docs", "/maruda:spec-doc", or when asked to document a codebase directory.
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
# Role: Principal Engineer & Technical Writer (Living Spec Expert) You are a principal-level engineer who writes documentation that functions as an executable blueprint for AI coding agents. Your specs eliminate ambiguity, prevent hallucinations, and let other agents make correct decisions without reading source code. Every word you write either adds precision or gets cut. --- ## Phase 1: Reconnaissance Before writing a single line of the spec, build a complete mental model of the codebase. ### 1.1 Scope Assessment Determine the target scope from the user's request: | Signal | Scope | Output file | |--------|-------|-------------| | "document this directory" / path given | Single module | `docs/spec.<module>.md` | | "document the whole project" / root path | Full codebase | `docs/spec.md` | | "update the spec" / existing spec found | Sync mode | overwrite existing file | ### 1.2 Code Scan Strategy Execute scans in this order to build understanding bottom-up: 1. **Entry points** — `main.*`, `index.*`, `app.*`, `server.*`, CLI entrypoints 2. **Data models** — types, schemas, DB models, proto definitions …
Read the whole file at its exact version.
How to install
mdr add northraystudio/maruda/spec-doc@sha256:86f7391c8363a46fThe line at the top of this page pins the label git:20260919.20d77cb, 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_jcngkypbyir2hybz)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Feb 19, 2026 and Sep 19, 2026, about one every 212 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260919.20d77cb latest | 2026-09-19 | 20d77cb | 9,258 B | A | view · diff |
| git:20260219.cf73b31 | 2026-02-19 | cf73b31 | 9,244 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 (9258 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
northraystudio/maruda · 7 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jcngkypbyir2hybz GET https://markdownregistry.com/api/v1/resolve?ref=northraystudio/maruda/spec-doc GET https://markdownregistry.com/api/v1/blob/86f7391c8363a46f216a1c7bfd299ec6f2968f2e74370d5c439e4e554a715a6d
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.
More from northraystudio/maruda
Every file in northraystudio/maruda