response-transformer
Response Transformer - Auto-activating skill for API Integration. Triggers on: response transformer, response transformer Part of the API Integration skill category.
29
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 essentially a placeholder with no substantive content. It repeats the skill name as its only trigger term, provides no concrete actions or capabilities, and fails to explain when Claude should select this skill. It would be nearly impossible for Claude to correctly choose this skill from a list of alternatives.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Transforms API response payloads by mapping fields, converting formats (JSON/XML/CSV), filtering data, and restructuring nested objects.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to transform, reshape, or convert API responses, parse response bodies, map response fields, or handle response data formatting.'
Differentiate from other API-related skills by specifying the exact niche, e.g., whether this handles response parsing vs. request building vs. authentication vs. error handling.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. 'Response Transformer' is a name, not a capability description. There are no specific actions like 'parse JSON responses', 'map fields', or 'convert formats' listed. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. The description only states the skill name, a redundant trigger, and a category label without explaining functionality or use cases. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'response transformer' repeated twice, which is not a natural phrase users would say. Missing natural terms like 'API response', 'transform data', 'parse response', 'map fields', 'convert JSON', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'API Integration' could overlap with many skills. Without specifying what kind of response transformation (format conversion, field mapping, error handling, etc.), it's indistinguishable from other API-related 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 that provides no actual content about response transformation. It contains only generic meta-descriptions of what it claims to do without any concrete instructions, code examples, or actionable guidance. It would need to be completely rewritten with actual response transformer implementation details to be useful.
Suggestions
Add concrete, executable code examples showing how to transform API responses (e.g., mapping fields, normalizing data structures, handling error responses)
Define a clear workflow for implementing response transformers, including validation steps for verifying transformed output matches expected schemas
Replace the generic 'Capabilities' and 'Example Triggers' sections with actual technical content such as common transformation patterns, middleware examples, and specific library usage
Include references to related detailed files (e.g., PATTERNS.md for common transformation patterns, EXAMPLES.md for real-world use cases) if the topic warrants more depth
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in vague, repetitive terms without providing any actual knowledge or instructions that Claude doesn't already know. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific steps, no examples of actual response transformation. Every section describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. The skill claims to provide 'step-by-step guidance' but contains no steps, no sequence, and no validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic placeholder with no meaningful structure, no references to detailed materials, and no navigation to related resources despite mentioning related skills. | 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.