from skills_collection22
Guidance and templates for designing API versioning strategies, managing breaking changes, and running deprecation/migration workflows.
Provides practical guidance, templates and checklists for API versioning strategy and backward-compatibility management. Includes recommended patterns (URL path, header, query), SemVer guidance, deprecation/sunset processes, and migration patterns with examples and header conventions.
When you need to choose or document an API versioning approach, prepare for breaking changes, publish migration guides, or run a deprecation plan for existing endpoints. Useful during API design, major releases, and when coordinating client migrations.
{ }
This skill is a knowledge-rich reference suitable for developer-facing assistant workflows (code-writing and API design helpers).
A knowledge-only skill providing guidance on API versioning strategies, breaking change management, deprecation processes, and migration workflows — written entirely in Japanese. The SKILL.md is comprehensive and well-structured as reference material, but lacks automation scripts despite frontmatter referencing check-breaking-changes.js and generate-migration-guide.sh. No executable code, just static reference content with tables and checklists.
Pure reference/knowledge skill with no scripts or automation. Security is nearly perfect since there's nothing executable. Code quality is mediocre — the content is thorough but the skill is mislabeled (frontmatter name is a filepath, not a skill name), dead script references undermine trust, and Japanese-only limits accessibility. Architecture is weak: no scripts/ directory, no actual separation of concerns despite claiming resources/ and templates/ subdirectories, and the frontmatter metadata is a filepath rather than a proper skill name. Usefulness is limited: API versioning guidance is valuable but this is just static reference content an LLM could generate on demand, and the language barrier and broken references reduce practical value.
