probes

Diagnose Cloudflare service health and cost risks with MCP-based probes producing provenance-tagged results and recommendations.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/littlebearapps/cloudflare-engineer --skill probes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: probes
Source: https://github.com/littlebearapps/cloudflare-engineer/tree/main/skills/probes
Command: npx skills add https://github.com/littlebearapps/cloudflare-engineer --skill probes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cloudflare service auditing and live validation can be time-consuming and error-prone.

Probes provide pre-built, battle-tested query and MCP call patterns to validate D1 schemas, observability signals, AI Gateway costs, queue health, and other Cloudflare resources, enabling rapid diagnostics and cost-aware optimization.

Core Features & Use Cases

  • Pre-built diagnostic probes for MCP availability, D1 database queries, Observability metrics, AI Gateway costs, and Queue health.
  • Guidance for live validation vs static analysis to identify gaps between theory and production data.
  • Use cases include validating explain query plans, monitoring error rates, and optimizing resource usage across Cloudflare services.

Quick Start

Run the probes against your Cloudflare environment to begin validating live production data.

Frequently Asked Questions about probes

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

FAQPage Schema
How do I run live validation diagnostics on Cloudflare D1 databases?

Live validation diagnostics for Cloudflare D1 databases are performed by applying pre-built query probes to execute explain query plans, validate schemas, and compare live production data against static analysis.

What is the best way to audit Cloudflare AI Gateway costs and queue health?

Auditing Cloudflare AI Gateway costs and queue health is done using pre-built diagnostic probes that analyze observability metrics, detect cost risks, and return provenance-tagged results with optimization recommendations.

Do I need MCP access to validate Cloudflare observability metrics?

Yes, MCP access is required to validate Cloudflare observability metrics. The probes orchestrate MCP tool calls to gather live production data, ensuring accurate health diagnostics and gap analysis against static configurations.

Can I compare static analysis with live production data for Cloudflare services?

Comparing static analysis with live production data is fully supported. The probes identify gaps between theoretical configurations and actual Cloudflare runtime data by cross-referencing prepared query patterns with live MCP tool outputs.

Why does my Cloudflare D1 schema validation show errors in production?

Cloudflare D1 schema validation errors are identified by probing live databases to validate query plans and schemas. The diagnostic results isolate discrepancies between static schema definitions and live production data states.

How to monitor Cloudflare service error rates using diagnostic probes?

Monitoring Cloudflare service error rates is achieved by running observability probes that analyze live metrics. These probes detect production anomalies, assess cost risks, and generate provenance-tagged diagnostic reports.