flowplane-ops

Boot, diagnose, and monitor a Flowplane API gateway in dev or prod mode.

1|Updated Jun 11, 2026
One-click install
npx skills add https://github.com/rajeevramani/flowplane --skill flowplane-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flowplane-ops
Source: https://github.com/rajeevramani/flowplane/tree/main/.claude/skills/flowplane-ops
Command: npx skills add https://github.com/rajeevramani/flowplane --skill flowplane-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Boot, diagnose, and monitor a Flowplane API gateway across development and production environments, enabling fast identification of boot issues, routing problems, and health concerns.

Core Features & Use Cases

  • Boot and initialize Flowplane in dev or prod modes (including MCP connectivity and seeding steps)
  • Run read-only diagnostics (trace requests, topology, config validation, audit queries, and xDS status)
  • Follow structured troubleshooting playbooks for 404s, 503s, auth issues, and cascading xDS failures
  • Inspect resources (clusters, listeners, route configs, virtual hosts, filters) to localize problems
  • Reference full architecture and boot recipes from the provided references to reproduce setups in new environments
  • Use with the flowplane-api skill to apply fixes after diagnosis

Quick Start

Boot Flowplane in development mode with flowplane init --with-envoy --with-httpbin, then verify health with flowplane status and auth mode with curl http://localhost:8080/api/v1/auth/mode.

Frequently Asked Questions about flowplane-ops

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

FAQPage Schema
How do I troubleshoot Flowplane API gateway routing and xDS delivery failures?

To troubleshoot Flowplane gateway routing and xDS failures, use structured playbooks to inspect clusters, listeners, route configs, and virtual hosts. This read-only diagnostics approach localizes 404s, 503s, and cascading xDS delivery issues without modifying gateway state.

What is the best way to run health checks and trace requests on a Flowplane gateway?

The best way to run health checks and trace requests on a Flowplane gateway is by executing read-only diagnostics. You can verify topology, validate configurations, query audit trails, and monitor xDS status to identify boot issues and health concerns.

How do I boot and initialize Flowplane in development mode with Envoy?

Boot Flowplane in development mode by running flowplane init --with-envoy --with-httpbin. Then verify gateway health with flowplane status and check the authentication mode using curl http://localhost:8080/api/v1/auth/mode.

Can I apply configuration fixes directly through Flowplane gateway operations?

No, Flowplane gateway operations enforce read-only inspection for diagnostics and troubleshooting. After identifying routing, xDS, or authentication issues, you must guide remediation through the separate flowplane-api skill to apply actual fixes.

Why does my Flowplane API gateway return 404 or 503 errors after boot?

Flowplane gateways return 404 or 503 errors due to routing misconfigurations, xDS delivery failures, or authentication issues. Inspect route configs, virtual hosts, and filters using the structured troubleshooting playbooks to isolate the specific boot or routing defect.