skill-adapter
Analyzes existing plugins to extract their capabilities, then adapts and applies those skills to the current task. Acts as a universal skill chameleon that learns from other plugins. Activates when you request "skill adapter" functionality.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill skill-adapter72
Quality
35%
Does it follow best practices?
Impact
98%
1.05xAverage score across 6 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skill-structure-cleanup-20251108-073936/plugins/examples/pi-pathfinder/skills/pi-pathfinder/SKILL.mdDiscovery
35%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description attempts to explain a meta-skill for learning from other plugins, but suffers from abstract language and a circular trigger clause. The concept is interesting but the description lacks concrete examples of what 'adapting skills' means in practice, and the activation trigger ('skill adapter') is technical jargon rather than natural user language.
Suggestions
Replace the circular trigger 'Activates when you request skill adapter functionality' with natural user phrases like 'Use when the user wants to apply capabilities from one plugin to a different context' or 'when asked to learn from or mimic another plugin'
Add concrete examples of what 'adapts and applies skills' means - e.g., 'copies formatting rules from one plugin to apply to different file types' or 'extracts API patterns from existing integrations'
Include natural trigger terms users might actually say, such as 'learn from', 'copy behavior', 'use like [other plugin]', 'transfer skills'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (plugin analysis) and some actions ('analyzes', 'extract capabilities', 'adapts and applies'), but the actions remain somewhat abstract - 'adapts and applies those skills' is vague about what concrete operations are performed. | 2 / 3 |
Completeness | The 'what' is partially addressed (analyzes plugins, extracts capabilities, adapts skills), but the 'when' clause is weak - 'Activates when you request skill adapter functionality' is circular and doesn't provide meaningful trigger guidance. | 2 / 3 |
Trigger Term Quality | The only explicit trigger is 'skill adapter' which is technical jargon unlikely to be naturally used by users. Missing natural terms users might say like 'learn from plugin', 'copy skill', 'use another plugin's ability', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The concept of a 'universal skill chameleon' is somewhat distinctive, but phrases like 'adapts and applies skills to the current task' are generic enough to potentially overlap with other meta-skills or plugin management tools. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is conceptually interesting but suffers from significant verbosity, explaining meta-concepts and processes that Claude inherently understands. The content reads more like documentation about a feature than actionable instructions. While the structure is reasonable, the lack of concrete executable examples and validation steps limits its practical utility.
Suggestions
Reduce content by 50%+ by removing explanations of basic concepts (what plugins are, how grep works, what 'adaptation' means) and trust Claude's intelligence
Replace abstract workflow descriptions with concrete, executable command sequences - e.g., actual grep patterns that work, specific file parsing approaches
Add validation checkpoints: how to verify a plugin was correctly analyzed, how to confirm an adaptation is working, what to do when extraction fails
Move the three detailed 'Example Workflows' to a separate EXAMPLES.md file and keep only a brief quick-start example in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanations of concepts Claude already understands (what plugins are, how to read files, basic grep commands). The 'Meta-Learning' and 'Transparency' sections add little actionable value. Could be reduced by 60%+ while preserving all useful information. | 1 / 3 |
Actionability | Provides some concrete guidance (grep commands, file paths) but most content is abstract methodology description rather than executable instructions. The 'Example Workflows' describe processes conceptually rather than providing copy-paste ready commands or code. | 2 / 3 |
Workflow Clarity | Has a clear 5-step numbered process (Task Analysis → Plugin Discovery → Capability Extraction → Pattern Synthesis → Skill Application), but lacks validation checkpoints. No feedback loops for when plugin analysis fails or when adaptation doesn't work as expected. | 2 / 3 |
Progressive Disclosure | Content is organized with clear headers, but everything is in one monolithic file. The extensive examples and detailed sections could be split into separate reference files. No external file references for advanced topics or detailed examples. | 2 / 3 |
Total | 7 / 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 | |
- 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.