edgeone-makers-recipes

Project structure templates and scaffolding recipes for typical EdgeOne Makers applications — full-stack apps, static sites, API services, and AI agent projects.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/makers-recipes/SKILL.md

Quality

Content

65%

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

The body is highly actionable with concrete executable recipes and clear section organization, but it is held back by repeated boilerplate file trees, missing validation checkpoints in its setup workflows, and a dangling kv-storage.md reference with no supporting bundle files.

Suggestions

Factor the repeated index.html / style.css / script.js frontend block out of each recipe and state it once, or note that all recipes share a standard static frontend, to tighten token use (conciseness).

Add an explicit verification step to the KV setup and dev-server preview workflows — e.g., confirm the namespace is bound or that the preview endpoint returns 200 before proceeding (workflow_clarity).

Either provide the referenced kv-storage.md as a bundle file or remove the dangling reference, and consider splitting the longer language-specific recipes into one-level-deep reference files (progressive_disclosure).

Dimension	Reasoning	Score
Conciseness	The body is mostly lean (executable snippets, tree diagrams, no condescending concept explanations), but the identical frontend block (index.html / style.css / script.js) is repeated across roughly six sections and the top blockquote warnings are somewhat verbose, so it could be tightened rather than earning the every-token-earns-its-place anchor at 3.	2 / 3
Actionability	Provides concrete, executable code for Go/Gin, Flask, FastAPI, the KV counter, and Express plus specific commands (`edgeone makers dev`) and file-path route conventions, matching the fully-executable/copy-paste-ready anchor; the undefined Go handler stubs are acceptable for scaffolding templates.	3 / 3
Workflow Clarity	Sequences are present (the KV setup steps 1-5 and the dev-server preview workflow), but neither includes explicit validation or verification checkpoints, which matches the 'steps listed but validation gaps' anchor and is below the explicit-checkpoint anchor at 3.	2 / 3
Progressive Disclosure	Sections are well-organized with clear headers, but all content lives inline in SKILL.md and the one signaled reference ([kv-storage.md](kv-storage.md)) points to a file that does not exist in the bundle (no references/scripts/assets dirs), so it is better than a monolithic wall but not the well-signaled one-level-deep reference anchor at 3.	2 / 3
	Total	9 / 12 Passed

Description

82%

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 specific and well-scoped to the EdgeOne Makers platform with good natural trigger terms, but it omits an explicit 'Use when' trigger clause, capping completeness. Adding a usage-trigger sentence would raise it to fully explicit.

Dimension	Reasoning	Score
Specificity	Names concrete deliverables ("Project structure templates and scaffolding recipes") and enumerates four specific app categories (full-stack apps, static sites, API services, AI agent projects), matching the 'lists multiple specific concrete items' anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Clearly states what the skill provides, but lacks any "Use when..." clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2 rather than reaching the explicit what-and-when anchor at 3.	2 / 3
Trigger Term Quality	Includes natural terms a user would say — "full-stack apps", "static sites", "API services", "AI agent projects" — alongside the platform name "EdgeOne Makers", giving good coverage of common project-type phrasings rather than only jargon.	3 / 3
Distinctiveness Conflict Risk	The platform-specific scope ("EdgeOne Makers applications") gives it a clear niche unlikely to trigger for unrelated scaffolding skills, matching the 'clear niche with distinct triggers' anchor; it is well above the generic overlap anchor at 2.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: TencentEdgeOne/edgeone-makers-tools
Path: skills/makers-recipes/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.