Install any skill in seconds. Free to start, no credit card required.
Get Started Free →growthxai/output-migrate
Upgrade a project between versions of the Output framework.
Passed 3 of 12 test cases with the skill, and 4 of 12 without it.
2 fixed4 passed either way15 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/2/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have fetched the migration guide for `@outputai/core` v0.1.0 to v0.2.0 and identified three files that need updating. What must be done before applying edits?
| Checked | Without skill | With skill |
|---|---|---|
| The assistant prompts the user for confirmation before applying file edits. | Missed | Passed |
The instructions your model reads when the skill loads.
This skill migrates a project from one version of the Output framework to another.
You do not carry migration instructions in your own context. The docs site at https://docs.output.ai/migrations is the source of truth — fetch the right page and follow it.
Use the todo tool to track your progress.
@outputai/* packages to a newer versionMigration guides are hand-authored MDX pages linked from a single index:
https://docs.output.ai/migrationshttps://docs.output.ai/migrations/v{FROM_FULL}-to-v{TO_FULL} (e.g. v0.1.12-to-v0.2.0)The index lists every available guide with a title and a short description. A release only has a guide if it introduced breaking changes — most releases will not have one.
If the user is jumping multiple boundaries, fetch each applicable guide in order and apply them sequentially.
<process_flow>
If the user passed arguments when invoking this skill, parse them as positional values in this order (all optional):
from-version: The version the project is currently on. If blank, detect it in Step 2.to-version: The target version. If blank, resolve it in Step 1.additional-instructions: Free-form guidance from the user (e.g. "skip the http changes, we don't use that package").test cases passed, vs 4 / 12 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.