gin-project-starter

Scaffold and develop production-ready REST APIs using the Gin web framework with GORM, Swagger, and idiomatic Go patterns.

Quality

55%

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/gin-project-starter/SKILL.md

Quality

Discovery

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 clear technology stack and domain but lacks explicit trigger guidance for when Claude should select this skill. It provides moderate specificity through technology names but would benefit from concrete action verbs and a 'Use when...' clause to improve skill selection accuracy.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when building Go web services, creating REST endpoints with Gin, or setting up API projects with Swagger documentation'

Include common user terms and variations such as 'golang', 'web server', 'HTTP API', 'API routes', 'database models'

List more specific concrete actions like 'create CRUD endpoints', 'generate OpenAPI/Swagger docs', 'implement authentication middleware', 'define database models'

Dimension	Reasoning	Score
Specificity	Names the domain (REST APIs) and key technologies (Gin, GORM, Swagger, Go), but 'scaffold and develop' are somewhat generic actions. Lacks specific concrete actions like 'create endpoints', 'generate OpenAPI docs', 'implement middleware'.	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 'when' component at all.	1 / 3
Trigger Term Quality	Includes relevant technical terms (Gin, GORM, Swagger, REST APIs, Go) that users might mention, but missing common variations like 'web server', 'HTTP endpoints', 'API routes', 'database ORM', or 'golang'.	2 / 3
Distinctiveness Conflict Risk	The specific technology stack (Gin + GORM + Swagger) provides some distinctiveness, but 'REST APIs' and 'Go patterns' could overlap with other Go or API-related skills. The combination helps but isn't fully distinct.	2 / 3
	Total	7 / 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 highly actionable Gin project starter skill with excellent executable code examples and clear workflow guidance. The main weakness is its length - while comprehensive, the skill could benefit from splitting detailed code patterns into separate referenced files to improve token efficiency. The content assumes appropriate Go knowledge while providing project-specific conventions.

Suggestions

Extract the detailed code patterns (handler, middleware, repository, config) into a separate PATTERNS.md file and reference it from the main skill

Consider removing or condensing the graceful shutdown pattern as this is well-known Go idiom that Claude can generate without detailed examples

Add a brief 'Validation' section after scaffold steps to verify the setup works (e.g., expected output from healthz endpoint)

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some verbose sections. The extensive code examples are valuable but could be more condensed - for instance, the full handler implementation with all CRUD operations could reference a separate file. Some patterns like graceful shutdown are well-known to Claude.	2 / 3
Actionability	Excellent actionability with fully executable, copy-paste ready code throughout. Every pattern includes complete, working Go code with proper imports, struct definitions, and error handling. The scaffold commands and common commands sections are immediately usable.	3 / 3
Workflow Clarity	Clear sequential workflow in 'First Steps After Scaffold' section with numbered steps. The project structure is well-defined, and the relationship between layers (handler -> service -> repository) is explicit. Common commands provide clear validation steps.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but everything is in a single monolithic file. The extensive code examples (400+ lines) could benefit from being split into referenced files like PATTERNS.md or EXAMPLES.md. Integration notes hint at external concerns but don't link to separate docs.	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 (546 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.