fp-cloud-cli

Inspect agent telemetry and operate a FailproofAI Cloud deployment via the fp CLI.

1.7k|417|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/FailproofAI/failproofai --skill fp-cloud-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fp-cloud-cli
Source: https://github.com/FailproofAI/failproofai/tree/main/fp-cloud-cli/skill
Command: npx skills add https://github.com/FailproofAI/failproofai --skill fp-cloud-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams running production AI agents lack a quick way to answer "how are my agents doing?" — checking errors, sessions, eval scores, and usage — and to operate their agent-observability deployment (issues, audits, API keys, users, policies) without opening a dashboard.

Core Features & Use Cases

  • Agent observability: Query events, sessions, errors, eval scores, and org usage with JSON output, filters, and aggregates to diagnose failures and quality regressions.
  • Deployment operations: Triage issues and audit findings, manage API keys, users, settings, and alerts, and run saved or ad-hoc ClickHouse SQL queries.
  • Enforcement management: Publish, test, and deploy policies to machine fleets and review guardrail activity (session-only commands).
  • Use Case: Ask "is anything broken today?" and the skill runs fp --json errors --since 24h --aggregate, drills into failing sessions, and reports the answer in prose.

Quick Start

Ask the assistant to check whether any of your production agents errored in the last 24 hours using the fp CLI.

Frequently Asked Questions about fp-cloud-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my production AI agents are failing?

Run fp --json errors --since 24h --aggregate for window totals, then fp --json errors --since 24h --all --limit 1000 to break failures down by session and error type. Use fp --json sessions --status error to list failed runs.

How do I investigate what happened inside a specific agent session?

Run fp --json events --session-id <id> --all --limit 1000 for the run's timeline. Add --full to include raw payloads, but always bound it to one session since the full feed is slow at scale.

Can I use the fp CLI with an API key in CI instead of logging in?

Yes, pass --api-key or set FP_API_KEY for non-interactive contexts. Note that login, orgs, agent, policies, fleet, and guardrails commands are session-only and exit with code 2 under a key, and you should pass --org explicitly with keys.

Why does fp events --all only return 50 rows?

The --limit flag defaults to 50 and --all paginates only up to that limit. Pass a high explicit cap like --all --limit 1000 for a full sweep, or use --aggregate for whole-window totals.

How do I run an audit and triage its findings from the CLI?

Run fp audits run <name> to queue a run, poll fp audits runs <name> until it succeeds, then list findings with fp audits findings --audit <name>. Triage with audits ack, mute, dismiss, or resolve, which stay in sync with the linked issue.

When should I not use the fp-cloud-cli skill?

Do not use it for writing evaluator scoring logic, adding SDK instrumentation to your app, debugging the collector daemon, or unrelated dev work like CI failures. It only covers operating and observing a FailproofAI Cloud deployment.