Name: implement
Rating: 93.8 (1 reviews)
Author: AI-Unified-Process

implement

Implements use cases across a NestJS backend with Drizzle ORM over PostgreSQL and a Next.js App Router frontend wired to that API. Use when the user asks to "implement a use case", "build the API", "create a REST endpoint", "write the data access layer", "build the page", or mentions NestJS modules, controllers, providers, Drizzle queries, repositories, or a Next.js frontend calling a NestJS backend.

1.01x

Quality

96%

Does it follow best practices?

Impact

85%

1.01x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

The canonical home for this skill is ai-unified-process/aiup-nestjs-nextjs

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tightly written, highly actionable full-stack implementation guide with executable NestJS and Next.js examples, an explicit multi-step workflow with build/compile/contract validation checkpoints, and a correctly externalized layout-detection reference. Its only weakness is mild over-explanation where prose restates the inline code.

Suggestions

Trim the 'The rules this code demonstrates' subsections to the few rules that are not already obvious from the code (e.g. no findOne, global ValidationPipe), removing rationale that restates what the example shows.

De-duplicate the DO NOT list against the Backend/Frontend rules sections so each constraint appears in one place, or cross-reference instead of restating.

Collapse the two 'The rules this code demonstrates' blocks into a single shared rules list, since several points (await everything, relative fetch path) recur across backend and frontend.

Dimension	Reasoning	Score
Conciseness	The body is dense with genuinely project-specific, non-obvious knowledge (no 'findOne', .js suffix rule, route indirection, repository-ownership guidance) and avoids explaining basics, but the recurring 'The rules this code demonstrates' prose partly re-states what the inline code already shows and the DO NOT list overlaps the rules sections, placing it at level-4 'minor instances of over-explanation' rather than the level-5 'every token earns its place'.	4 / 5
Actionability	Provides complete, copy-paste-ready NestJS feature-module files (repository, response type, service, query DTO, controller, module) and a full Next.js page.tsx with real imports and .js suffixes, covering the common list-with-optional-filter case, matching the level-5 'fully executable, copy-paste ready, covers common cases' anchor.	5 / 5
Workflow Clarity	The 7-step Workflow is clearly sequenced with explicit validation checkpoints ('verifying it compiles', 'Verify the frontend builds', 'Confirm the backend and frontend agree on the JSON shape') plus a dedicated reconciliation branch, matching the level-5 'clear sequence with explicit validation steps' anchor rather than the level-4 'minor validation gaps' anchor.	5 / 5
Progressive Disclosure	Clear sectioned overview (Instructions, DO NOT, Workflow, Backend, Frontend, Resources) with one well-signaled one-level-deep reference to references/project-layout.md (verified to exist as a self-contained detection table), keeping worked examples inline and externalizing only the lookup that should be shared, matching the level-5 'clear overview, well-signaled one-level-deep references, easy navigation' anchor.	5 / 5
	Total	19 / 20 Passed

Description

100%Weight 40%Scale 1-5

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 is a strong, third-person statement that explicitly covers both what the skill does and when to use it, with concrete action verbs and natural trigger phrases spanning both halves of the stack. It is distinctive and unlikely to fire for the wrong sibling skill.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across both halves of the stack — 'build the API', 'create a REST endpoint', 'write the data access layer', 'build the page' — naming the NestJS/Drizzle/PostgreSQL backend and Next.js frontend domain comprehensively, matching the level-5 anchor rather than the level-4 'minor gaps' anchor.	5 / 5
Completeness	Explicitly answers both 'what' ('Implements use cases across a NestJS backend ... and a Next.js App Router frontend') and 'when' ('Use when the user asks to ...') with concrete trigger phrases, matching the level-5 anchor exactly; it is not the level-4 anchor because the 'when' is fully explicit with multiple named triggers.	5 / 5
Trigger Term Quality	Provides comprehensive natural phrases users would actually say ('implement a use case', 'build the API', 'create a REST endpoint', 'write the data access layer', 'build the page') plus synonym-style mentions of NestJS modules/controllers/providers and Drizzle queries, fitting the level-5 'comprehensive coverage including synonyms' anchor.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — full-stack use-case implementation across a NestJS+Drizzle backend and Next.js frontend — with distinct triggers and minimal conflict risk, since adjacent concerns (tests, migrations) are owned by other named skills; this fits the level-5 'clear niche, minimal conflict' anchor rather than the level-4 'minor overlap' anchor.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: AI-Unified-Process/marketplace
Path: aiup-nestjs-nextjs/skills/implement/SKILL.md
Commit: c3a5da3

Reviewed: 6 days 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.