developer-case-study SKILL.md skillA
developer-case-study from samber/developer-relations-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add samber/developer-relations-skills/developer-case-study@v1.0.2Pins v1.0.2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- samber/developer-relations-skills
- Path
skills/developer-case-study/SKILL.md- Versions recorded
- 4
- Latest version
- v1.0.2, committed Oct 25, 2026
- First version recorded
- Aug 28, 2026
- Size
- 26,991 bytes
- Repository stars
- 8
- License
- MIT
Turns a customer's real production deployment into a technical case study engineers believe - measured numbers tied to how they were measured, before-and-after architecture, published limitations, and cleared naming and quote approval. Use whenever the user mentions a customer case study, a technical case study, a developer adoption or success story, a reference customer, or wants to turn a user interview, migration or production rollout into published proof - even if they only say…
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
# Developer Case Study You are writing someone else's engineering story. A developer case study says: these engineers ran this technology in production, here is what changed, here is what it cost them. The reader is an engineer deciding whether the same move works in their own system - not a buyer looking for reassurance. That reader discounts an all-upside narrative on sight. Your leverage is evidence discipline and honesty about the parts that hurt, not prose polish. ## Scope check Confirm the artefact before starting. Route elsewhere when: - The system is your own and no external adopter is involved → engineering blog post skill. - The story is your own project's progress, shared as it happens → build-in-public skill. - The reader needs to learn or install something → tutorial or quickstart skill. - The material is "what shipped in v2.4" or "how to move from v1 to v2" → changelog or migration-guide skill. - The user wants a portfolio piece about work _they_ did → that is a personal case study, and its hero is the author. Say so; this skill inverts that framing. See the References section for the exact identifiers. ## Interview …
Read the whole file at its exact version.
How to install
mdr add samber/developer-relations-skills/developer-case-study@sha256:6f4da1e1d8547a23The line at the top of this page pins the label v1.0.2, 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_csp4qryjzupt6i36)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 28, 2026 and Oct 25, 2026, about one every 19 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.2 latest | 2026-10-25 | 2c2141c | 26,991 B | A | view · diff |
| v1.0.1 | 2026-09-27 | bc8ac6d | 26,986 B | A | view · diff |
| v1.0.0 | 2026-08-28 | 5705c97 | 26,621 B | A | view · diff |
| v1.0.0 | 2026-08-28 | cc3a12f | 26,621 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 (26991 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
samber/developer-relations-skills · 8 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_csp4qryjzupt6i36 GET https://markdownregistry.com/api/v1/resolve?ref=samber/developer-relations-skills/developer-case-study GET https://markdownregistry.com/api/v1/blob/6f4da1e1d8547a239a05aea712ae8c182f6332b9506009e1ba551f4ee15bb04b
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.