Scaffold and develop high-performance REST APIs using the Fiber v2 web framework with GORM/SQLX, Express-inspired routing, and idiomatic Go patterns.
73
62%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backend-go/fiber-project-starter/SKILL.mdQuality
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 the technology stack (Fiber v2, GORM/SQLX, Go) but lacks explicit trigger guidance for when Claude should select this skill. The actions are somewhat vague ('scaffold and develop') rather than listing concrete capabilities, and it misses common user terminology variations.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Fiber framework', 'Go web API', 'golang REST', 'HTTP server in Go'
Replace vague 'scaffold and develop' with specific actions like 'create route handlers, configure middleware, set up database models, implement CRUD endpoints'
Include common user terminology variations: 'golang', 'web server', 'HTTP endpoints', 'backend API'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (REST APIs, Fiber v2) and mentions some technologies (GORM/SQLX, Express-inspired routing), but 'scaffold and develop' is somewhat vague and doesn't list multiple concrete actions like 'create endpoints, handle middleware, configure database connections'. | 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 caps completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'REST APIs', 'Fiber', 'GORM', 'SQLX', 'Go', but misses common user variations like 'web server', 'HTTP endpoints', 'API routes', 'golang', or 'backend service'. | 2 / 3 |
Distinctiveness Conflict Risk | Fiber v2 and GORM/SQLX provide some specificity, but 'REST APIs' and 'Go patterns' could overlap with other Go web framework skills or general API development skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill with excellent actionability and conciseness. The code examples are complete, executable, and follow idiomatic Go patterns. The main weakness is the monolithic structure - the extensive code examples could be better organized across multiple files with the main SKILL.md serving as an overview with references.
Suggestions
Consider splitting the Essential Patterns section into separate files (e.g., HANDLERS.md, MIDDLEWARE.md, DATABASE.md) and referencing them from the main skill
Move Integration Notes to a separate INTEGRATION.md file to keep the main skill focused on getting started quickly
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing executable code without explaining basic concepts Claude already knows. Every section serves a purpose with no padding or unnecessary explanations about what Go, REST APIs, or web frameworks are. | 3 / 3 |
Actionability | Fully executable code throughout - scaffold commands are copy-paste ready, all Go code examples are complete and runnable, and common commands section provides exact CLI invocations. No pseudocode or vague instructions. | 3 / 3 |
Workflow Clarity | Clear sequenced workflow in 'First Steps After Scaffold' section with numbered steps. The project structure is explicit, and the scaffold command shows exact dependency installation order. Common commands section provides clear operational guidance. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but this is a monolithic file with ~400 lines of code examples that could benefit from splitting into separate reference files (e.g., HANDLERS.md, DATABASE.md, MIDDLEWARE.md). The Integration Notes section at the end could be a separate file. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
81%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 (528 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 | |
181fcbc
Table of Contents
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.