Bindry
Sign in
Back to home

Plug-in

Claude Code

Compiles a bound Stack into Claude Code skills, so instructions load only when a task actually matches them — not on every single turn.

View source

Built and verified end-to-end

Tested against the real Claude Code CLI: both install commands complete, claude plugin list shows bindry@bindry-plugins enabled, and pinned and live sync modes both work.

Why skills, not a CLAUDE.md dump

Claude Code loads a skill on demand based on its description, rather than keeping it in context on every turn. That's the same "context saved" idea behind Bindry itself — so this plugin compiles each Binding into its own skill instead of concatenating a Stack into one always-on file. A tenant-isolation Binding only enters context when Claude Code is actually touching storage code.

How it works

  1. 1

    Install the plugin

    Run the two install commands below. Claude Code gets three new commands: /bindry-sync, /bindry-connect, and /bindry-check.

  2. 2

    Load a Stack with /bindry-sync

    Give it a Stack from the Library by name (like git-flow-command-center), or your own Stack's id from its Export page. Each Binding becomes its own skill under .claude/skills/.

  3. 3

    Keep it current

    Run /bindry-connect once, then /bindry-sync <stack> --mode live, and the skills always read the latest version. Prefer a fixed snapshot? Re-run /bindry-sync when the Stack changes — /bindry-check shows what is out of date.

Install

claude plugin marketplace add bindryai/Plugins
claude plugin install bindry@bindry-plugins

The marketplace manifest lives at the repo root and lists this plugin at ./claude-code — so marketplace add points at the whole repo, not the subdirectory. Verified end-to-end on Claude Code v2.1.238: both commands complete and claude plugin list shows bindry@bindry-plugins enabled. To test a local checkout instead, pass the repo root on disk in place of the repo name.

What a compiled skill looks like

One Binding from the "Git Flow Command Center" Stack, compiled to .claude/skills/git-branch-and-pr-hygiene/SKILL.md:

SKILL.md
---
name: git-branch-and-pr-hygiene
description: Branch & PR Hygiene. Use when: Creating a branch; Opening or updating a pull request.
---

<!-- bindry:pin stack=git-flow-command-center binding=bnd_git_branch_pr_hygiene version=3.1.0 -->

Use feature/<ticket>-<slug> branch names. Keep commits scoped to one logical
change with an imperative summary line. PR descriptions must include a
one-line "why" and a manual test note.

Constraints:
- Do not squash commits that mix unrelated changes into one message.

Verify before finishing:
- Every PR description has a test plan section before merge.

Install a Stack you don't own — no API key needed

/bindry-sync git-flow-command-center resolves a published Stack straight from the public Library by name. A key is only needed for your own private Stacks.

Using your own private Stacks

New to API keys? Read the plain-language explainer first if "generate a key" doesn't already mean something to you.

  1. 1

    Generate a key on the workspace's Team page

    Not Account settings — a key is scoped to whichever workspace's Team page you make it from. Give it a name (e.g. "This laptop") and, optionally, an expiration date. There's no permission picker to fill in: the key already does everything you can do in that one workspace, nothing more.

  2. 2

    Put it in BINDRY_API_TOKEN

    Set it as an environment variable rather than pasting it into a command — both /bindry-sync and /bindry-connect read the same variable, and it's the only credential either one needs.

  3. 3

    One key per workspace

    A key never sees more than the single workspace it was created in. Working across more than one team? Make a separate key on each team's own Team page, rather than expecting one key to reach both.