site-onboarding
Skill2 starsChanged 4 months agoMITView on GitHub
Checkpoint-driven hand-holding for new machines and new Astro + Cloudflare sites using Portable Web Toolkit. Use when the user is new to Cloudflare, needs host setup, API tokens, Cloudflare MCP/plugin install, Workers vs Pages choice, or a guided site-starter scaffold. Load docs/agent-skills/ONBOARDING_STAGES.md and stop at each stage checkpoint.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- respira-press/agent-skills-wordpresstheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- respira-press/agent-skills-wordpress★ 49same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- Web_Toolkit/AGENTS.mdAGENTS.md
- brand-doctorSkill
- discovery-doctorSkill
- image-pipelineSkill
- instagram-cloneSkill
- pagespeed-diagnosticsSkill
- portable-web-toolkit-routerSkill
- portable-web-toolkitSkill
- site-maintenanceSkill
- site-readinessSkill
- site-starterSkill
- toolkit-updateSkill
- vectorize-pipelineSkill
- wcag-auditorSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Follow repository path docs/agent-skills/ONBOARDING_STAGES.md as the source of truth (stages S0–S9).
- Very specific: line 20
Read ONBOARDING_STAGES.md before acting.
- Distinctive: line 21
Prefer full agent control.
- Distinctive: line 22
Ask before host installs, Cloudflare plugin/MCP, scaffold writes, and production mutate/deploy — use the host question UI when available.
- Distinctive: line 25
Always ask Workers vs Pages static before scaffolding.
- Very specific: line 26
Verify Cloudflare tokens with cf-agent permissions audit before mutations.
- Very specific: line 34
Create profiles with init-site-profile create … --project-root .
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Site Onboarding
Follow repository path docs/agent-skills/ONBOARDING_STAGES.md as the source of truth (stages S0–S9). Read that file before acting; do not invent parallel onboarding steps.
When to use
- New machine / agent environment setup
- User does not know Cloudflare well
- Creating a brand-new client site folder
- Installing Cloudflare Skills/MCP alongside the toolkit
- Guiding API token creation and
.envwiring
Rules
- Read
ONBOARDING_STAGES.mdbefore acting. - Prefer full agent control; detect sandbox limits in S0.
- Ask before host installs, Cloudflare plugin/MCP, scaffold writes, and production mutate/deploy — use the host question UI when available.
- Global PWT footprint stays light (
portable-web-toolkit-routeronly). Link heavier skills into the project with explicit--skills. - Fresh folders gaining files from
site-starteris success, not failure. - Always ask Workers vs Pages static before scaffolding.
- Verify Cloudflare tokens with
cf-agent permissions auditbefore mutations. - Re-fetch https://developers.cloudflare.com/agent-setup/prompt.md live for MCP/plugin install commands.
.envdivision of labor — copysite-starter/.env.exampleinto the client project (canonical). Do not use the toolkit-repo root.env.example(pointer only) or invent a third template:- A (user):
CLOUDFLARE_API_TOKEN,GOOGLE_PAGESPEED_API_KEY - B (agent + user): account/zone/worker or pages names, public URL — propose and challenge
- C (explain early): PostHog + GA4 — why product analytics + Google reporting matter; do not defer the conversation
- D (optional): forms/Turnstile/Instagram; registrar keys only if needed (Porkbun is an example, not required)
- A (user):
- Be curious: challenge vague names, “analytics later,” and missing required API keys before calling setup done.
- Create profiles with
init-site-profile create … --project-root .so the JSON lands in the client folder (<siteId>.site-profile.json). Never write live clients intoWeb_Toolkit/site-profiles/.
After onboarding
Hand off to site-readiness, then portable-web-toolkit for deploy/ops.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.