echo-project-starter

Scaffold and develop production-ready REST APIs using the Echo v4 web framework with custom validation, JWT auth, Swagger, and idiomatic Go patterns.

Quality

72%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./backend-go/echo-project-starter/SKILL.md

Quality

Discovery

67%

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

This description excels at specificity and distinctiveness by clearly naming the Echo v4 framework, Go language, and specific features like JWT auth and Swagger. However, it lacks an explicit 'Use when...' clause which limits Claude's ability to know when to select this skill, and could benefit from additional trigger term variations that users might naturally say.

Suggestions

Add a 'Use when...' clause with trigger terms like 'when building Go web APIs', 'when the user mentions Echo framework', 'when setting up REST endpoints in Golang'

Include common term variations such as 'Golang', 'API development', 'web server', 'API documentation', 'authentication middleware'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Scaffold and develop production-ready REST APIs' with specific technologies: 'Echo v4 web framework', 'custom validation', 'JWT auth', 'Swagger', and 'idiomatic Go patterns'.	3 / 3
Completeness	Clearly answers 'what' (scaffold/develop REST APIs with specific features), but lacks an explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill.	2 / 3
Trigger Term Quality	Contains good technical keywords like 'REST APIs', 'Echo v4', 'JWT auth', 'Swagger', 'Go' that developers would use, but missing common variations like 'API development', 'authentication', 'API docs', 'Golang', or 'web server'.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive with clear niche: specifically Echo v4 framework for Go REST APIs. Unlikely to conflict with generic API skills or other language/framework combinations due to explicit technology stack.	3 / 3
	Total	10 / 12 Passed

Implementation

77%

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

This is a strong, highly actionable skill for scaffolding Echo v4 REST APIs with comprehensive, executable code examples covering the full stack from main.go to service layer. The main weakness is its length - at 400+ lines, it could benefit from splitting detailed implementations into separate reference files while keeping SKILL.md as a leaner overview with quick-start essentials.

Suggestions

Move detailed code implementations (full handler, service, repository examples) to separate reference files like HANDLERS.md, SERVICES.md, and keep only essential patterns in the main skill

Add explicit references to external files: '**Full handler examples**: See [HANDLERS.md](HANDLERS.md)' to improve progressive disclosure

Consider trimming the Integration Notes section or moving it to a separate ADVANCED.md file

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some verbose sections. The extensive code examples are valuable but could be more condensed - the full service layer implementation and handler code could be trimmed or moved to separate reference files.	2 / 3
Actionability	Excellent actionability with fully executable, copy-paste ready code examples throughout. The scaffold command, project structure, and all code patterns are concrete and immediately usable.	3 / 3
Workflow Clarity	Clear sequential workflow in 'First Steps After Scaffold' section with numbered steps. Common commands are well-organized. The scaffold-to-running-server path is unambiguous with explicit validation (curl healthz).	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but the skill is monolithic - extensive code examples for service layer, handlers, and middleware could be split into separate reference files. No external file references are provided for advanced topics.	2 / 3
	Total	10 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (526 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: achreftlili/deep-dev-skills
Commit: 181fcbc

Reviewed: about 1 month 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.