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
Quality
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 description is essentially a placeholder with no substantive content. It provides only a skill name, a repeated trigger term, and a vague category label. The description completely fails to communicate what the skill does, when it should be used, or how it differs from other API-related skills.
Suggestions
Add specific concrete actions describing what the skill does, e.g., 'Maps API error codes to human-readable messages, creates error handling lookup tables, translates HTTP status codes to application-specific errors'
Add a 'Use when...' clause with natural trigger terms like 'error codes', 'API errors', 'error handling', 'status codes', 'error messages', 'exception mapping'
Define the specific scope to distinguish from other API skills, e.g., 'Use when the user needs to create or manage error code mappings, NOT for general API debugging or endpoint configuration'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Error Mapping Helper' is just a name, and 'API Integration' is a vague category. There are no specific capabilities like 'maps error codes to messages' or 'translates API errors to user-friendly responses'. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of functionality and no 'Use when...' clause or equivalent guidance for skill selection. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'error mapping helper' repeated twice, which is the skill name itself rather than natural user language. Users would more likely say 'map errors', 'handle API errors', 'error codes', or 'error messages'. | 1 / 3 |
Distinctiveness Conflict Risk | 'API Integration' is extremely generic and could conflict with many other API-related skills. Without specific triggers or clear scope definition, this skill could inappropriately activate for any API-related query. | 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 content is essentially a placeholder template with no actual instructional value. It describes what an error mapping helper skill should do without providing any concrete guidance, code examples, or actionable steps. The content fails on all dimensions by being verbose yet empty of substance.
Suggestions
Add concrete code examples showing how to map API errors to application-specific error types (e.g., mapping HTTP status codes to domain errors)
Include a specific workflow for implementing error mapping: identify error sources → define error taxonomy → create mapping functions → add validation
Provide executable code snippets for common error mapping patterns (e.g., REST API errors, webhook failures, OAuth errors)
Remove all generic boilerplate text and replace with actual error mapping techniques, patterns, and examples specific to API integration
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about error mapping. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific commands, no actual error mapping patterns or techniques. The content only describes what the skill claims to do without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The skill mentions 'step-by-step guidance' but provides none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to examples, and no structured navigation to additional resources. | 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
0c08951
- 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.