go-chi-project-starter

Scaffold and develop production-ready REST APIs using the Chi v5 router with clean architecture, structured logging (slog), SQLX, and idiomatic Go patterns.

Quality

55%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./backend-go/go-chi-project-starter/SKILL.md

Quality

Content

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 highly actionable skill with excellent executable code examples covering the full stack of a Chi-based REST API. The workflow is clear and the patterns are production-ready. However, the skill would benefit from being more concise by removing explanations of concepts Claude already knows, and from better progressive disclosure by splitting detailed implementations into referenced files.

Suggestions

Remove or significantly trim the 'Integration Notes' section - explanations like 'why closures over structs' and 'SQLX over GORM' explain concepts Claude already understands

Split detailed implementations (full handler code, repository code, middleware code) into separate referenced files like HANDLERS.md, REPOSITORY.md, keeping only essential patterns in the main skill

Trim inline code comments that explain obvious Go patterns (e.g., '// Structured logger', '// Database', '// Router')

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some verbose sections that could be tightened. The extensive code examples are valuable but some explanatory comments within code and the 'Integration Notes' section contain information Claude likely already knows (e.g., explaining what closures are, why SQLX over GORM).	2 / 3
Actionability	Excellent actionability with fully executable, copy-paste ready code examples throughout. The scaffold command, project structure, complete handler implementations, middleware, repository patterns, and SQL migrations are all concrete and immediately usable.	3 / 3
Workflow Clarity	Clear sequential workflow in 'First Steps After Scaffold' section with numbered steps. The 'Common Commands' section provides explicit commands for each operation. Migration workflow includes both up and down commands with clear sequencing.	3 / 3
Progressive Disclosure	The skill is a monolithic document with all content inline rather than appropriately split across files. For a skill of this size (~500 lines), the detailed repository, handler, and middleware implementations could be referenced in separate files, with SKILL.md serving as an overview with quick-start essentials.	2 / 3
	Total	10 / 12 Passed

Description

32%

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 identifies a specific technology stack and domain but lacks explicit trigger guidance for when Claude should select this skill. It uses appropriate third-person voice and mentions concrete technologies, but the actions described are generic ('scaffold and develop') rather than specific capabilities. The absence of a 'Use when...' clause significantly weakens its utility for skill selection.

Suggestions

Add a 'Use when...' clause with trigger terms like 'Chi router', 'Go REST API', 'golang backend', 'HTTP server in Go'

Replace generic 'scaffold and develop' with specific actions like 'create route handlers', 'implement middleware chains', 'set up database connections', 'structure project layout'

Include common user phrasings like 'API server', 'web service', 'golang', 'backend service' to improve trigger term coverage

Dimension	Reasoning	Score
Specificity	Names the domain (REST APIs) and mentions specific technologies (Chi v5, slog, SQLX), but 'scaffold and develop' are somewhat generic actions. Lacks concrete specific actions like 'create endpoints', 'implement middleware', 'generate handlers'.	2 / 3
Completeness	Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance should cap completeness at 2, and this has no trigger guidance at all.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'REST APIs', 'Chi', 'Go', 'SQLX', but missing common variations users might say like 'API server', 'web service', 'HTTP endpoints', 'golang', or 'backend'.	2 / 3
Distinctiveness Conflict Risk	The specific technology stack (Chi v5, slog, SQLX) provides some distinctiveness, but 'REST APIs' and 'Go patterns' could overlap with other Go or API-related skills. Could conflict with generic Go development or other API framework skills.	2 / 3
	Total	7 / 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 (763 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: 4 months 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.