spec-mining SKILL.md skillA
spec-mining from alexander-danilenko/cortex-claude-code-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add alexander-danilenko/cortex-claude-code-plugins/spec-mining@git:20261013.ecfffa1Pins git:20261013.ecfffa1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- alexander-danilenko/cortex-claude-code-plugins
- Path
plugins/engineering/cortex-modernization/skills/spec-mining/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261013.ecfffa1, committed Oct 13, 2026
- Size
- 3,109 bytes
- Repository stars
- 17
- License
- MIT
Apply this opinionated workflow when reverse-engineering legacy or undocumented systems: scope, explore the code, trace data flows, document in EARS format, flag uncertainties. For code archaeology, onboarding, and requirements extraction.
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
# Spec Mining Extract a specification from a system that has no usable documentation, by reading the code that actually runs. The discipline that makes the output trustworthy: **separate what you observed from what you inferred.** A reader will act on this document — rebuilding a service, planning a migration, onboarding — and a confident-sounding guess is worse than an acknowledged gap, because nobody goes back to check it. ## Approach Work outside-in: entry points, then routes, then the services behind them, then the data layer. Following an actual request path teaches you the system's real structure, which is often not the structure its directory names advertise. Read the tests too. They document intended behaviour and edge cases someone hit in production, and they are usually more honest than any comment or README in the repo. Read the migration history as well. Migrations are dated and ordered, so they show how the schema arrived at its current shape — which columns were added under pressure, what was backfilled, what was renamed but never dropped. That sequence is often the only surviving record of why the data model looks the way it does. …
Read the whole file at its exact version.
How to install
mdr add alexander-danilenko/cortex-claude-code-plugins/spec-mining@sha256:f9b3675b5f307687The line at the top of this page pins the label git:20261013.ecfffa1, 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_t35ktnxusys5dx5u)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 13, 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 (3109 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
alexander-danilenko/cortex-claude-code-plugins · 17 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_t35ktnxusys5dx5u GET https://markdownregistry.com/api/v1/resolve?ref=alexander-danilenko/cortex-claude-code-plugins/spec-mining GET https://markdownregistry.com/api/v1/blob/f9b3675b5f3076878c4d3a4653c9f1edb4b4cb01ee6e6de79944dee9a95d14d9
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 alexander-danilenko/cortex-claude-code-plugins
Every file in alexander-danilenko/cortex-claude-code-plugins