solid SKILL.md skillA
solid from jorgecostamacia/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jorgecostamacia/skills/solid@git:20260709.25e0753Pins git:20260709.25e0753 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jorgecostamacia/skills
- Path
plugins/solid/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260709.25e0753, committed Jul 9, 2026
- Size
- 5,206 bytes
- Repository stars
- 2
- License
- MIT
Transversal software-engineering principles for any code in any language, frontend or backend. Use when writing new code, implementing a feature, refactoring, reviewing code, naming things, deciding where logic belongs, splitting or merging classes/modules/components, introducing an abstraction, or judging whether code is "good enough" — even when the user doesn't name a principle explicitly (e.g. "clean this up", "does this look right?", "where should this go?"). It encodes SOLID, simple…
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
# Engineering principles (transversal) These apply to **all** code — any language, any layer, front or back. They are lenses for judgment, not laws: when two of them conflict, prefer the one that makes the code easier to change tomorrow. ## The core loop 1. **Understand the behavior** you need before touching code — inputs, outputs, edge cases. If you can't state it in one sentence, you're not ready. 2. **Make the smallest change that delivers it.** No speculative parameters, no "while I'm here" abstractions. 3. **Prove it works** — a test when the code is testable; a real execution when it isn't yet. 4. **Then refactor**: better names, remove duplication (rule of three), simplify structure. Refactor with green tests, never mid-change. ## Four elements of simple design — in priority order 1. **Works** — passes its tests / observably does the job. 2. **Expresses intent** — a reader gets *what* and *why* without archaeology. 3. **No knowledge duplication** — one fact lives in one place (code repetition is only a smell when it duplicates *knowledge*). 4. **Minimal** — nothing present "just in case". YAGNI. When these conflict, the lower number wins. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_n3httz3e3no2v6fj/43925c9bbc3341c856d8624d8dd74dceb4917216c7f4d74e9ad11be2ecc925c0.json
Then /plugin install solid@markdownregistry-n3httz3e3no2v6fj in Claude Code. It installs git:20260709.25e0753, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add jorgecostamacia/skills/solid@sha256:43925c9bbc3341c8The line at the top of this page pins the label git:20260709.25e0753, 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_n3httz3e3no2v6fj)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in jorgecostamacia/skills/solid since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of solid from somewhere else? Ask it: where did my solid come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Jul 9, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/solid/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (5206 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
jorgecostamacia/skills · 2 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_n3httz3e3no2v6fj GET https://markdownregistry.com/api/v1/resolve?ref=jorgecostamacia/skills/solid GET https://markdownregistry.com/api/v1/blob/43925c9bbc3341c856d8624d8dd74dceb4917216c7f4d74e9ad11be2ecc925c0
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 jorgecostamacia/skills
Every file in jorgecostamacia/skills