makers-cli

EdgeOne Makers CLI command reference. Use when running edgeone CLI commands for dev, build, deploy, env management.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an efficient, actionable command reference with concrete copy-paste commands and clean sectioning. Workflow clarity is the only weak spot: production deploy and setup sequences lack validation/verification checkpoints.

Suggestions

Add a verification step after deploy (e.g., check deployment status or output URL) since 'edgeone makers deploy' is an outward-facing production operation.

Insert a checkpoint in First-time setup to confirm 'edgeone login' and 'edgeone makers link' succeeded before running 'env pull' or 'dev'.

Show how to confirm an env var was set (e.g., 'edgeone makers env ls') after 'edgeone makers env set', so batch env changes can be validated.

Dimension	Reasoning	Score
Conciseness	Lean command table plus short workflow snippets with no concept explanations or padding; every line earns its place and assumes Claude's competence.	3 / 3
Actionability	Copy-paste ready executable commands such as 'npm install -g edgeone', 'edgeone makers deploy', and 'edgeone makers env set <KEY> <VALUE>' with specific flags documented.	3 / 3
Workflow Clarity	First-time setup and deploy sequences are listed, but production deploy and link/login steps lack validation checkpoints; per the rubric, missing verification for an outward-facing deploy caps this at 2 rather than 3.	2 / 3
Progressive Disclosure	Well-organized self-contained sections (Install, Commands, Environment Variable, Common Workflows) with no need for external references — appropriate for a single-purpose command reference.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, names concrete action areas, includes an explicit 'Use when' trigger, and is anchored to a distinct product CLI. It meets the highest-level anchor on every dimension without padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete action areas — 'dev, build, deploy, env management' — matching the anchor for naming several specific actions rather than vague language.	3 / 3
Completeness	Explicitly states what ('EdgeOne Makers CLI command reference') and when ('Use when running edgeone CLI commands for dev, build, deploy, env management'), satisfying the what+when anchor.	3 / 3
Trigger Term Quality	Natural terms a user would say ('dev', 'build', 'deploy', 'env management') with an explicit 'edgeone CLI commands' trigger; good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Tied to the distinct 'edgeone' CLI product niche with product-specific triggers, making conflict with other skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: TencentEdgeOne/edgeone-makers-tools
Path: skills/makers-cli/SKILL.md
Commit: 77de93b

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.