Compile skills from a Bindry Binder into a project’s Codex skills folder. Choose a pinned snapshot or live mode, and use a Binder ID, export URL, or saved export file as the source.
Compile a bound Bindry Binder into Codex skills for this project, so its Skills load on demand instead of sitting in every prompt. Use when the user asks to sync, install, or update Bindry Binder skills for this project.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Compile a Bindry Binder into Codex skills so its Skills load on demand instead of sitting in every prompt.
Invoke explicitly with $bindry-sync, or let it trigger automatically when the user asks to sync/update Bindry
skills.
./bindry.config.json in the current project (written by a previous sync) and
reuse the Binder id it remembers.--api-base <url> (the Bindry API's base URL — ask the user if not obvious from
context) and, for a private Binder, --token <api-key> (generated from the workspace's team page in Bindry,
not Account settings). A published Library Binder (referenced by slug or GUID) needs no token at all — it
resolves through the public Library's anonymous export route. Only your own private Binders require one.--mode pinned (a static snapshot). If the user wants this Binder to always stay current instead
— --mode live — first confirm the Bindry MCP server is connected (check the configured MCP servers for one
named bindry). If it isn't connected, tell the user to use the bindry-connect skill first and stop;
compiling live skills with no live connection would produce skills that always fail when used. --mode live
also only works from a live Binder id/URL, not a local export file — its Skills need real GUID ids, which a
hand-written or example export file won't have.--version <v>. It is remembered in
bindry.config.json, so later syncs stay on that version until --version latest removes the pin. A
version pin only applies to a Library Binder (your own workspace Binder always compiles from its current
composition), and an unknown version fails with a message naming the versions that do exist rather than
quietly serving the latest.bindry@<marketplace>), then run:
node <resolved-plugin-root>/scripts/compile-binder.mjs [<binder-id-or-file>] --out .agents/skills [--api-base <url>] [--token <api-key>] [--mode pinned|live] [--version <v>]
If you can't locate scripts/compile-binder.mjs under this plugin's installed root, stop and say so plainly
rather than guessing a path.bindry.config.json, mention that future syncs in this project can omit the Binder id (and remember the mode
too).bindry-check skill can diff against it. A live skill
never goes stale — it calls the Bindry MCP server for current content every time it's used — so there's
nothing to re-sync for it, only re-run if the Binder's Skill list itself changed (added/removed Skills).assets/ folder alongside SKILL.md — in both pinned and live mode, since the live MCP tools don't
serve binary files. If the script printed a warning that it skipped an asset, mention that plainly too —
that skill still compiled, just without the file, and needs an --api-base/network fix before it will
download.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Plan worthwhile local tasks by checking dependencies, effects, resources, and platform boundaries, then execute the exact approved plan. It can use safe parallel work or suitable Apple-silicon backends when the project exposes them.
Record deferred engineering decisions and temporary workarounds in a debt registry, with context such as effort, ongoing cost, affected area, and payoff trigger. Entries receive short labels so they can be reviewed or dropped later.
Generate or compare AI agent code for LangChain, EINO, AutoGen, AgentScope, and CrewAI using framework-specific templates, API mappings, conventions, and project structures. Reference files include verification dates to help identify potentially outdated guidance.
Investigate a reproducible bug, test failure, or unexpected page behavior, then make a narrowly scoped fix. The workflow calls for a regression test before changing code, verifies the fix, and reports remaining risks and evidence while avoiding unrelated refactoring or feature work.
Build an AI agent project through six collaborative stages, from requirements and architecture to tools, prompts, code generation, and verification. Start framework-independent, then generate a runnable project for frameworks such as LangChain, EINO, AutoGen, AgentScope, or CrewAI.
Audit a project or learning workflow for scope drift, conflicting plans, inconsistent names, and code quality concerns. The skill reads project files and code, then reports evidence, severity, and suggested next steps without changing files.