api-versioning-strategy SKILL.md skillA
api-versioning-strategy from mohitagw15856/pm-claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mohitagw15856/pm-claude-skills/api-versioning-strategy@git:20261006.b9ea321Pins git:20261006.b9ea321 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mohitagw15856/pm-claude-skills
- Path
exports/openclaw/api-versioning-strategy/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261006.b9ea321, committed Oct 6, 2026
- First version recorded
- Jul 14, 2026
- Size
- 15,624 bytes
- Repository stars
- 1,475
- License
- MIT
Write an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.
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
# API Versioning Strategy Produce a complete API versioning strategy document that gives a service team durable, consistent rules for evolving their API without breaking consumers. This document covers the versioning scheme selection (with rationale), lifecycle policy from introduction through sunset, a precise breaking-change classification, and all the communication artifacts a team needs when deprecating a version. Engineers should be able to hand this document to a new team member or external consumer and have them understand exactly what to expect. ## Required Inputs Ask for these if not already provided: - **API type** — REST, GraphQL, or gRPC (each has different versioning mechanics) - **Current versioning approach** — URL path (`/v1/`), request header, query parameter, or none; if none, document starts fresh - **Number of existing versions and active consumer count** — needed to size the lifecycle policy and migration scope - **Deprecation timeline constraints** — any hard deadlines (contract SLAs, compliance windows, annual release cycles) - **Consumer type** — internal teams only, external partners, public API, or mix (affects communication channel choices) …
Read the whole file at its exact version.
How to install
mdr add mohitagw15856/pm-claude-skills/api-versioning-strategy@sha256:f56ac57eedb0092eThe line at the top of this page pins the label git:20261006.b9ea321, 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_i7cxzo7uas37szfv)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jul 14, 2026 and Oct 6, 2026, about one every 84 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261006.b9ea321 latest | 2026-10-06 | b9ea321 | 15,624 B | A | view · diff |
| git:20260714.b87d8d4 | 2026-07-14 | b87d8d4 | 15,507 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 (15624 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
mohitagw15856/pm-claude-skills · 1,475 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_i7cxzo7uas37szfv GET https://markdownregistry.com/api/v1/resolve?ref=mohitagw15856/pm-claude-skills/api-versioning-strategy GET https://markdownregistry.com/api/v1/blob/f56ac57eedb0092e5d399458d6e5eeaed05538e5c00ac180492ff5a2d9864b0c
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 mohitagw15856/pm-claude-skills
Every file in mohitagw15856/pm-claude-skills