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 'Use when' guidance, and it is indistinguishable from other API-related skills.
Suggestions
Add specific concrete actions, e.g., 'Maps API error codes to standardized error responses, generates error handling middleware, and creates error code lookup tables for REST and GraphQL 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 errors, create error response schemas, or build error handling logic for API integrations.'
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 responses', 'error handling'.
| 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 skill from other API-related skills. 'Error mapping' could overlap with error handling, API debugging, logging, or response formatting skills. No clear niche is established. | 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 actual technical content. It contains only generic boilerplate descriptions that could apply to any skill topic, with no concrete guidance on error mapping, no code examples, no API error code patterns, and no actionable instructions whatsoever. It fails on every dimension of the rubric.
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) implement mapping function, 5) validate with test cases.
Include specific, copy-paste-ready code for common error mapping patterns (e.g., mapping Stripe/Twilio/AWS error codes to standardized internal errors).
Remove all generic boilerplate ('Provides step-by-step guidance', 'Follows industry best practices') and replace with actual technical content that Claude doesn't already know.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no specific technical content about error mapping, and pads extensively with generic phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' without any substance. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code examples, no specific error mapping patterns, no API error code mappings, no commands—just vague descriptions like 'Generates production-ready code and configurations' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill merely states it 'provides step-by-step guidance' without actually containing any steps. | 1 / 3 |
Progressive Disclosure | No bundle files exist, no references to external documents, and the content itself is a monolithic block of generic placeholder text with no meaningful structure or navigation to deeper content. | 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
3a2d27d
- 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.