Name: backend
Rating: 68 (1 reviews)
Author: redis

backend

NestJS backend development patterns for the RedisInsight API: module structure, services, controllers, DTOs, dependency injection, and error handling. Use when editing any file under redisinsight/api/**, writing or modifying NestJS modules, controllers, services, DTOs, providers, or when the user mentions the backend, API, or NestJS.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

75%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 content is a well-organized, mostly executable NestJS patterns reference with concrete code and a useful checklist. Its main weakness is the absence of progressive disclosure — all content lives in one ~240-line file with no external references to offload detail.

Suggestions

Trim generic platitudes (e.g., 'Separate concerns', 'Apply proper error handling') in the Architecture section to tighten conciseness toward a leaner token budget.

Add a concrete runnable example for the Redis Integration section, which is currently only bullet hints, to lift actionability.

Move the full folder-structure tree and/or the custom-exception template into a references/ file and link to it from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient — bullet lists and focused code examples that assume Claude's competence — with only minor over-explanation such as obvious maxims like 'Separate concerns' and 'Apply proper error handling'; not a 5 because a few generic platitudes remain.	4 / 5
Actionability	Provides concrete executable code (DI constructor pattern, custom exception class, constants object) and specific decorator/file-naming lists, but some sections (e.g., Redis Integration) are bullet-only hints without runnable detail, keeping it at 4 rather than 5.	4 / 5
Workflow Clarity	As a patterns reference it has a clear closing checklist and well-ordered sections, and no destructive/batch operations trigger the validation cap; it is not 5 because there are no explicit multi-step workflows with validation checkpoints, only reference structure.	4 / 5
Progressive Disclosure	The body is well-structured with clear section headers and inline content that is mostly appropriately placed, but with no bundle files present it is a monolithic single file over 50 lines with no one-level-deep references, so it fits 'good structure, minor organization gaps' rather than the 5 anchor.	4 / 5
	Total	16 / 20 Passed

Description

87%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 strong: it clearly states what the skill covers and gives explicit, concrete 'Use when...' triggers scoped to a distinct NestJS/RedisInsight niche. Minor room for improvement only in adding a few more natural synonyms.

Dimension	Reasoning	Score
Specificity	Lists several concrete pattern areas ('module structure, services, controllers, DTOs, dependency injection, and error handling') rather than vague language, with only minor gaps in coverage, fitting the 'several specific actions' anchor rather than the fully comprehensive anchor at 5.	4 / 5
Completeness	Explicitly answers both 'what' (NestJS backend development patterns and the enumerated areas) and 'when' with a concrete 'Use when...' clause and trigger phrases, matching the 5 anchor; it is not the 4 anchor because the 'when' is explicit and specific, not weakly implied.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('the backend, API, or NestJS', 'editing any file under redisinsight/api/**') plus specific artifacts (modules, controllers, services, DTOs, providers), but a few common synonyms are missing, so it sits at 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to NestJS/RedisInsight API with distinct triggers (redisinsight/api/**, NestJS-specific artifacts), giving a clear niche with minimal conflict risk, matching the 5 anchor.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: redis/RedisInsight
Path: .ai/skills/backend/SKILL.md
Commit: 6029714

Reviewed: 1 day 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.