How do I install the Makers CLI skill?

Run npx skillmds@latest add infometa/makers-cli in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Makers CLI safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Makers CLI?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Makers CLI free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Makers CLI?

infometa (@infometa) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Makers CLI by infometa — Agent Skill

Name: Makers CLI
Rating: 4.2 (5 reviews)
Author: infometa

File contents

EdgeOne Makers CLI Reference

Install

Default — install from the npmmirror registry (significantly faster for users in mainland China; the CLI package itself is identical on both registries):

npm install -g edgeone@latest --registry=https://registry.npmmirror.com

Verify: edgeone -v — output must be 1.6.7 or higher.

If the mirror install fails → retry once against the official registry

npmmirror is a lazy-sync mirror, so a freshly published CLI version can lag behind by minutes. If the mirror install fails, or edgeone -v reports a version below 1.6.7, fall back to the official registry:

npm install -g edgeone@latest --registry=https://registry.npmjs.org

Tell the user which registry you used and why before running the fallback. Do not silently retry more than once per registry.

Install error reference

Error	Cause	Action
`ETIMEDOUT` / `ENOTFOUND` / `EAI_AGAIN` / `network`	Registry unreachable	Retry once on the other registry (see above)
`edgeone -v` < `1.6.7` after install	Mirror lag, or a stale global install	Retry on the official registry
`EACCES` / `permission denied`	No write access to the global prefix	Do NOT use `sudo` unprompted. Tell the user and suggest `npm config set prefix ~/.npm-global` (plus adding `~/.npm-global/bin` to PATH), or ask them to run the install themselves
`command not found: edgeone` right after a successful install	Global bin dir not on PATH	Report the npm global prefix (`npm prefix -g`) and ask the user to add its `bin/` to PATH

⚠️ Version >= 1.6.7 is required. Older versions hang on interactive prompts in Agent/CI/sandbox environments and lack --json output. Never proceed with an outdated version.

Commands

Command	Description
`edgeone makers dev`	Start local dev server (agent runtime + frontend)
`edgeone makers build`	Build agents + frontend into `.edgeone/`
`edgeone makers deploy`	Build and deploy to EdgeOne Makers
`edgeone makers deploy -n <name>`	Deploy as a new project
`edgeone makers deploy -t <token>`	Deploy with API token (CI/headless)
`edgeone makers deploy -e preview`	Deploy to preview environment
`edgeone makers link`	Link local project to remote EdgeOne project
`edgeone makers env pull`	Pull remote env vars to local `.env`
`edgeone makers env set <KEY> <VALUE>`	Set a remote environment variable
`edgeone makers env ls`	List remote environment variables
`edgeone makers env rm <KEY>`	Remove a remote environment variable
`edgeone login`	Login (browser-based)
`edgeone login --site china`	Login to China site
`edgeone login --site global`	Login to Global site
`edgeone whoami`	Check current login status

Environment Variable

Before any edgeone command, set:

export PAGES_SOURCE=skills

Or inline: PAGES_SOURCE=skills edgeone makers dev

Common Workflows

First-time setup

npm install -g edgeone@latest --registry=https://registry.npmmirror.com
edgeone login
PAGES_SOURCE=skills edgeone makers link
PAGES_SOURCE=skills edgeone makers env pull
PAGES_SOURCE=skills edgeone makers dev

Deploy

edgeone makers deploy

Set env vars for production

edgeone makers env set WSA_API_KEY "your-key"
edgeone makers env set SUPABASE_URL "https://xxx.supabase.co"

---name: makers-clidescription: EdgeOne Makers CLI command reference. Use when running edgeone CLI commands for dev, build, deploy, env management.--- # EdgeOne Makers CLI Reference ## Install **Default — install from the npmmirror registry** (significantly faster for users in mainland China; the CLI package itself is identical on both registries): ```bash npm install -g edgeone@latest --registry=https://registry.npmmirror.com ``` Verify: `edgeone -v` — output must be `1.6.7` or higher. ### If the mirror install fails → retry once against the official registry npmmirror is a lazy-sync mirror, so a freshly published CLI version can lag behind by minutes. If the mirror install fails, or `edgeone -v` reports a version below `1.6.7`, fall back to the official registry: ```bash npm install -g edgeone@latest --registry=https://registry.npmjs.org ``` Tell the user which registry you used and why before running the fallback. Do not silently retry more than once per registry. ### Install error reference | Error | Cause | Action | |-------|-------|--------| | `ETIMEDOUT` / `ENOTFOUND` / `EAI_AGAIN` / `network` | Registry unreachable | Retry once on the other registry (see above) | | `edgeone -v` < `1.6.7` after install | Mirror lag, or a stale global install | Retry on the official registry | | `EACCES` / `permission denied` | No write access to the global prefix | Do NOT use `sudo` unprompted. Tell the user and suggest `npm config set prefix ~/.npm-global` (plus adding `~/.npm-global/bin` to PATH), or ask them to run the install themselves | | `command not found: edgeone` right after a successful install | Global bin dir not on PATH | Report the npm global prefix (`npm prefix -g`) and ask the user to add its `bin/` to PATH | > ⚠️ Version `>= 1.6.7` is required. Older versions hang on interactive prompts in Agent/CI/sandbox environments and lack `--json` output. Never proceed with an outdated version. ## Commands | Command | Description | |---------|-------------| | `edgeone makers dev` | Start local dev server (agent runtime + frontend) | | `edgeone makers build` | Build agents + frontend into `.edgeone/` | | `edgeone makers deploy` | Build and deploy to EdgeOne Makers | | `edgeone makers deploy -n <name>` | Deploy as a new project | | `edgeone makers deploy -t <token>` | Deploy with API token (CI/headless) | | `edgeone makers deploy -e preview` | Deploy to preview environment | | `edgeone makers link` | Link local project to remote EdgeOne project | | `edgeone makers env pull` | Pull remote env vars to local `.env` | | `edgeone makers env set <KEY> <VALUE>` | Set a remote environment variable | | `edgeone makers env ls` | List remote environment variables | | `edgeone makers env rm <KEY>` | Remove a remote environment variable | | `edgeone login` | Login (browser-based) | | `edgeone login --site china` | Login to China site | | `edgeone login --site global` | Login to Global site | | `edgeone whoami` | Check current login status | ## Environment Variable Before any `edgeone` command, set: ```bash export PAGES_SOURCE=skills ``` Or inline: `PAGES_SOURCE=skills edgeone makers dev` ## Common Workflows ### First-time setup ```bash npm install -g edgeone@latest --registry=https://registry.npmmirror.com edgeone login PAGES_SOURCE=skills edgeone makers link PAGES_SOURCE=skills edgeone makers env pull PAGES_SOURCE=skills edgeone makers dev ``` ### Deploy ```bash edgeone makers deploy ``` ### Set env vars for production ```bash edgeone makers env set WSA_API_KEY "your-key" edgeone makers env set SUPABASE_URL "https://xxx.supabase.co" ```

Frequently asked questions

Makers CLI