versioning-strategy-helper

Quick Review

This skill is extremely generic and underdeveloped. The description and capabilities sections are circular, repeatedly stating 'versioning strategy helper' without explaining what versioning strategies are covered (semantic versioning, URI versioning, header-based, etc.). There is no concrete task knowledge, code examples, decision trees, or actionable guidance. The structure is clear but empty of substance. While API versioning can be complex, this implementation provides no meaningful reduction in token cost over asking a CLI agent directly, as it contains no specific frameworks, patterns, or decision logic. To improve: add concrete versioning approaches (URL path, query param, header, content negotiation), migration strategies, breaking change detection, and practical examples for different API types.