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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill error-mapping-helperOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is severely lacking across all dimensions. It provides only a name and category without explaining what the skill does, when to use it, or what specific capabilities it offers. The trigger terms are just the skill name repeated, providing no useful matching criteria for skill selection.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Maps API error responses to user-friendly messages, translates HTTP status codes, creates error handling documentation').
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when handling API errors, translating error codes, mapping HTTP status codes to messages, or creating error response documentation').
Define the specific scope to distinguish from other API-related skills (e.g., specify which APIs, what types of error mapping, what output formats).
| 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's no explanation of what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There's no explanation of capabilities and no meaningful usage guidance beyond the redundant trigger phrase. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'error mapping helper' repeated twice, which is the skill's own name rather than natural keywords users would say. Missing terms like 'API errors', 'error codes', 'status codes', 'error handling', etc. | 1 / 3 |
Distinctiveness Conflict Risk | 'API Integration' is extremely broad and could conflict with many other skills. Without specific actions or clear scope, this could trigger inappropriately for any API-related task. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content about error mapping. It contains only generic placeholder text that could apply to any skill topic. There is no actionable guidance, no code, no examples, and no real information about how to map errors in API integrations.
Suggestions
Add concrete code examples showing how to map API errors to application-specific error types (e.g., mapping HTTP status codes to domain exceptions)
Include a specific error mapping table or pattern showing common API errors and their recommended mappings
Provide executable code demonstrating error transformation, such as converting third-party API error responses to a standardized internal format
Remove all generic boilerplate text ('provides automated assistance', 'follows industry best practices') and replace with actual technical content
| 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 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 flat, uninformative structure with no references to detailed materials, no examples to link to, and no organization beyond generic section headers. | 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.