hashgraph-online/awesome-codex-plugins / plugins/bindryai/Plugins/skills/bindry-check
bindry-check
UnverifiedReport which compiled Bindry skills are stale, without changing anything. Use when the user asks to check for drift, staleness, or whether their Bindry skills are up to date.
Check whether the skills already compiled by the bindry-sync skill in this project have fallen behind the
Bindry Binder they came from. This is read-only — it never edits, deletes, or re-syncs a skill, only reports.
Invoke explicitly with $bindry-check, or let it trigger automatically when the user asks about drift/staleness.
- This needs
bindry.config.jsonin the project root (written by a previous sync) to know which Binder, API base to check against. If it's missing, tell the user to use thebindry-syncskill at least once first, then stop. - For a private Binder, also need
--token <api-key>(generated from the workspace's team page in Bindry, not Account settings) or theBINDRY_API_TOKENenvironment variable — same requirement asbindry-sync. - Locate this plugin's own installed root first (e.g. list installed Codex plugins and find the path for
bindry@<marketplace>), then run:node <resolved-plugin-root>/scripts/check-drift.mjs [--dir .agents/skills] [--api-base <url>] [--token <api-key>]If you can't locatescripts/check-drift.mjsunder this plugin's installed root, stop and say so plainly rather than guessing a path. - Report exactly what it printed: which skills are up to date, which are stale (and at what version each side
is), which are live (compiled with
--mode live— always current by design, calls the MCP server directly, never goes stale), and which it couldn't check (no pin or live comment, e.g. a hand-authored skill, or a Skill no longer in the Binder). If it failed with an authentication error, say so plainly rather than retry or guess. - If this project is pinned to a Binder version, the report ends with one of two lines, and they mean different things. "pinned to X, which is the newest published version" means there is nothing to do. "pinned to X; the Binder has since published Y" is not staleness — the project is deliberately not following the Binder. Relay it as information, and do not suggest re-syncing unless the user says they want to move off the pin.
- If anything is stale, tell the user to use the
bindry-syncskill to update it — this skill never does that for them. Live skills never need this — don't suggest re-syncing them just because they showed up in the report.
Note on "how far behind": the API doesn't expose full version history for a Skill today, only its current pinned version, so the report names the two version strings on each side (e.g. "compiled at 1.0.0, Binder now pins 2.0.0") rather than a version count. Don't invent a count if asked — say this isn't available yet.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |