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 that names the skill and its category but provides no substantive information about what it does or when to use it. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance, making it nearly impossible for Claude to correctly select this skill from a pool of alternatives.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Transforms, maps, and reshapes API response payloads into desired data formats, handles JSON/XML conversion, extracts nested fields, and normalizes response structures.'
Add an explicit 'Use when...' clause with natural trigger scenarios, e.g., 'Use when the user needs to transform API responses, convert response formats, extract data from API payloads, or reshape JSON/XML output.'
Include natural keyword variations users might actually say, such as 'API response', 'transform response', 'parse API output', 'map response fields', 'convert JSON', 'response mapping', 'data transformation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('API Integration') and a concept ('Response Transformer') but provides no concrete actions. There is no indication of what specific operations this skill performs—no verbs describing capabilities like 'parse', 'transform', 'map', or 'convert'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and the 'when' clause is essentially just the skill name repeated. There is no explicit 'Use when...' guidance with meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'response transformer' repeated twice. These are narrow technical jargon and miss natural variations users might say such as 'transform API response', 'map response data', 'convert response format', 'parse API output', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to be distinctive. 'API Integration' is a broad category, and 'Response Transformer' without specifics could overlap with many API-related skills. Nothing clearly carves out a unique niche. | 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 actionable content whatsoever. It consists entirely of generic boilerplate that could apply to any topic—there is no domain-specific knowledge about response transformation, API integration patterns, or any concrete implementation guidance. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples showing common response transformation patterns (e.g., mapping API responses to internal schemas, normalizing error formats, paginated response handling).
Define a clear workflow for implementing a response transformer, including steps like: identify source schema, define target schema, write mapping logic, validate output, handle edge cases/errors.
Remove all generic filler text ('This skill provides automated assistance...') and replace with specific, actionable instructions that assume Claude's competence.
If the topic warrants depth, split into a concise SKILL.md overview with references to supporting files (e.g., PATTERNS.md for common transformation patterns, EXAMPLES.md for worked examples).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no domain-specific information, and every section restates the same vague concept ('response transformer') without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific steps, no examples of actual response transformation logic. The 'capabilities' section describes what the skill claims to do but never actually does it. | 1 / 3 |
Workflow Clarity | No workflow, sequence, or steps are provided. The skill mentions 'step-by-step guidance' as a capability but never delivers any steps, let alone validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no bundle files to support it. There is no meaningful content to disclose progressively. | 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.