backend-node

Node Developer Agent. Node.js/TypeScript 기반 백엔드 개발을 담당합니다. NestJS, Express, Prisma 전문.

Quality

27%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/backend-node/SKILL.md

Quality

Discovery

32%

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 identifies a clear technology stack but lacks actionable specificity about what tasks it performs and completely omits guidance on when Claude should use it. The Korean language mixed with English technical terms is acceptable, but the description reads more like a job title than a functional skill description.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Node.js APIs, NestJS modules, Express routes, Prisma schemas, or TypeScript backend code'

List specific concrete actions such as 'Creates REST APIs, configures database connections with Prisma, sets up NestJS modules and controllers, handles Express middleware'

Include common user terms and file extensions like 'API development', 'server-side code', '.ts files', 'ORM', 'database queries' to improve trigger term coverage

Dimension	Reasoning	Score
Specificity	Names the domain (Node.js/TypeScript backend development) and mentions specific technologies (NestJS, Express, Prisma), but doesn't list concrete actions like 'create APIs', 'set up database schemas', or 'configure middleware'.	2 / 3
Completeness	Describes what domain it covers but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. The rubric caps completeness at 2 for missing this, and the 'what' is also weak.	1 / 3
Trigger Term Quality	Includes relevant technical keywords (Node.js, TypeScript, NestJS, Express, Prisma, backend) that users might mention, but missing common variations like 'API', 'server', 'REST', 'database', or file extensions like '.ts'.	2 / 3
Distinctiveness Conflict Risk	The specific technology stack (NestJS, Express, Prisma) provides some distinction, but 'backend development' is broad and could overlap with other backend-focused skills in Python, Go, or general TypeScript skills.	2 / 3
	Total	7 / 12 Passed

Implementation

22%

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

This skill content is essentially a role description rather than actionable guidance. It lists technologies and vague conventions but provides no executable code, concrete examples, or workflows that would help Claude perform Node.js/TypeScript backend development tasks. The content describes what the agent does rather than instructing how to do it.

Suggestions

Add executable code examples for common tasks (e.g., NestJS controller setup, Prisma schema definition, Express middleware pattern)

Include concrete TypeScript conventions with before/after code examples showing interface-first patterns and type guards

Define workflows for common operations like project setup, database migrations, or API endpoint creation with validation steps

Remove the trigger keywords section and replace with actionable quick-start guidance

Dimension	Reasoning	Score
Conciseness	The content is brief but lacks substance - it lists categories without providing actionable value. The trigger keywords section is unnecessary as Claude can infer relevance from context.	2 / 3
Actionability	No concrete code examples, commands, or executable guidance provided. The content only lists technologies and vague conventions like 'strict 모드 사용' without showing how to implement anything.	1 / 3
Workflow Clarity	No workflows, processes, or sequences defined. The skill provides no guidance on how to actually perform backend development tasks, set up projects, or handle common operations.	1 / 3
Progressive Disclosure	The content is organized into clear sections, but there are no references to detailed documentation, examples, or advanced guides. For a skill covering multiple frameworks, external references would be valuable.	2 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Repository: shaul1991/shaul-agents-plugin
Commit: 9242c58

Reviewed: 29 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.