versioning-strategy-helper

Versioning Strategy Helper - Auto-activating skill for API Development. Triggers on: versioning strategy helper, versioning strategy helper Part of the API Development skill category.

1.00x

Quality

Does it follow best practices?

Impact

98%

1.00x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./planned-skills/generated/15-api-development/versioning-strategy-helper/SKILL.md

Evaluation results

95%

-1%

REST API Version Rollout for a Payments Platform

REST API URL path versioning

Criteria

Without context

With context

URL path versioning

100%

Separate route files

100%

Versioned router mounting

100%

v2 includes idempotency_key

100%

v1 deprecation notice

100%

Backward compatibility maintained

100%

Retirement timeline communicated

100%

Strategy rationale documented

100%

Trade-offs addressed

100%

Production-ready error handling

100%

Step-by-step migration guidance

42%

28%

Without context: $0.4314 · 1m 49s · 21 turns · 22 in / 6,704 out tokens

With context: $0.4691 · 1m 52s · 27 turns · 27 in / 6,127 out tokens

100%

OpenAPI Specification Update for a Breaking API Change

OpenAPI specification versioning

Criteria

Without context

With context

Semantic version bump is major

100%

OpenAPI 3.x format

100%

Structured address schema

100%

Deprecated field marked

100%

Version in info.description or operation description

100%

Response example provided

100%

Major bump rationale in migration notes

100%

Client migration steps

100%

Transition strategy included

100%

Valid YAML structure

100%

Path parameter defined

100%

Without context: $0.2563 · 1m 10s · 15 turns · 15 in / 4,217 out tokens

With context: $0.4786 · 2m 1s · 26 turns · 287 in / 6,666 out tokens

100%

GraphQL Schema Evolution Without Breaking Clients

GraphQL schema evolution strategy

Criteria

Without context

With context

ShipmentStatus enum defined

100%

New shipmentStatus field

100%

Old status field deprecated

100%

Deprecation reason provided

100%

estimatedDelivery field added

100%

Query type present

100%

Step-by-step migration path

100%

GraphQL deprecation mechanism explained

100%

Migration window recommended

100%

Enum vs string trade-offs

100%

Valid SDL syntax

100%

Without context: $0.3459 · 1m 32s · 19 turns · 20 in / 4,867 out tokens

With context: $0.4367 · 1m 44s · 26 turns · 285 in / 5,544 out tokens

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 0c08951

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

Table of Contents

REST API Version Rollout for a Payments Platform OpenAPI Specification Update for a Breaking API Change GraphQL Schema Evolution Without Breaking Clients

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.