connector-tunnel-management
Skill1 starsChanged 32 days agoApache-2.0View on GitHub
Create, expose, check, and retire an outbound-only connector tunnel that publishes an internal application or connects a private network to a cloud edge without opening inbound firewall ports — Cloudflare Tunnel (the cloudflared connector). Use when a tunnel needs to be created, a hostname or private network route attached to it, its health diagnosed, or the tunnel and its routes removed. Not for site-to-site IPsec or GRE tunnels (see vpn-tunnel-management). Assumes an authenticated Cloudflare API client with tunnel permissions is already available and that the operator can run the connector on a host inside the private network; this skill does not provision or authenticate that client.
In this repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- alert-monitor-managementSkill
- automation-job-executionSkill
- casb-policy-managementSkill
- casb-posture-assessmentSkill
- certificate-managementSkill
- change-managementSkill
- cloud-security-group-auditSkill
- cmdb-asset-managementSkill
- compute-instance-provisioningSkill
- config-backup-managementSkill
- container-workload-deploymentSkill
- crm-contact-managementSkill
- dcim-asset-managementSkill
- dhcp-scope-managementSkill
- dns-record-managementSkill
- dns-zone-managementSkill
- firewall-managementSkill
- incident-managementSkill
- infrastructure-plan-executionSkill
- interface-link-troubleshootingSkill
- ipam-allocationSkill
- load-balancingSkill
- log-querySkill
- metric-querySkill
- network-access-control-managementSkill
- network-health-verificationSkill
- network-state-collectionSkill
- notificationsSkill
- repository-pull-request-managementSkill
- routing-troubleshootingSkill
- sdwan-policy-managementSkill
- sdwan-site-onboardingSkill
- secret-retrievalSkill
- software-upgrade-lifecycleSkill
- vpn-tunnel-managementSkill
- vulnerability-lookupSkill
- waf-managementSkill
- wireless-network-managementSkill
- zero-trust-access-policy-managementSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Not for site-to-site IPsec or GRE tunnels between routers (see vpn-tunnel-management), for the access policy that decides who may reach the …
- Very specific: line 40
Only one implementation is listed in references/INDEX.md.
- Distinctive: line 55
Does not cover the policy that governs who may use a published application or private route, the provider's load balancing, or the internal …
- Very specific: line 57
Does not cover site-to-site IPsec or GRE tunnels.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Connector Tunnel Management
Creates a connector tunnel, attaches a published hostname or a private network route to it, diagnoses
its health, and retires it, following the platform's own documented procedure
(references/<vendor>/procedure.md).
When to use this skill
- An internal web or TCP service needs to be reachable from the Internet or from authorized users without an inbound firewall rule: create the tunnel and publish a hostname.
- A private IP range or private hostname needs to be reachable through a connector installed inside that network: create the tunnel and add a route.
- A tunnel shows as inactive, down, or degraded, or users get an error for a published application: diagnose it.
- A tunnel, its routes, or its connectors need to be removed (retired).
- Not for site-to-site IPsec or GRE tunnels between routers (see
vpn-tunnel-management), for the access policy that decides who may reach the application (seezero-trust-access-policy-management), or for the DNS records of a zone beyond the one the platform's procedure requires (seedns-record-management).
Universal concepts (apply regardless of platform)
- A connector tunnel is outbound-only. The connector runs inside the private network and opens connections out to the provider, so exposing a service does not require an inbound rule. Where documented, the tunnel object and the connector process are separate: creating the tunnel does not make it carry traffic until a connector runs with the tunnel's credential.
- The tunnel credential is a secret. Anyone holding it can run the tunnel. Handle it as a secret and do not echo it into logs or reports.
- Where the platform documents it, tunnel health describes the connector's link to the provider only. A tunnel can read healthy while the application behind it fails, so check the internal service separately.
- Where the platform documents it, routing is a separate record from the tunnel. Reaching a service needs a route or published hostname attached to the tunnel.
- Only one implementation is listed in
references/INDEX.md; each claim above holds only where the platform documents it.
Procedure
- Identify the target platform from the request or the
platformargument. If it is not inreferences/INDEX.md, stop: this skill does not cover it and does not improvise a procedure. - Open
references/<platform>/procedure.mdand follow it exactly, including its confirmation gates. It holds the full steps, error handling, patterns, limitations, tools, and verification checklist. - Report the outcome using that procedure's own status vocabulary, not a normalized one.
Known limitations
- Platform coverage is exactly the platforms in
references/INDEX.md. - Does not cover the policy that governs who may use a published application or private route, the provider's load balancing, or the internal service's own configuration.
- Does not cover site-to-site IPsec or GRE tunnels; those are routed to
vpn-tunnel-management.
Contributing to this skill
SKILL.md itself should only ever change for two reasons: a bug in the universal concepts or router
logic above, or adding a pointer to a newly supported platform. Platform-specific changes — a new
error, a corrected field, a changed path — belong in that platform's own references/<platform>/
files, never here.
Tools
Each platform assumes its own authenticated client; see references/INDEX.md for which, and that
platform's procedure.md for the operations.
Verification checklist
- Target platform confirmed against
references/INDEX.md - That platform's
procedure.mdwas followed, including its confirmation gates - The tunnel credential was not written into any output
- Outcome reported using the platform procedure's own status vocabulary
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

