expressjs-project-starter
Scaffold a production-ready Express 5.x API with TypeScript, layered architecture, Zod validation, and robust error handling.
Install with Tessl CLI
npx tessl i github:achreftlili/deep-dev-skills --skill expressjs-project-starter74
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 specific technology stack (Express 5.x, TypeScript, Zod) which provides moderate specificity, but lacks explicit trigger guidance for when Claude should use this skill. The absence of a 'Use when...' clause significantly weakens its utility for skill selection among many options.
Suggestions
Add a 'Use when...' clause with trigger terms like 'create Express API', 'scaffold Node.js backend', 'new REST API project', 'TypeScript server setup'
Include common user phrases and variations such as 'REST API', 'backend service', 'Node.js API', 'web server'
Expand specific actions beyond 'scaffold' to include concrete capabilities like 'generate route handlers, configure middleware, set up validation schemas, create error handlers'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Express 5.x API) and some specific elements (TypeScript, layered architecture, Zod validation, error handling), but 'scaffold' is a single action rather than multiple concrete actions. Could list more specific capabilities like 'generate routes, configure middleware, set up database connections'. | 2 / 3 |
Completeness | Describes what it does (scaffold an Express API with specific features) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'Express', 'TypeScript', 'Zod', 'API' that users might say, but missing common variations like 'REST API', 'backend', 'server', 'Node.js', 'web service', or 'create API'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Express 5.x, TypeScript, and Zod provides some distinctiveness, but could overlap with general Node.js scaffolding skills, TypeScript project setup skills, or generic API creation skills without clearer boundaries. | 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 that provides comprehensive, actionable guidance for scaffolding an Express.js API. The code examples are complete and production-ready, conventions are clearly stated, and the workflow is logical. The main weakness is that the extensive inline content could benefit from splitting advanced topics (auth, database integration, Docker) into separate referenced files.
Suggestions
Consider extracting Integration Notes topics (Database, Auth, Docker, Testing) into separate referenced files like INTEGRATIONS.md or DATABASE.md for better progressive disclosure
Add a brief validation step after scaffold (e.g., 'Verify structure: ls -la src/' or 'Run type check: pnpm tsc --noEmit') to confirm successful setup
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information without explaining basic concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Fully executable code throughout with copy-paste ready examples for every component. The scaffold command, all TypeScript files, and common commands are complete and immediately usable. | 3 / 3 |
Workflow Clarity | Clear sequential workflow from scaffold command through project structure to first steps. The 'First Steps After Scaffold' section provides explicit numbered steps, and the structure naturally guides through the layered architecture. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is monolithic with all patterns inline. The Integration Notes section could reference separate files for database setup, auth patterns, and Docker configuration rather than brief inline mentions. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Reviewed
Table of Contents
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.