error-mapping-helper
Error Mapping Helper - Auto-activating skill for API Integration. Triggers on: error mapping helper, error mapping helper Part of the API Integration skill category.
33
0%
Does it follow best practices?
Impact
96%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/16-api-integration/error-mapping-helper/SKILL.mdQuality
Discovery
0%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 extremely weak description that appears to be auto-generated boilerplate with no meaningful content. It fails on all dimensions: no concrete actions are described, trigger terms are just the skill name duplicated, there is no 'when to use' guidance, and it lacks any distinguishing detail that would help Claude select it appropriately from a pool of skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Maps API error codes to standardized error responses, generates error translation tables, and creates error handling middleware for REST APIs.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to map HTTP status codes, translate API error responses, create error code lookup tables, or standardize error handling across API endpoints.'
Remove the duplicated trigger term and replace with diverse natural language variations users would actually say, such as 'error codes', 'API errors', 'status code mapping', 'error response handling', 'error translation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. 'Error Mapping Helper' is a label, not a description of what it does. There are no specific capabilities listed like 'maps API error codes to user-friendly messages' or 'generates error handling middleware'. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. The description only states a category ('API Integration') and repeats the skill name as triggers, with no explicit 'Use when...' clause or functional description. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('error mapping helper, error mapping helper'). No natural user language is included—users would more likely say things like 'map error codes', 'handle API errors', 'error response mapping', or 'translate HTTP status codes'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to distinguish this from any other API-related or error-handling skill. 'Error Mapping Helper' for 'API Integration' could overlap with error handling, API debugging, status code reference, or exception handling skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty placeholder with no substantive content. It contains only generic boilerplate text that repeats the skill name without providing any actual guidance on error mapping, API error codes, mapping strategies, or integration patterns. It fails on every dimension because it teaches Claude nothing actionable.
Suggestions
Add concrete error mapping examples showing how to map HTTP status codes or third-party API errors to internal application error types, with executable code snippets.
Define a clear workflow for creating error mappings: e.g., 1) identify source API error codes, 2) define internal error schema, 3) create mapping table, 4) validate coverage of all error cases.
Include specific patterns such as error code lookup tables, error transformation functions, and retry logic for transient errors with copy-paste ready code.
Replace all generic boilerplate sections ('Purpose', 'When to Use', 'Example Triggers') with actual technical content about error mapping strategies, common pitfalls, and validation approaches.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the phrase 'error mapping helper' excessively, and provides zero substantive information about how to actually perform error mapping. | 1 / 3 |
Actionability | There are no concrete code examples, commands, specific error mapping patterns, or executable guidance of any kind. Every section is vague and abstract, describing what the skill supposedly does rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic placeholder text with no references to detailed materials, no links to related files, and no meaningful structural organization beyond boilerplate headings. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
c8a915c
- 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.