Install any skill in seconds. Free to start, no credit card required.
Get Started Free →octanejs/react-library-port
Compatibility entry point for autonomously porting React libraries to Octane bindings.
Passed 20 of 22 test cases with the skill, and 3 of 22 without it.
and 20 more in the full report
17 fixed3 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are porting `timeline-engine` from GitHub release tag `v4.2.0` into a React package. What skill directive should be loaded and what details must be preserved?
| Checked | Without skill | With skill |
|---|---|---|
| Directs the port process to follow octane-react-library-port. | Missed | Passed |
| Preserves GitHub release tag v4.2.0. | Passed | Passed |
The instructions your model reads when the skill loads.
This is the stable legacy entry point for React-library binding work.
For existing-binding audits, maintenance, lifecycle fixes, dependency/metadata updates, convenience imports, or reduction, load and follow update-bindings. A missing convenience wrapper does not justify porting framework-neutral code available through a direct import.
For a new React-library port or actual copied/rewritten React implementation, load and follow octane-react-library-port. Preserve supplied library names, versions, and npm/GitHub inputs. Its implementation, verification, and terminal requirements apply to that port; routing alone does not complete an authorized implementation. Preserve the user's scope and any existing shipping authorization.
test cases passed, vs 3 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.