Versioning Strategy Helper - Auto-activating skill for API Development. Triggers on: versioning strategy helper, versioning strategy helper Part of the API Development skill category.
34
0%
Does it follow best practices?
Impact
98%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/15-api-development/versioning-strategy-helper/SKILL.mdREST API URL path versioning
URL path versioning
100%
100%
Separate route files
100%
100%
Versioned router mounting
100%
100%
v2 includes idempotency_key
100%
100%
v1 deprecation notice
100%
100%
Backward compatibility maintained
100%
100%
Retirement timeline communicated
100%
100%
Strategy rationale documented
100%
100%
Trade-offs addressed
100%
100%
Production-ready error handling
100%
100%
Step-by-step migration guidance
42%
28%
OpenAPI specification versioning
Semantic version bump is major
100%
100%
OpenAPI 3.x format
100%
100%
Structured address schema
100%
100%
Deprecated field marked
100%
100%
Version in info.description or operation description
100%
100%
Response example provided
100%
100%
Major bump rationale in migration notes
100%
100%
Client migration steps
100%
100%
Transition strategy included
100%
100%
Valid YAML structure
100%
100%
Path parameter defined
100%
100%
GraphQL schema evolution strategy
ShipmentStatus enum defined
100%
100%
New shipmentStatus field
100%
100%
Old status field deprecated
100%
100%
Deprecation reason provided
100%
100%
estimatedDelivery field added
100%
100%
Query type present
100%
100%
Step-by-step migration path
100%
100%
GraphQL deprecation mechanism explained
100%
100%
Migration window recommended
100%
100%
Enum vs string trade-offs
100%
100%
Valid SDL syntax
100%
100%
c8a915c
Table of Contents
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.