EdgeOne Makers Skills
🔌 Via the WorkBuddy EdgeOne connector? The connector's cli.json preAuth has already installed the edgeone CLI, checked its version, and logged the user in before you start — do NOT create tasks or run commands to install/upgrade the CLI, check its version, or check/perform login. Go straight to build + deploy. (Standalone skill / CI use has no preAuth — there, verify per references/makers-cli/SKILL.md and references/makers-deploy/SKILL.md.)
When you need EdgeOne Makers platform development guidance, read the matching Skill based on the task:
| Task |
Read |
| AI Agent development (DeepAgents, LangGraph, Claude SDK, OpenAI Agents, CrewAI) |
references/makers-agents/SKILL.md |
| Deploy project to EdgeOne |
references/makers-deploy/SKILL.md |
| Edge Functions (V8 lightweight functions) |
references/makers-edge-functions/SKILL.md |
| Cloud Functions (Node.js / Go / Python APIs) |
references/makers-cloud-functions/SKILL.md |
| KV + Blob Storage |
references/makers-storage/SKILL.md |
| Persist dynamic data for a site (messages, uploads, votes, save-state) — no database; use Blob |
references/makers-storage/SKILL.md |
| Middleware (auth, rewrites, routing) |
references/makers-middleware/SKILL.md |
| CLI command reference |
references/makers-cli/SKILL.md |
| Project structure / scaffolding |
references/makers-recipes/SKILL.md |
| Environment adaptation (WorkBuddy / sandbox / CI) |
references/makers-env-adaption/SKILL.md |
⚠️ Before writing any code (applies to every task)
These cross-cutting rules bite even pure static "develop + deploy" tasks — follow them no matter which sub-skill you loaded. Full detail in references/makers-recipes/SKILL.md.
- Write
index.html LAST. Creating it instantly triggers the IDE file:// preview (unavoidable in WorkBuddy). Write every dependency first — style.css, script.js, Cloud Functions (functions/), static assets — then index.html last, so the preview opens with all assets already in place. Write it in one shot; don't scaffold an empty shell and fill it in with repeated edits (every save re-renders and flickers). For a tiny single-page tool, inline the CSS/JS into one index.html.
- Preview via the dev server (8088), then the live URL. After development, run
edgeone makers dev — it serves on http://127.0.0.1:8088/ — and present that 127.0.0.1:8088 URL in the browser via present_files. After deploying, open and present the live deployment URL. (Blob/KV projects need edgeone makers dev -n <project-name>.)
- Read
references/makers-recipes/SKILL.md before scaffolding for project structure and Cloud Function file-naming — a function file missing its .js / .py / .go extension is silently served as static HTML.
Scripts (Quick Actions)
For common operations, run these scripts directly instead of manually composing CLI commands:
| Action |
Script |
Description |
| Install/upgrade CLI |
node references/makers-cli/scripts/install-cli.mjs |
Auto-selects fastest registry, idempotent |
| Deploy project |
node references/makers-deploy/scripts/deploy.mjs --name <project> |
Full pipeline: CLI check → auth → deploy → JSON output |
| Deploy to preview |
node references/makers-deploy/scripts/deploy.mjs --name <project> --preview |
Same as above, preview environment |
Scripts output structured JSON on stdout. Exit code 0 = success.
⚠️ Only read the Skill relevant to the current task. Do not load all skills at once.
1---2name: edgeone-pages3description: EdgeOne Makers / EdgeOne Pages platform development router — the single entry point for building, storing data, and deploying on Tencent EdgeOne Makers. Trigger whenever the user develops, scaffolds, or deploys anything on EdgeOne Makers / EdgeOne Pages: AI agents (DeepAgents, LangGraph, CrewAI, OpenAI/Claude SDK), Cloud Functions (Node/Go/Python), Edge Functions (V8), KV + Blob storage, middleware, CLI usage, project scaffolding, and — importantly — persisting dynamic site data (messages, uploads, votes, save-state) where there is NO managed database, so Blob is used as the backend. Also trigger on "deploy to EdgeOne", "上线", "发布", "部署到 EdgeOne". This SKILL is a routing table; read only the sub-skill relevant to the current task, never all of them at once.4---5
6# EdgeOne Makers Skills
7
8> 🔌 **Via the WorkBuddy EdgeOne connector?** The connector's `cli.json` preAuth has already installed the `edgeone` CLI, checked its version, and logged the user in **before you start** — do NOT create tasks or run commands to install/upgrade the CLI, check its version, or check/perform login. Go straight to build + deploy. (Standalone skill / CI use has no preAuth — there, verify per `references/makers-cli/SKILL.md` and `references/makers-deploy/SKILL.md`.)
9
10When you need EdgeOne Makers platform development guidance, read the matching Skill based on the task:
11
12| Task | Read |
13|------|------|
14| AI Agent development (DeepAgents, LangGraph, Claude SDK, OpenAI Agents, CrewAI) | references/makers-agents/SKILL.md |
15| Deploy project to EdgeOne | references/makers-deploy/SKILL.md |
16| Edge Functions (V8 lightweight functions) | references/makers-edge-functions/SKILL.md |
17| Cloud Functions (Node.js / Go / Python APIs) | references/makers-cloud-functions/SKILL.md |
18| KV + Blob Storage | references/makers-storage/SKILL.md |
19| Persist dynamic data for a site (messages, uploads, votes, save-state) — **no database; use Blob** | references/makers-storage/SKILL.md |
20| Middleware (auth, rewrites, routing) | references/makers-middleware/SKILL.md |
21| CLI command reference | references/makers-cli/SKILL.md |
22| Project structure / scaffolding | references/makers-recipes/SKILL.md |
23| Environment adaptation (WorkBuddy / sandbox / CI) | references/makers-env-adaption/SKILL.md |
24
25## ⚠️ Before writing any code (applies to every task)
26
27These cross-cutting rules bite even pure static "develop + deploy" tasks — follow them no matter which sub-skill you loaded. Full detail in `references/makers-recipes/SKILL.md`.
28
29- **Write `index.html` LAST.** Creating it instantly triggers the IDE `file://` preview (unavoidable in WorkBuddy). Write every dependency first — `style.css`, `script.js`, Cloud Functions (`functions/`), static assets — then `index.html` last, so the preview opens with all assets already in place. Write it in one shot; don't scaffold an empty shell and fill it in with repeated edits (every save re-renders and flickers). For a tiny single-page tool, inline the CSS/JS into one `index.html`.
30- **Preview via the dev server (8088), then the live URL.** After development, run `edgeone makers dev` — it serves on `http://127.0.0.1:8088/` — and present that `127.0.0.1:8088` URL in the browser via `present_files`. After deploying, open and present the live deployment URL. (Blob/KV projects need `edgeone makers dev -n <project-name>`.)
31- **Read `references/makers-recipes/SKILL.md` before scaffolding** for project structure and Cloud Function file-naming — a function file missing its `.js` / `.py` / `.go` extension is silently served as static HTML.
32
33## Scripts (Quick Actions)
34
35For common operations, run these scripts directly instead of manually composing CLI commands:
36
37| Action | Script | Description |
38|--------|--------|-------------|
39| Install/upgrade CLI | `node references/makers-cli/scripts/install-cli.mjs` | Auto-selects fastest registry, idempotent |
40| Deploy project | `node references/makers-deploy/scripts/deploy.mjs --name <project>` | Full pipeline: CLI check → auth → deploy → JSON output |
41| Deploy to preview | `node references/makers-deploy/scripts/deploy.mjs --name <project> --preview` | Same as above, preview environment |
42
43Scripts output structured JSON on stdout. Exit code 0 = success.
44
45⚠️ Only read the Skill relevant to the current task. Do not load all skills at once.
ahang1598