cloudflare-manager
Manage Cloudflare DNS records, Tunnels (cloudflared), and Zero Trust policies. Use for pointing domains, exposing local services via tunnels, and updating ingress rules.
87
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies the Cloudflare-specific domain and lists concrete management actions. It includes explicit 'Use for' guidance which helps Claude know when to select it. The main weakness is that trigger terms could include more natural user language variations beyond the technical product names.
Suggestions
Add common user variations to trigger terms such as 'DNS setup', 'domain configuration', 'tunnel setup', or 'access control' to improve discoverability
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Manage Cloudflare DNS records, Tunnels (cloudflared), and Zero Trust policies' with specific use cases like 'pointing domains, exposing local services via tunnels, and updating ingress rules.' | 3 / 3 |
Completeness | Clearly answers both what ('Manage Cloudflare DNS records, Tunnels, and Zero Trust policies') and when ('Use for pointing domains, exposing local services via tunnels, and updating ingress rules') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'Cloudflare', 'DNS records', 'Tunnels', 'cloudflared', 'Zero Trust', 'domains', 'ingress rules', but missing common user variations like 'DNS', 'domain setup', 'tunnel configuration', or 'access policies'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific to Cloudflare ecosystem with distinct product names (cloudflared, Zero Trust) that are unlikely to conflict with other skills; clear niche in cloud infrastructure management. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that provides actionable commands for Cloudflare management. The content respects Claude's intelligence and provides executable guidance. The main weakness is the lack of explicit validation/verification steps after applying DNS or ingress changes, which is important for infrastructure operations.
Suggestions
Add explicit validation steps after DNS and ingress operations (e.g., 'Verify DNS propagation: `dig <subdomain>.<domain>`' or 'Verify tunnel status: `cloudflared tunnel info`')
Include a feedback loop for error recovery when ingress updates fail (e.g., 'If service restart fails: check logs with `journalctl -u cloudflared`, fix config, retry')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient, assuming Claude knows what Cloudflare, DNS records, and tunnels are. No unnecessary explanations of basic concepts; every section serves a clear purpose. | 3 / 3 |
Actionability | Provides specific, executable commands with full paths and flags. Commands are copy-paste ready with clear parameter placeholders like `<subdomain>` and `<ip>`. | 3 / 3 |
Workflow Clarity | Steps are listed but validation is limited. The `--dry-run` flag is mentioned for ingress updates, but there's no explicit validation checkpoint or error recovery workflow after applying changes. | 2 / 3 |
Progressive Disclosure | Clear overview structure with well-signaled one-level-deep references to sudoers.example and tunnel-guide.md. Content is appropriately split between quick reference and detailed documentation. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.