Menu

Individual skill

bindry-check

Report 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.

plugins/bindryai/Plugins/skills/bindry-check/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,533
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

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.

1. This needs `bindry.config.json` in 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 the `bindry-sync` skill at least once first,
   then stop.
2. For a private Binder, also need `--token <api-key>` (generated from the workspace's team page in Bindry, not
   Account settings) or the `BINDRY_API_TOKEN` environment variable — same requirement as `bindry-sync`.
3. 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 locate `scripts/check-drift.mjs` under this plugin's installed root, stop and say so plainly
   rather than guessing a path.