SKILLEMALL.ai

AC nestjs-best-practices

NestJS best practices and architecture patterns for building production-ready applications. This skill should be used when writing, reviewing, or refactoring NestJS code to ensure proper patterns for modules, dependency injection, security, and performance.

trycompai/crm Agent Skills author: trycompai MIT 43 files body ≈ 1 097 tokens Open the sourcegithub.com↗ analyzed 6 d ago

NestJS best practices and architecture patterns for building production-ready applications.

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
99
Quality 40%
89
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: autoskills

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 1

    ✓ No critical or high findings

    Medium and low: 1
    • low Secrets in code secret-high-entropy-token rules/db-use-migrations.md:98
      High-entropy token-like string (may be an id, hash or a credential)
      export class Rena…000 implements MigrationInterface {

    Files scanned: 43. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 51/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 3 mutating operations with no state check
    • 100Tools and files. No external tools needed
    • 100Steps. 50 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1097 tokens

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +3Description length 257: enough signal without eating the budget
    • +4Structure: 16 headings
    • +3Step-by-step instructions: 50 items
    • +4Has examples (1 code blocks)
    • +4Reference files are cited in the instructions (3 of 42)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.