fp-cloud-cli
SolidThe 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. Trigger when the user wants to: • inspect agent telemetry — did agents error/fail/go flaky; sessions, events, latency, token usage, slowest models; eval/quality scores and whether quality dropped; • operate the deployment — ack/assign/resolve/mute/dismiss issues (alerts, reports, and audit findings) with notes; run and triage audits; see who has access and change roles (e.g. read-only); create or scope API keys (e.g. a push-only CI key); change settings; run saved or ad-hoc ClickHouse queries. Served by the `fp` CLI against FailproofAI Cloud. NOT for writing or designing an evaluator service / scoring logic (that's `agenteye-evaluator`), adding SDK/instrumentation to your app (that's `failproofai-sdk`, imported as `failproofai_sdk`), debugging the collector/daemon, or unrelated dev work (why a build/CI run failed, rotating non-FailproofAI Cl
Install
Quality Score: 83/100
Skill Content
Details
- Author
- FailproofAI
- Repository
- FailproofAI/failproofai
- Created
- 5 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- NOASSERTION
Similar Skills
Semantically similar based on skill content — not just same category
failproofai-sdk
The way to make an AI agent report what it did to Failproof AI — planning what to record, writing the instrumentation, and proving the events land. Reach for it on vague phrasing too: "add observability to my agent", "why isn't my agent showing up?" Trigger when the user wants to: • plan an integration — which points in their agent loop to record, and what the platform must see before sessions, errors, and evals work at all; • write or fix instrumentation — add the `failproofai_sdk` Python SDK to an agent codebase, thread session/agent identity through it, emit tool, model, hook, or human events; • verify it — confirm events are being written, or debug an integration that looks correct and produces nothing. Served by the `failproofai_sdk` Python SDK, inside the user's own agent. NOT for reading telemetry that already landed or operating a deployment (that's `fp-cloud-cli`), or building the evaluator service that scores runs (that's `agenteye-evaluator`).
firebase-cli
Safety-first Firebase CLI (firebase-tools v15) skill for full project control — deploy, Hosting (sites/channels/rollback), Cloud Functions (+secrets), Firestore (databases/indexes/backups/delete), Realtime Database, Auth import/export, Remote Config, App Distribution, App Hosting, Extensions, Data Connect, Emulator Suite & MCP server. Classifies every command by risk tier via a deterministic classifier script and gates destructive/irreversible/cost-incurring ops behind AskUserQuestion confirmation; enforces the --non-interactive/--force contract so nothing hangs and nothing is auto-confirmed. Wrong-project preflight prevents deploying to prod by accident. Ships a 3-level self-test (static classifier battery, live read-only, guarded live-write w/ cleanup). Use when running, planning, or debugging any `firebase` command.
fal
Generate and edit media with fal.ai — images, video, speech, music, sound effects, lipsync/talking-head avatars, motion control, upscaling, 3D, and full multi-shot video pipelines. Use when the user asks to "generate an image", "make a video", "text to video", "image to video", "animate this photo", "AI voiceover", "text to speech", "clone a voice", "make music", "lipsync", "talking head", "UGC ad", "AI avatar", "upscale", "remove background", "outpaint", "reframe to vertical", "transcribe", "dub this", "image to 3D", or mentions fal, fal.ai, FAL_KEY, Veo, Kling, Seedance, Nano Banana, Seedream, Flux, ElevenLabs, MiniMax, Topaz, or a fal endpoint id. Also use for Higgsfield-style workflows built on fal instead.