CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cf-proxy

Deploy a free VLESS proxy/VPN node on Cloudflare Pages using edgetunnel. Automates code download, UUID generation, Pages deployment, free domain registration (DNSExit), DNS configuration, custom domain binding, and client setup for Shadowrocket/v2rayN/Clash. Uses Cloudflare Pages (not Workers) because Pages supports CNAME-based custom domains from any DNS provider, avoiding the need to host DNS on Cloudflare.

56

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/cf-proxy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-organized, concise overview with genuinely useful non-obvious context (Pages-vs-Workers rationale, free-tier limits, subdomain CNAME pitfall). However, it describes the workflow rather than instructing it — no executable commands for deployment, DNS, or client setup — so an agent reading it still cannot perform the core task without the external source repo.

Suggestions

Add the key executable commands inline (wrangler/Pages deploy, UUID generation, DNS CNAME creation via DNSExit API, and a filled-in VLESS connection URI template) so the 7 phases are actionable from SKILL.md alone.

Add explicit validation checkpoints and error-recovery loops, e.g., verify the *.pages.dev endpoint responds before binding the custom domain, and what to do when custom-domain binding fails or the domain's SNI gets blocked.

Move client-specific setup details (Shadowrocket/v2rayN/Clash config formats, QR-code usage) into references/ files linked from the body to deepen progressive disclosure.

DimensionReasoningScore

Conciseness

Sections are efficient and assume Claude's competence; the free-tier limits table and "Why Pages Instead of Workers" rationale convey non-obvious domain knowledge. Minor redundancy remains — "When to Use" bullets repeat the description and the Example section restates the 7-phase list — keeping it just below the lean anchor.

4 / 5

Actionability

The body only describes the phases ("Downloads edgetunnel — fetches the worker code from GitHub", "Skill walks through the full 7-phase setup interactively") with no executable commands for the core workflow — no deploy/DNS/UUID commands and no client-config URI template; only "npx skills add LewisLiu007/cf-proxy" is executable. This matches minimal concrete guidance with missing specific steps rather than incomplete-but-mostly-executable.

2 / 5

Workflow Clarity

The 7 phases are clearly sequenced and phase 7 mentions verification ("Verifies and configures — tests the node"), but checkpoints are implicit, there are no error-recovery loops for likely failures (Pages binding errors, blocked SNI beyond "domain rotation may be needed"), and steps lack executable commands.

3 / 5

Progressive Disclosure

The single SKILL.md is well organized into clear sections with no nested references and a readable overview. It falls short of the top anchor because operational detail that clearly belongs in references/ files (client configuration formats, DNS record commands, DNSExit registration steps) is absent from the bundle entirely rather than appropriately split into well-signaled one-level-deep files.

4 / 5

Total

13

/

20

Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is highly specific and distinctive, enumerating the full automation pipeline with concrete third-person verbs and named tools. Its one structural weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness and slightly limits natural triggering by users.

Suggestions

Append an explicit trigger clause, e.g., "Use when the user asks to set up a free Cloudflare proxy/VPN node, deploy edgetunnel, or bypass workers.dev SNI blocking."

Include natural user synonyms and variations such as "VPN node", "Cloudflare Workers proxy", or common non-English phrasings (e.g., 翻墙/科学上网) to broaden trigger coverage.

Trim the trailing rationale sentence ("Uses Cloudflare Pages (not Workers) because...") into a shorter differentiator or move it to the body to reduce description length.

DimensionReasoningScore

Specificity

"Automates code download, UUID generation, Pages deployment, free domain registration (DNSExit), DNS configuration, custom domain binding, and client setup for Shadowrocket/v2rayN/Clash" lists multiple concrete third-person actions with comprehensive coverage of the deployment lifecycle.

5 / 5

Completeness

The "what" is fully explicit, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the capability description itself is complete and unambiguous.

3 / 5

Trigger Term Quality

Good natural keyword coverage ("proxy/VPN node", "Cloudflare Pages", "VLESS", "DNS", "Shadowrocket/v2rayN/Clash") but a few natural user phrasings are missing, such as deploying to Workers, generic "VPN setup" variants, or non-English user phrasings, so it falls just below the comprehensive synonym/variant anchor.

4 / 5

Distinctiveness Conflict Risk

"Cloudflare Pages using edgetunnel", "VLESS", "DNSExit", and "CNAME-based custom domains" define a clear niche with distinct triggers and minimal overlap risk with generic networking or cloud skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

davepoon/buildwithclaude

Path

plugins/all-skills/skills/cf-proxy/SKILL.md

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.