Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →failproofai/fp-cloud-cli
The way to answer "how are my production AI agents doing?" and to run the team's agent-observability deployment — reach for it even on casual phrasing that names no tool.
Passed 13 of 18 test cases with the skill, and 7 of 18 without it.
and 13 more in the full report
10 fixed7 passed either way4 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to list recent session runs for our deployment using the command line client. Should I append the JSON format option at the end like `fp sessions --json` or does flag placement matter?
| Checked | Without skill | With skill |
|---|---|---|
| Places the global flag `--json` before the `sessions` subcommand. | Missed | Passed |
| States that placing global flags after subcommands causes a usage error. | Missed | Passed |
The instructions your model reads when the skill loads.
fp is a command-line client for a FailproofAI Cloud deployment. It authenticates
either as a signed-in user or with a scoped API key (§2), and every command
takes --json, so it's built to be driven by an agent.
Resolve this once, then reuse it for every call:
fp is on PATH (command -v fp) → use fp (it's
installed via pipx / uv tool / pip). This is the normal case.fp-cloud-cli/ directory containing the
fp_cli package → run it from there with uv run fp (a local dev
build). The first run after a code change prints Building…/Installed… on
stderr — that's uv, not CLI output; ignore it.pipx install fp-cloud-cli or uv tool install fp-cloud-cli) and stop. Don't try to
reach the dashboard another way.Don't go spelunking in the CLI source tree for flags — if you're unsure of one,
run fp <group> <cmd> --help. The source is not the documented contract
and reading it wastes effort.
Throughout this skill, fp means "whichever form you resolved."
Global options go BEFORE the command: fp --json events, never
fp events --json. Globals are --base-url, --org, --token,
--api-key, --json, --insecure/--secure. After the command they're a
usage error.
Two ways to authenticate, and they are not interchangeable:
| How you supply it | What it is | |
|---|---|---|
| Session | fp login (interactive; it emails a one-time code) | a signed-in user, carrying that person's org memberships and permissions |
| API key | --api-key <key>, or FP_API_KEY in the environment | a scoped credential, carrying exactly the permissions it was granted |
A key is what you want in CI or any other non-interactive context: no browser, no
test cases passed, vs 7 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.