Use Checkfu with your coding agent

Print drift-checked integration recipes and install the Checkfu authoring skill.

The CLI ships two forms of coding-agent context. Recipes teach your agent to build customer-owned integration code from tested examples. Skills teach it the Checkfu agent-authoring workflow. Both version with the installed CLI, and neither grants an agent authority to operate Checkfu on its own.

The Checkfu CLI has no self-service public installation channel during private alpha. The commands below assume access through an explicitly authorized alpha arrangement. See CLI access in private alpha for the source-checkout and HTTP alternatives.

Print an integration recipe

List the embedded catalog:

checkfu add --list

Print one recipe to the terminal, or pipe it to your coding agent:

checkfu add tool-server
checkfu add slack | claude
checkfu add embed | claude

checkfu add writes nothing, fetches nothing, and never invokes an agent. Each recipe names the example files it draws on and quotes them verbatim. A repository gate keeps those quotes honest: it fails if a named source disappears, a quoted excerpt drifts, a required CLI command leaves --help, or a required SDK symbol leaves the built types.

The catalog covers serving Custom tools and embedding a Session view.

Install the authoring skill

Install the shipped checkfu-agent-authoring skill into a supported user-level layout. Pick the client you use:

checkfu skills install --client claude
checkfu skills install --client codex

Claude installs beneath $HOME/.claude/skills; Codex uses $CODEX_HOME/skills when configured and otherwise $HOME/.codex/skills. Use an explicit directory for another client:

checkfu skills install --client generic --dir ./agent-skills

An identical installation is a no-op. If any installed file is modified, missing, extra, or symlinked, the CLI refuses the whole skill directory and preserves it byte-for-byte. Review or move your local copy before installing a new version.

On POSIX systems the public skill directory is an atomic link to a hidden installer-owned sibling named .checkfu-agent-authoring.content-*; keep that sibling with the public link when backing up, moving, or excluding the install. Windows installations remain ordinary directories, including on supported network-backed homes and explicit directories.

If publication fails, the CLI prints the hidden staging path and retains it for inspection. This fail-safe avoids deleting a pathname another local process may have replaced; remove the retained directory only after verifying its contents.

The skill routes agents back to checkfu add --list and the machine-readable documentation index, so instructions can be loaded progressively.

After installation, follow Author an Agent project for the human-readable inspect, edit, compile, scenario, observation, and evidence loop. The public guide summarizes stable facts; the installed skill owns the detailed, version-matched repair workflow and closed observation format.

Recipe or AgentBlueprint?

The two surfaces solve different jobs and never substitute for each other:

Surface	What it contains	What it changes	Runtime authority
Integration recipe	Markdown instructions for customer-side adapters and UI	Nothing; your coding agent edits your application after you choose to run it	None
AgentBlueprint	Versioned declarative install intent for Checkfu resources	checkfu blueprint apply reconciles ordinary governed resources through the public API	The resulting resources; never the package or installation record

Use a recipe to build the Slack worker, tool server, or embedded frontend that stays in your stack. Use an AgentBlueprint to declare the governed Checkfu resources that adapter calls: the Agent, its Principal and installation, PermissionAssignments, ActionPolicies, Budgets, Automations, and memory.