new-api-version
new-api-version is a Migrations, upgrades & porting skill for AI agents, published by jellyrock in the jellyrock repository on GitHub. Skillspace rates new-api-version D (57/100) and it passed the safety scan; the rating is based on static analysis only.
Guided workflow for standing up a NEW Jellyfin apiVersion tier (V3, V4, …) in JellyRock when an upstream release restructures the API enough to need a new `if m.getApiVersion() >= N` dispatch level. Wraps the "Adding Support for New Server Versions" recipe in docs/dev/jellyfin-server-versioning.md and walks every surface that must move together — the boundary map (YAML), its BrightScript twin `resolveApiVersion()`, the `sdkVN.bs` endpoints, the dispatch branches, the device profile, the manifest tier-clamp, and the validators — stopping at each step so the tier split can't land half-built. Use when proactive RC/master triage (via `/server-upgrade <rc-or-unstable>`) shows a breaking API shift that a per-method `>= N` branch must cover. NOT for routine endpoint additions inside an existing tier (those use the existing `>= 2` shape directly).
- Grade
- D
- Quality
- 57 / 100
- Safety
- Passed
- GitHub stars
- 35
Unproven: rated by static analysis only, not yet compared head-to-head.
This rating describes the version of the repository we crawled; it may have changed since, so go by its current files.
Our review
- Architecture
- 87 / 100
- Maturity
- Basic: a single SKILL.md
- Security scan
- Low-risk patterns
- License
- GPL-2.0
- Adoption
- Adopted by 0 other repositories, in 0 collections
What the scanner flagged
- over-broad allowed-tools ('*')
Not checked yet
- Not judged on the rubric yet (not a contender in its category)
- No blind task eval yet
- Scope (portable / vendor / repo-internal) not assessed; only the top of each category is read for scope
- Sibling files (scripts, references) not fetched; security scan covers SKILL.md only
Skillspace indexes and rates this skill; it does not host or endorse it. Run third-party skills at your own risk.