Atrib Log - Printing Press CLI

Prerequisites: Install the CLI

This skill drives the atrib-log-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

1. Install via the Printing Press installer:

   npx -y @mvanhorn/printing-press install atrib-log --cli-only

2. Verify: atrib-log-pp-cli --version
3. Ensure $GOPATH/bin (or $HOME/go/bin) is on $PATH.

If the npx install fails before this CLI has a public-library category, install Node or use the category-specific Go fallback after publish.

If --version reports "command not found" after install, the install step did not put the binary on $PATH. Do not proceed with skill commands until verification succeeds.

atrib transparency log - Sigsum-style append-only Merkle log of signed
agent action records. Each entry is a cryptographically signed record
of an LLM agent action (tool call, transaction, observation, annotation,
revision, or directory anchor).

Command Reference

by-context - Manage by context

• atrib-log-pp-cli by-context <hex> - All entries in a context (session)

by-creator - Manage by creator

• atrib-log-pp-cli by-creator <key> - All entries by signer (creator key)

checkpoint - Manage checkpoint

• atrib-log-pp-cli checkpoint - Returns the current signed checkpoint (tree size + root hash + log signature). Use this to anchor your local view of...

entries - Manage entries

• atrib-log-pp-cli entries - Write path. Submit a signed record for inclusion in the log. Returns an inclusion-proof bundle on success.

feed-json - Manage JSON Feed

• atrib-log-pp-cli feed-json - JSON Feed 1.1 companion for newest-first decoded log entries.

log-pubkey - Manage C2SP log public key

• atrib-log-pp-cli log-pubkey - Get the log public key in signed-note vkey format.

lookup - Manage lookup

• atrib-log-pp-cli lookup <hex> - Lookup entry by record hash

proof - Manage proof recovery

• atrib-log-pp-cli proof <hex> - Recover an inclusion-proof bundle for a record already in the log.

pubkey - Manage pubkey

• atrib-log-pp-cli pubkey - Get verification public key

recent - Manage recent

• atrib-log-pp-cli recent - Most recent entries

stats - Manage stats

• atrib-log-pp-cli stats - Tree statistics

stream - Manage SSE stream

• atrib-log-pp-cli stream - Stream new decoded log entries as raw Server-Sent Events.

tile - Manage tile

• atrib-log-pp-cli tile get - Sigsum-style Merkle tile at level L, position N
• atrib-log-pp-cli tile get-entries - Get entries within a tile (leaf-level)

Finding the right command

When you know what you want to do but not which command does it, ask the CLI directly:

atrib-log-pp-cli which "<capability in your own words>"

which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match - fall back to --help or use a narrower query.

Auth Setup

No authentication required.

Run atrib-log-pp-cli doctor to verify setup.

Agent Mode

Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.

• Pipeable - JSON on stdout, errors on stderr

• Filterable - --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:

  atrib-log-pp-cli by-context mock-value --agent --select id,name,status

• Previewable - --dry-run shows the request without sending

• Offline-friendly - sync/search commands can use the local SQLite store when available

• Non-interactive - never prompts, every input is a flag

• Explicit retries - use --idempotent only when an already-existing create should count as success

Response envelope

Commands that read from the local store or the API wrap output in a provenance envelope:

{
  "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
  "results": <data>
}

Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal AND no machine-format flag (--json, --csv, --compact, --quiet, --plain, --select) is set - piped/agent consumers and explicit-format runs get pure JSON on stdout.

Agent Feedback

When you (or the agent) notice something off about this CLI, record it:

atrib-log-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
atrib-log-pp-cli feedback --stdin < notes.txt
atrib-log-pp-cli feedback list --json --limit 10

Entries are stored locally at ~/.atrib-log-pp-cli/feedback.jsonl. They are never POSTed unless ATRIB_LOG_FEEDBACK_ENDPOINT is set AND either --send is passed or ATRIB_LOG_FEEDBACK_AUTO_SEND=true. Default behavior is local-only.

Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.

Output Delivery

Every command accepts --deliver <sink>. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:

Sink	Effect
stdout	Default; write to stdout only
file:<path>	Atomically write output to <path> (tmp + rename)
webhook:<url>	POST the output body to the URL (application/json or application/x-ndjson when --compact)

Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.

Named Profiles

A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.

atrib-log-pp-cli profile save briefing --json
atrib-log-pp-cli --profile briefing by-context mock-value
atrib-log-pp-cli profile list --json
atrib-log-pp-cli profile show briefing
atrib-log-pp-cli profile delete briefing --yes

Explicit flags always win over profile values; profile values win over defaults. agent-context lists all available profiles under available_profiles so introspecting agents discover them at runtime.

Exit Codes

Code	Meaning
0	Success
2	Usage error (wrong arguments)
3	Resource not found
5	API error (upstream issue)
7	Rate limited (wait and retry)
10	Config error

Argument Parsing

Parse $ARGUMENTS:

1. Empty, help, or --help → show atrib-log-pp-cli --help output
2. Starts with install → ends with mcp → MCP installation; otherwise → see Prerequisites above
3. Anything else → Direct Use (execute as CLI command with --agent)

MCP Server Installation

Install the MCP binary from this CLI's published public-library entry or pre-built release, then register it:

claude mcp add atrib-log-pp-mcp -- atrib-log-pp-mcp

Verify: claude mcp list

Direct Use

1. Check if installed: which atrib-log-pp-cli
   If not found, offer to install (see Prerequisites at the top of this skill).
2. Match the user query to the best command from the Unique Capabilities and Command Reference above.
3. Execute with the --agent flag:

   atrib-log-pp-cli <command> [subcommand] [args] --agent

4. If ambiguous, drill into subcommand help: atrib-log-pp-cli <command> --help.