一键在 Manus 中运行任何 Skill

$pwd:

flarectl

Name: Flarectl
Author: kryptobaseddev

// Cloudflare CLI management via the flarectl tool. Use when the user asks to manage Cloudflare zones, DNS records, firewall rules, cache purging, or zone exports using flarectl. Covers onboarding (installation, API Token vs Global API Key setup), zone CRUD, DNS record CRUD, firewall access rules, cache purging, zone file export, and permission verification. Also guides when to use Wrangler instead (Workers, Pages, R2, KV, D1). Triggers on: 'flarectl', 'cloudflare cli', 'cloudflare dns', 'cloudflare zone', 'CF_API_TOKEN', 'CF_API_KEY', 'manage cloudflare', 'cloudflare firewall', 'purge cloudflare cache', 'cloudflare setup', 'flarectl setup'.

在 Manus 中运行

$ git log --oneline --stat

stars:0

forks:0

updated:2026年5月21日 22:33

文件资源管理器

4 个文件

SKILL.md

readonly

name

flarectl

description

Cloudflare CLI management via the flarectl tool. Use when the user asks to manage Cloudflare zones, DNS records, firewall rules, cache purging, or zone exports using flarectl. Covers onboarding (installation, API Token vs Global API Key setup), zone CRUD, DNS record CRUD, firewall access rules, cache purging, zone file export, and permission verification. Also guides when to use Wrangler instead (Workers, Pages, R2, KV, D1). Triggers on: 'flarectl', 'cloudflare cli', 'cloudflare dns', 'cloudflare zone', 'CF_API_TOKEN', 'CF_API_KEY', 'manage cloudflare', 'cloudflare firewall', 'purge cloudflare cache', 'cloudflare setup', 'flarectl setup'.

flarectl — Cloudflare CLI Skill

Important: Scope Boundaries

flarectl manages zones, DNS, firewall rules, cache, and zone exports. It does NOT support Workers, Pages, R2, KV, D1, or Queues — use Wrangler (npm i -g wrangler) for those.

flarectl is legacy software (v0 branch of cloudflare-go). It works and is installable via Homebrew (v0.116.0+), but receives no new features.

Onboarding Workflow

Guide users through setup in this order:

Install → verify with flarectl --version
Authenticate → choose API Token (recommended) or Global API Key
Verify access → run flarectl zone list or flarectl user info
Verify token permissions → run scripts/cf-check-access.sh

See references/setup-guide.md for detailed installation and authentication instructions.

Authentication Quick Reference

Method	Env Vars	Security
API Token (recommended)	`CF_API_TOKEN`	Scoped permissions, limited blast radius
Global API Key (legacy)	`CF_API_KEY` + `CF_API_EMAIL`	Full account access, dangerous if leaked

Precedence: CF_API_TOKEN wins if set. Otherwise both CF_API_KEY and CF_API_EMAIL required.

Note: flarectl uses CF_ prefixed vars. Wrangler uses CLOUDFLARE_ prefixed vars. They are NOT interchangeable.

Verifying Access & Permissions

Run scripts/cf-check-access.sh to verify token validity and test common permissions. Or manually:

# Verify token is valid (API Token only)
curl -s "https://api.cloudflare.com/client/v4/user/tokens/verify" \
  -H "Authorization: Bearer $CF_API_TOKEN" | jq .

# List token details and policies
curl -s "https://api.cloudflare.com/client/v4/user/tokens" \
  -H "Authorization: Bearer $CF_API_TOKEN" | jq '.result[] | {name, status, policies}'

# Quick permission tests via flarectl
flarectl zone list          # Tests Zone:Read
flarectl user info          # Tests User Details:Read
flarectl dns list --zone example.com  # Tests DNS:Read

Required Token Permissions by Command

Command	Required Permission
`zone list/info`	Zone: Zone: Read
`zone create/delete`	Zone: Zone: Edit
`dns list`	Zone: DNS: Read
`dns create/update/delete`	Zone: DNS: Edit
`zone purge`	Zone: Cache Purge: Purge
`firewall rules list`	Zone: Firewall Services: Read
`firewall rules create/update/delete`	Zone: Firewall Services: Edit
`user info`	User: User Details: Read

Command Reference

See references/command-reference.md for the complete command reference with all flags and examples covering:

Zone management (list, info, create, delete, purge, export, lockdown)
DNS record CRUD (list, create, update, create-or-update, delete)
Firewall access rules (list, create, update, delete — IP/CIDR/ASN/country)
User-agent blocking, page rules, IP ranges
Command aliases quick reference

Global Options

--json            Output as JSON instead of ASCII table
--account-id <id> Account ID (or set CF_ACCOUNT_ID)
--help, -h        Show help
--version, -v     Show version

Always use --json when parsing output programmatically.

Common Workflows

Add a zone and configure DNS

flarectl zone create --zone example.com --jumpstart
flarectl dns create --zone example.com --name www --type A --content 203.0.113.50 --proxy
flarectl dns create --zone example.com --name @ --type MX --content mail.example.com --priority 10

Bulk DNS update (idempotent)

# create-or-update is an upsert — safe to run repeatedly
flarectl dns create-or-update --zone example.com --name app --type CNAME --content new-backend.example.com --proxy

Purge cache

flarectl zone purge --zone example.com --everything
# Or selective:
flarectl zone purge --zone example.com --files "https://example.com/style.css"

Export zone file (BIND format)

flarectl zone export --zone example.com > example.com.zone

Block an IP via firewall

flarectl firewall rules create --zone example.com --value 198.51.100.1 --mode block --notes "Abuse"

When to Use Wrangler Instead

Need	Tool
DNS, zones, firewall, cache purge, zone export	flarectl
Workers, Pages, R2, KV, D1, Queues, Durable Objects	Wrangler
Full API surface or features not in either CLI	curl + Cloudflare API

related-skills.json

同仓库

proxmox-admin.md

from "kryptobaseddev/awesome-skills"

Use this skill to administer a Proxmox VE 8.x/9.x host, node, or cluster remotely — provisioning, day-2 ops, troubleshooting, hardening, IaC, migration off VMware/ESXi. Covers KVM VMs (qm), LXC containers (pct; OCI in 9.1+), storage (pvesm; ZFS, LVM-thin, NFS, Ceph), networking and SDN (zones, VNets, Fabrics in 9.0+, BGP/WireGuard in 9.2+), clustering and HA (pvecm, ha-manager, Dynamic Load Balancer in 9.2+), backup/restore (vzdump, Proxmox Backup Server), API tokens (pveum), firewall and security, and IaC (Terraform bpg/Telmate, Ansible). Onboards a YAML connection profile (SSH key + API token + defaults) under ~/.config/proxmox-admin/ and drives ops via bundled SSH/REST helpers or cv4pve-cli. Trigger even when the user does not say "Proxmox" — e.g. "spin up a VM on my homelab", "the LXC container is OOMing", "web UI at port 8006", "vCenter alternative", ProxMox, PVE, PBS, ProxLB, PegaProx, vmbr0, vmid, cloud-init, GPU passthrough, ZFS pool, cluster quorum, qm, pct, pvesh.

2026-05-220

agent-browser.md

from "kryptobaseddev/awesome-skills"

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

2026-05-210

code-optimizer.md

from "kryptobaseddev/awesome-skills"

Deep code optimization audit using parallel specialist agents. Each agent hunts for performance anti-patterns, inefficiencies, and suboptimal code using pattern-based detection (Grep/Glob) WITHOUT reading the full source code first — avoiding anchoring bias on existing implementations. Covers ALL optimization domains: database queries, memory leaks, algorithmic complexity, concurrency, bundle size, dead code, I/O & network, rendering/UI, data structures, error handling, caching, build config, security-performance, logging, and infrastructure. Use when asked to: 'optimize my code', 'find performance issues', 'audit code quality', 'speed up my app', 'find bottlenecks', 'code review for performance', 'find anti-patterns', 'improve code efficiency', 'reduce latency', 'optimize performance', 'code smell detection', 'find slow code', 'optimize this project', 'performance audit', 'code optimization'. Also triggers on: 'optimizar codigo', 'encontrar cuellos de botella', 'mejorar rendimiento'.

2026-05-210

drizzle-orm.md

from "kryptobaseddev/awesome-skills"

Expert guidance for Drizzle ORM and drizzle-kit, covering the v1.0.0-beta (RQBv2, defineRelations, new migration folder structure, consolidated validators) and stable 0.x releases. Includes Node 24 node:sqlite integration with drizzle-orm/node-sqlite driver, drizzle-orm/zod validation (createInsertSchema, createSelectSchema, createUpdateSchema, createSchemaFactory), schema design for all dialects (SQLite preferred, PostgreSQL, MySQL, MSSQL), migrations (generate/migrate), rapid prototyping (push), and drizzle-seed. Use when: (1) working with Drizzle ORM projects, (2) setting up or running migrations with drizzle-kit, (3) using Node 24 built-in node:sqlite with Drizzle, (4) validating data with drizzle-orm/zod or drizzle-zod, (5) upgrading from 0.x to v1 beta, (6) defining relations with defineRelations or RQBv2, (7) seeding databases with drizzle-seed, (8) configuring drizzle.config.ts, or (9) any Drizzle ORM question.

2026-05-210

neonctl.md

from "kryptobaseddev/awesome-skills"

Comprehensive Neon CLI (neonctl) management for serverless Postgres. Use when managing Neon projects, branches, databases, roles, connection strings, IP allowlists, operations, or authentication via the neonctl command-line tool. Triggers on: 'neonctl', 'neon cli', 'neon projects', 'neon branches', 'neon databases', 'neon roles', 'neon connection-string', 'neon set-context', 'neon ip-allow', 'neon operations', 'neon auth', 'neon schema-diff', 'neon branch reset', 'neon branch restore', 'NEON_API_KEY', 'neon completion', 'neon init', 'manage neon', 'neon setup', 'neonctl install'.

2026-05-210

payment-provider-oauth.md

from "kryptobaseddev/awesome-skills"

Build OAuth connections for payment providers (Stripe Connect, Square) in SvelteKit applications. Use when creating booking platforms, marketplaces, or applications where businesses need to connect their own payment accounts. Covers complete OAuth flows, database schema with Drizzle, token management, security best practices, webhook handling, and extensible provider abstraction for easily adding new providers. Integrates with Better-Auth authentication and includes token refresh strategies.

2026-05-210

package.json

"author": "kryptobaseddev"

"repository": "kryptobaseddev/awesome-skills"

打开 GitHub 仓库查看创作者相关仓库

$ install --global

$ download --local

在 Manus 中运行

$ useful --forSOC

网络与计算机系统管理员计算机与数学类职业15-1244L4

name

flarectl

description

flarectl — Cloudflare CLI Skill

Important: Scope Boundaries

flarectl manages zones, DNS, firewall rules, cache, and zone exports. It does NOT support Workers, Pages, R2, KV, D1, or Queues — use Wrangler (npm i -g wrangler) for those.

flarectl is legacy software (v0 branch of cloudflare-go). It works and is installable via Homebrew (v0.116.0+), but receives no new features.

Onboarding Workflow

Guide users through setup in this order:

Install → verify with flarectl --version
Authenticate → choose API Token (recommended) or Global API Key
Verify access → run flarectl zone list or flarectl user info
Verify token permissions → run scripts/cf-check-access.sh

See references/setup-guide.md for detailed installation and authentication instructions.

Authentication Quick Reference

Method	Env Vars	Security
API Token (recommended)	`CF_API_TOKEN`	Scoped permissions, limited blast radius
Global API Key (legacy)	`CF_API_KEY` + `CF_API_EMAIL`	Full account access, dangerous if leaked

Precedence: CF_API_TOKEN wins if set. Otherwise both CF_API_KEY and CF_API_EMAIL required.

Note: flarectl uses CF_ prefixed vars. Wrangler uses CLOUDFLARE_ prefixed vars. They are NOT interchangeable.

Verifying Access & Permissions

Run scripts/cf-check-access.sh to verify token validity and test common permissions. Or manually:

# Verify token is valid (API Token only)
curl -s "https://api.cloudflare.com/client/v4/user/tokens/verify" \
  -H "Authorization: Bearer $CF_API_TOKEN" | jq .

# List token details and policies
curl -s "https://api.cloudflare.com/client/v4/user/tokens" \
  -H "Authorization: Bearer $CF_API_TOKEN" | jq '.result[] | {name, status, policies}'

# Quick permission tests via flarectl
flarectl zone list          # Tests Zone:Read
flarectl user info          # Tests User Details:Read
flarectl dns list --zone example.com  # Tests DNS:Read

Required Token Permissions by Command

Command	Required Permission
`zone list/info`	Zone: Zone: Read
`zone create/delete`	Zone: Zone: Edit
`dns list`	Zone: DNS: Read
`dns create/update/delete`	Zone: DNS: Edit
`zone purge`	Zone: Cache Purge: Purge
`firewall rules list`	Zone: Firewall Services: Read
`firewall rules create/update/delete`	Zone: Firewall Services: Edit
`user info`	User: User Details: Read

Command Reference

See references/command-reference.md for the complete command reference with all flags and examples covering:

Zone management (list, info, create, delete, purge, export, lockdown)
DNS record CRUD (list, create, update, create-or-update, delete)
Firewall access rules (list, create, update, delete — IP/CIDR/ASN/country)
User-agent blocking, page rules, IP ranges
Command aliases quick reference

Global Options

--json            Output as JSON instead of ASCII table
--account-id <id> Account ID (or set CF_ACCOUNT_ID)
--help, -h        Show help
--version, -v     Show version

Always use --json when parsing output programmatically.

Common Workflows

Add a zone and configure DNS

flarectl zone create --zone example.com --jumpstart
flarectl dns create --zone example.com --name www --type A --content 203.0.113.50 --proxy
flarectl dns create --zone example.com --name @ --type MX --content mail.example.com --priority 10

Bulk DNS update (idempotent)

# create-or-update is an upsert — safe to run repeatedly
flarectl dns create-or-update --zone example.com --name app --type CNAME --content new-backend.example.com --proxy

Purge cache

flarectl zone purge --zone example.com --everything
# Or selective:
flarectl zone purge --zone example.com --files "https://example.com/style.css"

Export zone file (BIND format)

flarectl zone export --zone example.com > example.com.zone

Block an IP via firewall

flarectl firewall rules create --zone example.com --value 198.51.100.1 --mode block --notes "Abuse"

When to Use Wrangler Instead

Need	Tool
DNS, zones, firewall, cache purge, zone export	flarectl
Workers, Pages, R2, KV, D1, Queues, Durable Objects	Wrangler
Full API surface or features not in either CLI	curl + Cloudflare API

flarectl

flarectl — Cloudflare CLI Skill

Important: Scope Boundaries

Onboarding Workflow

Authentication Quick Reference

Verifying Access & Permissions

Required Token Permissions by Command

Command Reference

Global Options

Common Workflows

Add a zone and configure DNS

Bulk DNS update (idempotent)

Purge cache

Export zone file (BIND format)

Block an IP via firewall

When to Use Wrangler Instead

同仓库更多 Skills

同仓库更多 Skills

flarectl — Cloudflare CLI Skill

Important: Scope Boundaries

Onboarding Workflow

Authentication Quick Reference

Verifying Access & Permissions

Required Token Permissions by Command

Command Reference

Global Options

Common Workflows

Add a zone and configure DNS

Bulk DNS update (idempotent)

Purge cache

Export zone file (BIND format)

Block an IP via firewall

When to Use Wrangler Instead