Menu

Individual skill

bindry-sync

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.

plugins/bindryai/Plugins/skills/bindry-sync/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,531
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

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.

1. Determine the source from what the user actually said, in order:
   - A Binder id (GUID) or a full export URL they gave you — sync live from the Bindry API.
   - A file path they gave you — compile from that local export file.
   - Neither given: check for `./bindry.config.json` in the current project (written by a previous sync) and
     reuse the Binder id it remembers.
   - None of those apply — ask the user for a Binder id (from Bindry → Binder → Export → target "codex") or a
     saved export file path, then stop.
2. For a live sync, also need `--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