The Cefense skill | Cefense docs

There are two. One onboards an agent that has never seen Cefense. The other is the day to day guide, installed into your repository so it is there in every future session.

The setup document

cefense.com/skill.mdbash

curl -fsSL https://cefense.com/skill.md

Written for an agent with no prior knowledge. It gets cf installed, gets the user signed in, connects the repository, and finishes by running cf skill install. Point an agent at the URL and it does the rest. See Agent quickstart.

The installed skill

Install it into the repositorybash

cf skill install
cf skill list
cf skill show claude

This is the larger document, and the one that matters day to day. It covers the vocabulary, the filters, the fix lifecycle, how to read a data flow, which organization a command acts on and what each role is allowed to do, every error code, and the rules around opening and merging pull requests. It ships with the CLI, so it is always in step with the version you have installed.

Where it is written

Each agent gets the document at the path it actually reads, in the format it actually expects. See Supported agents for the full list.

Keeping it current

Reinstalling replaces what is there. In a shared file like AGENTS.md it replaces only the marked section and leaves the rest of the file alone. Upgrade the CLI and run cf skill install again to pick up a newer skill.

Committing it

The files belong in a commit. That is what makes the behaviour consistent across the team rather than depending on who ran the install.

Teaching a coding agentEvery flag on `cf skill`, and what it writes where.Supported agentsThe full list, and wiring up one that is not on it.Schema and readinessWhat an agent can read about the CLI before it runs anything.

Have a correction or need help?

Email the docs team