CtrlK
BlogDocsLog inGet started
Tessl Logo

giuseppe-trisciuoglio/developer-kit

Comprehensive developer toolkit providing reusable skills for Java/Spring Boot, TypeScript/NestJS/React/Next.js, Python, PHP, AWS CloudFormation, AI/RAG, DevOps, and more.

89

Quality

89%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Risky

Do not use without reviewing

Overview
Quality
Evals
Security
Files

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 an excellent skill description that clearly defines a specific technology stack integration pattern. It provides comprehensive trigger terms covering the full range of authentication scenarios, uses proper third-person voice, and includes an explicit 'Use when...' clause with detailed trigger conditions. The specificity of the technology combination (Better Auth + NestJS + Next.js + Drizzle ORM + PostgreSQL) makes it highly distinctive and unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: setting up Better Auth with NestJS, integrating Next.js App Router frontend, configuring Drizzle ORM schema, implementing social login (GitHub, Google), adding plugins (2FA, Organization, SSO, Magic Link, Passkey), implementing email/password authentication with session management, and creating protected routes and middleware.

3 / 3

Completeness

Clearly answers both 'what' (Better Auth integration patterns for NestJS/Next.js with Drizzle ORM and PostgreSQL) and 'when' with an explicit 'Use when...' clause listing multiple specific trigger scenarios.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'Better Auth', 'NestJS', 'Next.js', 'Drizzle ORM', 'PostgreSQL', 'social login', 'GitHub', 'Google', '2FA', 'Organization', 'SSO', 'Magic Link', 'Passkey', 'email/password authentication', 'session management', 'protected routes', 'middleware', 'App Router'. These are all terms a developer would naturally use when seeking help with this stack.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive due to the very specific technology combination (Better Auth + NestJS + Next.js + Drizzle ORM + PostgreSQL). The description carves out a clear niche that is unlikely to conflict with generic auth skills or generic NestJS/Next.js skills.

3 / 3

Total

12

/

12

Passed

Implementation

70%

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

This is a well-structured skill with excellent progressive disclosure and clear workflow sequencing with validation checkpoints. Its main weaknesses are some verbosity (redundant sections, generic advice Claude already knows) and incomplete actionability in certain steps where code is missing or potentially incorrect for the specific frameworks involved.

Suggestions

Remove or significantly trim the 'When to Use' section (it repeats the overview) and generic best practices Claude already knows (e.g., 'store secrets in .env', 'use HTTPS') to improve conciseness.

Add complete, executable code for Phase 2 Step 1 (Drizzle connection service) and verify that the NestJS auth controller code works correctly with Better Auth's handler API (Request/Response type compatibility).

Verify the Next.js middleware example matches Better Auth's actual client-side API pattern, as the current `auth((req) => {...})` pattern may not be accurate.

DimensionReasoningScore

Conciseness

The skill is mostly efficient but includes some unnecessary sections like 'When to Use' (which largely repeats the overview) and the 'Best Practices' section contains some generic advice Claude already knows (e.g., 'store secrets in .env', 'use HTTPS'). The overview and constraints sections have some redundancy.

2 / 3

Actionability

Provides executable code examples for several steps, but key parts are incomplete or vague—Phase 2 step 1 says 'Set up Drizzle connection service' without code, the auth controller handler may not work as shown (NestJS Request/Response types vs Node types), and the middleware example in Phase 3 uses a pattern that doesn't match Better Auth's actual API. Some code snippets may not be copy-paste ready.

2 / 3

Workflow Clarity

The 4-phase setup is clearly sequenced with explicit validation checkpoints after each phase (verify tables, test endpoint, test redirect, verify new tables after plugins). Includes a clear progression from database to backend to frontend to advanced features, with verification steps that catch errors early.

3 / 3

Progressive Disclosure

Excellent structure with a concise overview and quick start in the main file, with clear one-level-deep references to detailed guides (nestjs-setup.md, plugins.md, passkey.md, schema.md, etc.). References are well-signaled and organized by topic, making navigation easy.

3 / 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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

10

/

11

Passed

Reviewed

Table of Contents