response-transformer
Response Transformer - Auto-activating skill for API Integration. Triggers on: response transformer, response transformer Part of the API Integration skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill response-transformerOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is severely lacking across all dimensions. It provides no concrete actions, uses repetitive technical jargon as triggers, fails to explain what the skill does or when to use it, and is too generic to distinguish from other API-related skills. The description appears to be auto-generated boilerplate rather than a thoughtful explanation of the skill's purpose.
Suggestions
Add specific concrete actions describing what 'response transformation' means (e.g., 'Converts API responses between JSON, XML, and CSV formats, extracts nested data fields, maps response schemas')
Add a 'Use when...' clause with natural trigger terms like 'convert API response', 'transform JSON', 'parse response data', 'map API output', 'reformat response'
Clarify the specific niche this skill serves to distinguish it from general API skills (e.g., specify which APIs, what types of transformations, what output formats)
| 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 explicit use cases or scenarios). 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 broad and could conflict with many other API-related skills. There's nothing distinctive about what specific type of response transformation this handles. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no substantive content. It describes what a response transformer skill would do without providing any actual guidance, code examples, or actionable information about transforming API responses. The content fails all dimensions by being entirely meta-description rather than instruction.
Suggestions
Add concrete code examples showing how to transform API responses (e.g., mapping fields, handling errors, normalizing data structures)
Define what 'response transformer' means in this context and provide specific patterns (e.g., adapter pattern, data normalization, error mapping)
Include at least one complete, executable example with input/output showing a transformation
Remove the generic 'Example Triggers' and 'Capabilities' sections and replace with actual implementation guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about response transformers. Every section describes what the skill does abstractly rather than providing concrete guidance. | 1 / 3 |
Actionability | No concrete code, commands, or specific examples are provided. The content only describes capabilities in vague terms like 'provides step-by-step guidance' without actually providing any guidance. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for any response transformer task. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no examples, and no navigation to related resources despite mentioning 'Related Skills'. | 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.