Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →octanejs/octane-react-library-port
Complete a verified local @octanejs binding for React libraries from npm names or npm/GitHub links/lists.
Passed 17 of 21 test cases with the skill, and 6 of 21 without it.
and 10 more in the full report
13 fixed7 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
Which skill must be loaded prior to editing or creating `.tsrx` component files during port implementation?
| Checked | Without skill | With skill |
|---|---|---|
| Loads authoring-tsrx before editing .tsrx files. | Missed | Passed |
The instructions your model reads when the skill loads.
For existing-binding audits, dependency/metadata maintenance, convenience imports, lifecycle fixes, or reduction, load update-bindings first. Continue here only for actual copied or rewritten React implementation. Demonstrated framework-neutral APIs should be imported from upstream; a missing Octane convenience export alone does not establish a functional gap or justify an upstream snapshot tree.
The primary deliverable is completed binding code, tests, provenance, and verified evidence in the local worktree. Preflight, graph, manifest, terminal, and progress reports are internal safety gates, never the outcome or a substitute for implementation.
The invocation itself authorizes the complete safe local workflow, including
local writes, tests, dependency install/repair, and generation within the user's
requested implementation scope. Do not ask the user to advance stages and do not
end on a progress report. Preserve shipping authorization already given; otherwise
deliver local readiness. Load create-a-pr before its branch/commit/PR triggers.
A React implementation port covers one pinned upstream release, not a convenient subset. Account for every published export, runtime test, and type test with executable evidence or a precise disposition. In mixed packages, validated imported surfaces use dependency evidence while the owned React implementation retains its full provenance and parity obligations. Finish only when every requested branch is:
verified: its complete local binding passed the machine gate;satisfied: a verified existing capability fully covers it; orhard-blocked: immutable evidence proves a terminal policy, identity,
collision, version, or concrete feasibility stop and names the repair.Never return actionable, pending-intake, ready, implementing, failed
validation, or unrun validation as final. pending-intake, type/test failures,
undiscovered tests, missing Vitest projects, generated drift, lockfile churn, and
incomplete evidence are work queues. Diagnose, repair, rerun, and continue every
independent branch. Ask only for a genuine product/version choice or new
test cases passed, vs 6 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.