Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Domain/DNS ops across Cloudflare, DNSimple, Namecheap for Peter. Use for onboarding zones to Cloudflare, flipping nameservers, setting redirects (Page Rules/Rulesets/Workers), updating redirect-worker mappings, and verifying DNS/HTTP. Source of truth: ~/Projects/manager.
Domain/DNS ops across Cloudflare, DNSimple, Namecheap for Peter. Use for onboarding zones to Cloudflare, flipping nameservers, setting redirects (Page Rules/Rulesets/Workers), updating redirect-worker mappings, and verifying DNS/HTTP. Source of truth: ~/Projects/manager.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
This skill is a thin router: use ~/Projects/manager as truth, run the repo scripts, follow the checklists.
~/Projects/manager/DOMAINS.md (domain -> target map; registrar hints; exclusions) ~/Projects/manager/DNS.md (Cloudflare onboarding + DNS/redirect checklist) ~/Projects/manager/redirect-worker.ts + ~/Projects/manager/redirect-worker-mapping.md (worker redirects)
Decide routing model Page Rule redirect (small scale, per-zone). Rulesets / Bulk Redirects (account-level; needs token perms). Worker route (fallback; uses redirect-worker). Cloudflare zone Create zone (UI), then confirm with cli4: cli4 --get name=example.com /zones Nameservers If registrar = Namecheap: cd ~/Projects/manager && source profile && bin/namecheap-set-ns example.com emma.ns.cloudflare.com scott.ns.cloudflare.com If registrar = DNSimple: see ~/Projects/manager/DNS.md for delegation API notes. DNS placeholders (so CF can terminate HTTPS) Proxied apex A + wildcard A → 192.0.2.1 (see ~/Projects/manager/DNS.md for exact cli4 calls). Redirect If using Page Rules: use the cli4 --post ... /pagerules template from ~/Projects/manager/DNS.md. If using Worker: update mapping (~/Projects/manager/redirect-worker-mapping.md), deploy/bind routes per ~/Projects/manager/DNS.md. Verify DNS: dig +short example.com @1.1.1.1 (expect CF anycast). HTTPS redirect: curl -I https://example.com (expect 301).
Cloudflare token sanity: source ~/.profile (prefer CLOUDFLARE_API_TOKEN; CF_API_TOKEN fallback). Disable “Block AI bots”: cd ~/Projects/manager && source profile && bin/cloudflare-ai-bots status / bin/cloudflare-ai-bots disable.
If you changed anything in ~/Projects/manager (docs, worker, scripts, mappings): commit there too. Review: cd ~/Projects/manager && git status && git diff Stage: git add <paths> Commit (Conventional Commits): git commit -m "feat: …" / fix: / docs: / chore: Push only when explicitly asked: git push origin main
Don’t touch .md lore domains or steipete.md unless explicitly asked; check ~/Projects/manager/DOMAINS.md. Confirm registrar before debugging CF “invalid nameservers” (often “wrong registrar”). Prefer reversible steps; verify after each change (NS → DNS → redirect).
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.