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 its scope, technology stack, and trigger conditions. It uses specific, natural terminology that developers would use when seeking authentication help in Next.js, and the explicit 'Use when...' clause with multiple scenarios makes it easy for Claude to select appropriately. The description is concise yet comprehensive, covering the key capabilities without unnecessary verbosity.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: authentication implementation patterns, protected routes, session management in Server Components/Actions, OAuth provider configuration, role-based access control, and sign-in/sign-out flows.

3 / 3

Completeness

Clearly answers both 'what' (authentication implementation patterns for Next.js 15+ App Router using Auth.js 5) and 'when' with an explicit 'Use when...' clause listing six specific trigger scenarios.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'authentication', 'Auth.js', 'NextAuth.js', 'protected routes', 'sessions', 'OAuth providers', 'role-based access control', 'sign-in/sign-out', 'Next.js', 'App Router'. These are all terms developers naturally use when seeking auth help.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive due to the specific technology stack (Next.js 15+ App Router, Auth.js 5/NextAuth.js) and focused domain (authentication). The combination of framework version, library, and auth-specific actions makes it very unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Implementation

85%

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, highly actionable skill with clear sequential workflow and good progressive disclosure through referenced files. Its main weakness is verbosity—the Examples section substantially duplicates patterns already shown in the Instructions, and some best practices state things Claude already knows. Trimming the redundant examples and obvious advice would make this significantly more token-efficient.

Suggestions

Remove or consolidate the Examples section, as Examples 1-3 closely duplicate code already shown in Instructions steps 6, 9, and 7 respectively—instead, make the instruction examples slightly more complete if needed.

Trim best practices to only non-obvious, Auth.js-specific guidance—remove generic advice like 'Never hardcode secrets', 'Use HTTPS in production', and 'Validate all user input' that Claude already knows.

DimensionReasoningScore

Conciseness

The skill is fairly comprehensive but includes some redundancy—the Examples section largely repeats patterns already shown in the Instructions (e.g., protected dashboard, role-based access, secure server actions are all demonstrated twice). The best practices list also contains some items Claude would already know (e.g., 'Never hardcode secrets', 'Use HTTPS in production'). Could be tightened significantly.

2 / 3

Actionability

All code examples are fully executable TypeScript/TSX with correct imports, file paths, and copy-paste ready patterns. The skill provides specific commands (npm install, openssl), exact file locations, and complete implementations rather than pseudocode.

3 / 3

Workflow Clarity

The 10-step numbered workflow provides a clear sequence from installation through to type extensions. Validation is addressed through the constraints/warnings section with explicit ❌/✅ patterns showing common mistakes and corrections. The middleware step includes proper route matching logic and the security considerations section serves as a verification checklist.

3 / 3

Progressive Disclosure

The skill provides a clear overview and complete working patterns inline, then references four specific supplementary files for deeper topics (adapters, providers, database sessions, testing). References are one level deep and clearly signaled with descriptive labels.

3 / 3

Total

11

/

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