tessl-labs/mongoose-best-practices
Mongoose and MongoDB patterns — schema design, validation, indexes, virtuals,
99
99%
Does it follow best practices?
Impact
100%
1.11xAverage score across 5 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It provides specific technical capabilities, uses natural developer terminology, includes an explicit 'Use when...' clause with multiple trigger scenarios, and clearly distinguishes itself as MongoDB/Mongoose-specific rather than a generic database skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'schema design, validation, indexes, virtuals, middleware, population, lean queries, transactions, and pagination' - these are all concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (Mongoose/MongoDB patterns with specific capabilities listed) AND when ('Use when building or reviewing apps with MongoDB and Mongoose, when designing document schemas, or when migrating from SQL to MongoDB'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'MongoDB', 'Mongoose', 'document schemas', 'SQL to MongoDB', plus technical terms like 'indexes', 'virtuals', 'middleware' that developers naturally use when seeking help. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting specifically MongoDB and Mongoose - unlikely to conflict with general database skills or other ORM skills due to explicit technology naming and MongoDB-specific terminology like 'document schemas', 'population', 'lean queries'. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill document that demonstrates best practices for technical documentation. It uses the WRONG/RIGHT pattern consistently to show anti-patterns and solutions with executable code, maintains high token efficiency by assuming Claude's competence, and provides comprehensive coverage of Mongoose gotchas ordered by impact. The checklist and verifier references provide excellent progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is highly efficient, using WRONG/RIGHT patterns that immediately show the problem and solution without explaining what MongoDB or Mongoose is. Every section earns its place with concrete, actionable guidance. | 3 / 3 |
Actionability | All code examples are fully executable TypeScript with proper imports, realistic scenarios, and copy-paste ready patterns. The WRONG/RIGHT format makes it immediately clear what to do and what to avoid. | 3 / 3 |
Workflow Clarity | Multi-step processes like transactions include explicit validation (try/finally for session cleanup), error handling patterns (catching error code 11000), and clear sequencing. The checklist at the end provides a verification workflow. | 3 / 3 |
Progressive Disclosure | Content is well-organized with numbered sections ordered by impact, a comprehensive checklist for quick reference, and clear references to external Mongoose/MongoDB docs. Verifier references at the end provide appropriate one-level-deep navigation. | 3 / 3 |
Total | 12 / 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