mongoose-starter
Scaffold a Mongoose 8.x project with TypeScript, schemas, models, virtuals, instance/static methods, hooks (pre/post), discriminators, population, and connection management.
73
64%
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 ./database/mongoose-starter/SKILL.mdQuality
Discovery
50%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 excels at specificity by listing comprehensive Mongoose features and has a clear distinctive niche. However, it completely lacks trigger guidance ('Use when...'), which is critical for Claude to know when to select this skill. The technical terminology is accurate but could benefit from more natural user-facing keywords.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Mongoose setup', 'MongoDB schema', 'Node.js database models', or 'ODM configuration'
Include natural language variations users might say, such as 'MongoDB object modeling', 'database layer setup', or 'Node.js MongoDB integration'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Scaffold a Mongoose 8.x project with TypeScript, schemas, models, virtuals, instance/static methods, hooks (pre/post), discriminators, population, and connection management.' This comprehensively covers the domain with specific technical capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' 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 like 'Mongoose', 'TypeScript', 'schemas', 'models', 'hooks' that users might say, but these are fairly technical. Missing more natural variations like 'MongoDB ODM', 'database models', or 'Node.js database setup'. | 2 / 3 |
Distinctiveness Conflict Risk | Very clear niche with 'Mongoose 8.x' and 'TypeScript' as distinct identifiers. Unlikely to conflict with other database or Node.js skills due to the specific technology stack mentioned. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
79%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, actionable Mongoose starter skill with excellent executable code examples covering all major features (schemas, hooks, discriminators, aggregation). The main weaknesses are the lack of explicit validation/verification steps in workflows and the monolithic structure that could benefit from progressive disclosure to separate reference files.
Suggestions
Add validation checkpoints to the Database Initialization section (e.g., verify index creation with `db.collection.getIndexes()`, confirm seed data with a count check)
Split detailed code examples into separate files (e.g., PATTERNS.md for discriminators/aggregation, MODELS.md for complete model examples) and keep SKILL.md as a concise overview with links
| 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 Mongoose or MongoDB are. | 3 / 3 |
Actionability | Fully executable TypeScript code throughout with complete, copy-paste ready examples. The connection management, model definitions, repository patterns, and aggregation pipelines are all production-ready implementations. | 3 / 3 |
Workflow Clarity | While the project structure and patterns are clear, there are no explicit validation checkpoints or feedback loops. The database initialization section lacks verification steps to confirm indexes were created or seeds ran successfully. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but this is a monolithic file with ~300 lines of code examples that could benefit from splitting into separate reference files (e.g., PATTERNS.md, EXAMPLES.md). Integration notes hint at external skills but don't provide clear navigation structure. | 2 / 3 |
Total | 10 / 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 | |
- Repository
- achreftlili/deep-dev-skills
- Commit
181fcbc
- 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.