api-versioning-strategy

Implements API versioning using URL paths, headers, or query parameters with backward compatibility and deprecation strategies. Use when managing multiple API versions, planning breaking changes, or designing migration paths.

1.25x

Quality

89%

Does it follow best practices?

Impact

93%

1.25x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Evaluation results

90%

E-Commerce API Upgrade: Adding a New Version

URL path versioning structure

Criteria

Without context

With context

URL path versioning

100%

Separate route mounts

50%

100%

Both versions served

100%

Breaking changes identified

100%

Safe changes no bump

100%

N-1 support policy

100%

URL path rationale

100%

6+ month migration window

70%

100%

Migration guide commitment

Version path format

100%

39%

Retiring a Legacy Payment API Version

Deprecation headers and lifecycle

Criteria

Without context

With context

Deprecation header value

100%

Sunset header present

100%

Link successor header

100%

HTTP 410 on shutdown

100%

Deprecated phase duration

100%

Sunset Announced phase

100%

Read-Only phase

100%

Shutdown phase

100%

6+ month migration window

100%

v1 middleware placement

100%

89%

10%

Evolving a SaaS User Profile API to a New Response Format

Version adapter pattern and migration guide

Criteria

Without context

With context

Adapter function exists

100%

Adapter maps id field

80%

100%

Adapter maps name/email

80%

70%

Adapter type field

25%

Demo/runnable output

100%

Migration guide present

100%

Code examples in guide

100%

Version identification

90%

100%

No mutation of input

100%

Migration window stated

100%

Repository: secondsky/claude-skills
Commit: 90d6bd7

Evaluated: 30 days ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

E-Commerce API Upgrade: Adding a New Version Retiring a Legacy Payment API Version Evolving a SaaS User Profile API to a New Response Format

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.