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.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
Deploy a free VLESS proxy node on Cloudflare Pages + edgetunnel, with WebSocket over TLS through Cloudflare's global CDN.
*.linkpc.net)*.pages.devHelp me set up a free Cloudflare proxy node
/cf-proxy
Deploy a VLESS proxy on Cloudflare using my domain example.com
Fix my Cloudflare proxy — Shadowrocket can't connect
Client (Shadowrocket / v2rayN / Clash)
↓ VLESS over WebSocket over TLS (port 443)
Custom Domain (CNAME → *.pages.dev)
↓
Cloudflare CDN (global edge)
↓
Cloudflare Pages Function (edgetunnel _worker.js)
↓ TCP outbound
Target Website
workers.dev domains are blocked at the TLS SNI layer by some firewalls| Resource | Free Quota | Impact on Proxy |
|---|---|---|
| Requests | 100,000/day | WebSocket connection = 1 request; messages free |
| Bandwidth | Unlimited | No egress fees — biggest advantage |
| CPU time | 10 ms/request | Proxy is I/O-bound, typically <3ms |
| Memory | 128 MB/isolate | Sufficient |
User: "帮我搭建一个 Cloudflare 代理节点"
Output: Skill walks through the full 7-phase setup interactively — collecting Cloudflare credentials, generating config, deploying to Pages, registering a free domain if needed, configuring DNS, binding the custom domain, and providing the final VLESS connection URI for the user's proxy client.
vless.example.com), never the root domain — a root CNAME destroys the zone's SOA/NS recordshttps://your-domain/<admin-password> provides ready-to-scan QR codes for mobile clientsgh)npx skills add LewisLiu007/cf-proxyNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Automate ActiveCampaign tasks via Rube MCP (Composio): manage contacts, tags, list subscriptions, automation enrollment, and tasks. Always search tools first for current schemas.
The English summary is being prepared. Showing the original description.
Pull the ads a competitor is running right now on Meta (Facebook/Instagram) and Google, then extract the hooks, offers, CTAs and landing pages worth modelling. Use when writing ad copy, planning creative tests, choosing a landing page angle, or when the user asks "what is X advertising", "what ads does X run", "find competitor ad hooks". Reads live Ad Library and Ads Transparency data through the Tracetify MCP; falls back to a manual Ad Library walkthrough when the connector is absent.
The English summary is being prepared. Showing the original description.
Analytics your AI agent can actually use. Track, analyze, run A/B experiments, and optimize across all your projects via CLI. Includes a growth playbook so your agent knows HOW to grow, not just what to track.
The English summary is being prepared. Showing the original description.
Teaches when to recall from long-term memory before acting and when to save durable decisions, corrections and failures afterwards. Use when a memory tool or MCP memory server is connected but the agent is not using it consistently, when the user complains that the assistant forgets preferences, conventions or past decisions between sessions, or when setting up persistent memory for a project. Works with any memory backend: a folder of Markdown files, a local MCP server, or a managed service.
The English summary is being prepared. Showing the original description.
Audit local AI coding-agent sessions with agenttrace for cost, tokens, tool failures, latency, anomalies, health, diffs, and CI gates.
The English summary is being prepared. Showing the original description.
Checks which private files (.env, keys, secrets) Claude Code and its subagents reached in this project, whether a value came into an agent's context, and which key to change, by running the open source agentwhy CLI over the session records Claude Code already keeps on disk. Use when the user asks whether the agent or a subagent read their .env or other secrets, which private files a session touched, whether a key leaked into the conversation, or which key to rotate. Runs locally and never prints a secret value.
The English summary is being prepared. Showing the original description.