Skip to content
Cabuya

Two lines, and your agent knows the protocol

The pack teaches any coding agent the Cabuya Protocol — schema, levels, exclusions, validator — and works with no network, because the specification travels inside it. You install it once and say one sentence.

1. Install the pack

Either line works; both are proven on a clean machine. The second vendors the pack into your repository, reviewable in a pull request.

shellscript
npx skills add Cabuya/cabuya-skill
# or, vendored into your repository:
git clone --depth 1 https://github.com/Cabuya/cabuya-skill .agents/skills/cabuya

2. Say the sentence

shellscript
/cabuya

That is the whole interface. In agents that intercept the slash, say it in words: “adopt Cabuya”.

What happens next

The agent reads your repository — it writes nothing yet — and tells you, in plain language, what implementing Cabuya means here: which files, which endpoints, roughly how much work, and the one decision that will be yours. Then it plans the adoption and runs it one task at a time, validating each.

It asks before it proposes

If your team already plans work with a spec-driven methodology, the agent hands it the whole context — ordered tasks, acceptance criteria, validation commands — and your workflow keeps planning. Yours outranks anything it would bring.

With DeepWorkPlan, the plan lands on disk as task files you can review in a pull request, each with its own validation, and it survives across sessions — the pack offers to install and onboard it.

Without it, the agent plans in its own plan mode over the same task list. The decisions survive either way; the task detail lives in the session. It is lighter, and the pack says so. Neither tool is required.

The one thing it will ask you

What may be published. The agent presents every column that could carry personal data and waits: that decision is yours by design, and there is no flag that skips it.

If your records describe people rather than places, the specification caps the app at L1 permanently — a fact about the data, not a verdict on the app.

Not ready? Ask it questions

The pack answers “what is Cabuya”, “why a protocol”, and “what would this take in our app” from the specification it carries, with citations — and previews the work without writing a file.

What it will not do

  • Claim a conformance level the validator did not measure — and it never uses the word “certified”.
  • Publish a contact value, anywhere, in any encoding. Contact reaches people through each record’s public page.
  • Open a pull request, or write any file, without asking first.
  • Send your data anywhere. It has no telemetry and calls no one home.