cloudflare-governance

Route broad Cloudflare prompts to the appropriate specialist sub-skill.

Updated Mar 24, 2026

Search Tags:#routing #governance #cloudflare #dns #zerotrust #edge-security

Ready to run

npx skills add https://github.com/pingqLIN/UniText --skill cloudflare-governance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cloudflare-governance
Source: https://github.com/pingqLIN/UniText/tree/main/runtime/skills/cloudflare-governance
Command: npx skills add https://github.com/pingqLIN/UniText --skill cloudflare-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Centralizes broad Cloudflare prompts and routes them to the most appropriate specialist, reducing misrouting and surfacing governance controls for validation and audit.

Core Features & Use Cases

Default entrypoint for broad Cloudflare questions when no narrower specialist is named.
Routes to focused sub-skills such as cloudflare-zerotrust-device, cloudflare-tunnel-dns, cloudflare-edge-security, cloudflare-access-mcp, and cloudflare-runtime-sync.
Provides a governance-first discovery layer with references, checklists, and scripts to support safe handoffs.

Quick Start

Simply ask for broad Cloudflare governance and routing and this skill will determine the right specialist and surface the appropriate actions.

Frequently Asked Questions about cloudflare-governance

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

FAQPage Schema

How do I route broad Cloudflare governance questions to the right specialist?▼

Cloudflare governance routing identifies whether a prompt is broad or narrow and directs it to a primary specialist. It evaluates available credentials to surface the correct sub-skill with a safe handoff.

What is the default entrypoint for broad Cloudflare edge-security and DNS prompts?▼

The default entrypoint for broad Cloudflare prompts centralizes routing to focused sub-skills like cloudflare-tunnel-dns and cloudflare-edge-security, reducing misrouting and surfacing governance controls for validation.

How does Cloudflare ZeroTrust governance handle credential evaluation for sub-skills?▼

Cloudflare ZeroTrust governance evaluates available credentials to surface the correct sub-skill, ensuring a safe handoff. It provides a governance summary and keeps local runtime context synchronized during the process.

Can I use this routing layer for Cloudflare runtime sync and access management?▼

Yes, you can use this routing layer for Cloudflare runtime sync and access management. It routes prompts to focused sub-skills such as cloudflare-access-mcp and cloudflare-runtime-sync while providing checklists for safe handoffs.

Do I need to specify a narrow specialist for Cloudflare edge-security and DNS tasks?▼

No, you do not need to specify a narrow specialist. The governance layer acts as the default entrypoint for broad Cloudflare questions, automatically determining the right specialist and surfacing appropriate actions.

What are the limitations of using a default routing layer for Cloudflare governance?▼

The default routing layer for Cloudflare governance is limited to identifying broad or narrow prompts and routing them to available sub-skills. It requires available credentials to evaluate and surface the correct specialist safely.