status-code-recommender
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill status-code-recommenderStatus Code Recommender - Auto-activating skill for API Development. Triggers on: status code recommender, status code recommender Part of the API Development skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, consisting mainly of metadata labels rather than actual skill documentation. It fails to explain what the skill does, provides no concrete actions or capabilities, and the trigger terms are just the skill name duplicated. The description would be nearly useless for Claude to distinguish this skill from others in a large skill library.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Recommends appropriate HTTP status codes for API endpoints based on the operation type and expected responses.'
Include a 'Use when...' clause with natural trigger terms like 'HTTP status code', 'response code', 'REST API', '4xx/5xx errors', 'which status code should I use'.
Add specific examples of when to activate, such as 'Use when designing API responses, handling errors, or when the user asks about appropriate status codes for specific scenarios.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Status Code Recommender') without describing any concrete actions. It doesn't explain what the skill actually does - no verbs like 'recommends', 'suggests', 'analyzes', or specific capabilities are mentioned. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no explicit use-case guidance beyond the redundant trigger terms). Both components are essentially missing. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('status code recommender, status code recommender'). Missing natural user phrases like 'HTTP status', 'response code', '404', '500 error', 'which status code', 'REST API response'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Status Code Recommender' is somewhat specific to HTTP/API status codes, which provides some distinctiveness. However, the vague 'API Development' category could overlap with many other API-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no actual content. It repeatedly mentions 'status code recommender' without ever explaining what status codes are appropriate for which situations, providing no examples, decision criteria, or actionable guidance. The entire content could be replaced with a simple table of status codes and their use cases to be infinitely more useful.
Suggestions
Add a concrete reference table mapping common API scenarios to appropriate HTTP status codes (e.g., 'Resource created' → 201, 'Validation failed' → 400, 'Unauthorized' → 401)
Include a decision tree or flowchart for selecting status codes based on the operation type (GET/POST/PUT/DELETE) and outcome
Provide specific code examples showing how to return different status codes in common frameworks
Remove all generic boilerplate text ('provides automated assistance', 'follows best practices') and replace with actual status code recommendations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens without adding value. | 1 / 3 |
Actionability | There is zero concrete guidance - no actual status codes listed, no decision criteria, no code examples, no specific recommendations. The skill describes what it claims to do rather than actually doing it. | 1 / 3 |
Workflow Clarity | No workflow exists. There are no steps, no process for recommending status codes, no decision tree or criteria for selecting appropriate codes. The 'Capabilities' section lists vague promises without any actual procedure. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed resources. No references to HTTP status code documentation, no links to examples, and no organization of content by use case. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Reviewed
Table of Contents
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.