response-transformer
Response Transformer - Auto-activating skill for API Integration. Triggers on: response transformer, response transformer Part of the API Integration skill category.
29
Quality
0%
Does it follow best practices?
Impact
76%
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/response-transformer/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 severely lacking across all dimensions. It provides no concrete actions, no natural trigger terms users would say, and no guidance on when to use the skill. The description appears to be auto-generated boilerplate without meaningful content about what 'Response Transformer' actually does.
Suggestions
Add specific concrete actions describing what the skill does (e.g., 'Transforms API responses into different formats, maps response fields, handles JSON/XML conversion, normalizes data structures').
Include a 'Use when...' clause with natural trigger terms (e.g., 'Use when the user needs to transform, convert, or reformat API responses, or when working with response mapping, data normalization, or format conversion').
Remove the redundant 'Triggers on: response transformer, response transformer' and replace with meaningful trigger scenarios that distinguish this from other API-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Auto-activating skill for API Integration' without describing any concrete actions. It does not explain what the skill actually does - no verbs describing capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no use cases or scenarios provided). The 'Triggers on' line is redundant and uninformative. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'response transformer' repeated twice, which is technical jargon. Missing natural user terms like 'transform API response', 'convert response format', 'parse API data', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'API Integration' is extremely generic and could conflict with many other API-related skills. Without specific capabilities or use cases, there's no clear niche defined. | 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 essentially a placeholder template with no actual content. It describes what a response transformer skill would do without providing any actual guidance, code, or instructions for response transformation. The entire document is meta-commentary about the skill rather than the skill itself.
Suggestions
Add concrete code examples showing how to transform API responses (e.g., mapping fields, normalizing data structures, handling different response formats)
Define what 'response transformer' actually means in this context and provide specific transformation patterns (JSON to JSON, XML to JSON, error normalization, etc.)
Include at least one complete, executable example with input response and expected transformed output
Remove all generic capability claims and replace with actual implementation guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler text that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless without specifics. The entire skill could be reduced to nothing because it contains no actual instructions. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no examples of actual response transformation. The 'Capabilities' section describes what it claims to do but never actually does it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. The skill mentions 'step-by-step guidance' but provides none. There are no steps, no sequence, and no validation checkpoints for any process. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no actual content to organize. There are no references to detailed materials, no structure beyond generic headings, and nothing pointing to where real information might be found. | 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.