Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →octanejs/update-bindings
Audit one, several, or all existing Octane bindings; implement selected maintenance findings or remove redundant copied files with evidence matched to source ownership.
Passed 17 of 21 test cases with the skill, and 6 of 21 without it.
and 15 more in the full report
11 fixed6 passed either way4 still failing0 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to revalidate findings FIND-201, FIND-202, and FIND-203 against the baseline report /tmp/report.json. How do I pass all three finding IDs into the revalidation script command?
| Checked | Without skill | With skill |
|---|---|---|
| Executes node scripts/bindings-audit.mjs revalidate with --input /tmp/report.json | Missed | Passed |
| Repeats the --finding CLI argument for each individual selected finding ID | Missed | Passed |
The instructions your model reads when the skill loads.
Prefer direct upstream imports for demonstrated framework-neutral APIs. Octane should own the hooks, adapters, and components required for integration. A missing Octane convenience subpath alone is not a functional gap.
Preserve the user's scope and existing authorization. Skill creation or workflow evaluation does not authorize changes to real bindings. Do not restart a paused campaign or reopen a closed PR merely because its files appear in an audit.
Read AGENTS.md, the selected binding's public exports and status, and
docs/differences-from-react.md for relevant behavior. Use the shared inventory
through the audit CLI; do not maintain a separate binding list. Read
audit-evidence.md for report assessments and
baseline comparisons before relying on a report.
Run the audit script directly so package-manager auto-install cannot run lifecycle scripts during an audit. Required tooling dependencies must already be available; resolve missing setup separately before auditing.
Choose a report path outside every Git source tree, including worktrees and ignored directories. For example, use an external temporary directory:
node scripts/bindings-audit.mjs audit --binding <name> --output <external-report.json>
node scripts/bindings-audit.mjs audit --binding <name> --binding <other-name> --output <external-report.json>
node scripts/bindings-audit.mjs audit --all --output <external-report.json>
test cases passed, vs 6 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.