platform-backend

Server-side architecture and security — API design, error handling, validation, logging. Use when building APIs, server logic, or reviewing backend security.

1.06x

Quality

51%

Does it follow best practices?

Impact

99%

1.06x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

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

Quality

Discovery

67%

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 description provides a reasonable foundation with clear 'what' and 'when' clauses, earning full marks for completeness. However, it relies on category names rather than concrete actions, and the trigger terms could be expanded to include more natural user language and technology-specific keywords that would help Claude select this skill more precisely.

Suggestions

Add more specific concrete actions like 'Design RESTful endpoints', 'Implement authentication/authorization', 'Configure rate limiting', 'Set up structured logging'

Expand trigger terms to include common variations: 'REST API', 'endpoints', 'middleware', 'authentication', 'authorization', 'Express', 'FastAPI', or similar framework names

Dimension	Reasoning	Score
Specificity	Names the domain (server-side architecture) and lists some actions (API design, error handling, validation, logging), but these are more categories than concrete actions. Lacks specific verbs like 'implement', 'configure', or 'audit'.	2 / 3
Completeness	Clearly answers both what (API design, error handling, validation, logging) and when ('Use when building APIs, server logic, or reviewing backend security') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes relevant keywords like 'APIs', 'server logic', 'backend security' that users might say, but missing common variations like 'REST', 'endpoints', 'authentication', 'middleware', or 'Node/Express/Django'.	2 / 3
Distinctiveness Conflict Risk	Somewhat specific to backend/server work, but 'API design' and 'error handling' could overlap with general coding skills or frontend API consumption skills. The 'backend security' focus helps distinguish it.	2 / 3
	Total	9 / 12 Passed

Implementation

35%

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

This skill is a thin wrapper that delegates almost all substance to external rules files while providing only two abstract principles. The troubleshooting and examples sections are generic templates that don't add backend-specific value. For a skill about API design, error handling, validation, and logging, it lacks any concrete patterns, code examples, or actionable guidance.

Suggestions

Add concrete code examples for error handling patterns (e.g., guard clauses, error response formats, validation middleware)

Include specific API design patterns with executable snippets (request validation, response schemas, logging formats)

Replace generic troubleshooting section with backend-specific gotchas (common validation pitfalls, security anti-patterns)

Expand the two principles into actionable guidance with before/after code examples

Dimension	Reasoning	Score
Conciseness	The content is relatively lean but includes boilerplate sections (Troubleshooting, Examples) that add little value for Claude. The actual backend-specific guidance is minimal - just two principles and a reference to external rules.	2 / 3
Actionability	No concrete code examples, API patterns, validation snippets, or executable guidance. The principles are abstract ('throw early', 'never swallow errors') without showing how. The workflow is generic and not backend-specific.	1 / 3
Workflow Clarity	A 3-step workflow exists but it's generic meta-process (identify scope, apply rules, validate) rather than actual backend development workflow. No validation checkpoints for API design, error handling patterns, or security review steps.	2 / 3
Progressive Disclosure	References external rules via [rules/_sections.md] which is appropriate, but the SKILL.md itself lacks substantive overview content. The reference is one-level deep but the main file doesn't provide enough context about what those rules contain.	2 / 3
	Total	7 / 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
metadata_field	'metadata' should map string keys to string values	Warning

	Total	10 / 11 Passed

Repository: ravnhq/ai-toolkit
Commit: 7b466be

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