skill-adapter
Execute 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. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
20
10%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/examples/pi-pathfinder/skills/skill-adapter/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 extremely weak across all dimensions. It relies on vague buzzwords ('universal skill chameleon'), placeholder trigger guidance ('Use when appropriate context detected'), and describes no concrete actions. It would be nearly impossible for Claude to correctly select this skill from a pool of alternatives, and its universal framing creates maximum conflict risk with other skills.
Suggestions
Replace vague language with specific concrete actions—describe exactly what 'analyzing plugins' and 'adapting skills' means in practice (e.g., 'Reads plugin source code to extract API endpoints and function signatures').
Add a genuine 'Use when...' clause with real trigger scenarios and natural user phrases instead of the placeholder 'Use when appropriate context detected' (e.g., 'Use when the user asks to combine capabilities from multiple plugins or wants to reuse a plugin's logic for a different task').
Define a clear, narrow scope to reduce conflict risk—specify which types of plugins, what kinds of tasks, and what distinguishes this from simply using those plugins directly.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'adapts and applies those skills' and 'universal skill chameleon that learns from other plugins.' No concrete actions are listed—there's no specificity about what it actually does (e.g., what kind of analysis, what outputs). | 1 / 3 |
Completeness | The 'what' is extremely vague (analyzes plugins, adapts skills) and the 'when' is essentially a placeholder ('Use when appropriate context detected' and 'Trigger with relevant phrases based on skill purpose'). Neither question is meaningfully answered. | 1 / 3 |
Trigger Term Quality | The only concrete trigger term is 'skill adapter,' which is not something a user would naturally say. Phrases like 'relevant phrases based on skill purpose' and 'appropriate context detected' are meta-placeholders, not actual trigger terms. | 1 / 3 |
Distinctiveness Conflict Risk | As a 'universal skill chameleon,' this description is inherently designed to overlap with every other skill. It has no clear niche and would conflict with virtually any skill in a multi-skill environment. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
20%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 ambitious but practically weak. It describes a meta-process of learning from other plugins but provides no concrete, executable guidance—no actual grep/find commands, no example file parsing code, no template for the adaptation report. The content is verbose, explaining things Claude already knows (plugin structure, what commands and agents are), while failing to provide the specific, actionable details that would make this skill useful.
Suggestions
Add concrete, executable commands for plugin discovery (e.g., `find plugins/ -name 'plugin.json' | xargs grep -l 'security'`) and pattern extraction (e.g., specific jq or grep patterns for reading plugin.json fields).
Replace the prose-based examples with actual input/output examples showing a real plugin being analyzed and the resulting adaptation report format.
Remove explanatory text about what plugins, commands, agents, and skills are—Claude already knows these concepts. Focus only on the specific discovery and synthesis logic.
Add a validation checkpoint after step 4 (synthesis) to verify the combined approach is coherent before applying it, such as checking for conflicting tool requirements or incompatible patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is verbose and explains concepts Claude already understands (what plugins are, how to read files, what commands/agents/skills are). The overview restates the description. Phrases like 'Functions as a universal skill chameleon' and extensive explanations of plugin structure are unnecessary padding. The entire concept is also somewhat meta-circular—it's teaching Claude to read other skills, which Claude can already do. | 1 / 3 |
Actionability | Despite being a multi-step process, there are no concrete commands, code snippets, or executable examples. Instructions like 'Search existing plugins for relevant capabilities using file globbing' are vague—no actual glob patterns, grep commands, or find commands are provided. The examples section describes processes in prose rather than showing actual commands or outputs. | 1 / 3 |
Workflow Clarity | The six numbered steps provide a clear sequence, and the error handling table adds some recovery guidance. However, there are no validation checkpoints—no step verifies that extracted patterns are correct or that the synthesized approach works before applying it. For a skill that involves analyzing and adapting potentially complex patterns, this lack of verification is a significant gap. | 2 / 3 |
Progressive Disclosure | The skill references three external files (how-it-works.md, example-workflows.md, errors.md) which is good structure, but no bundle files were provided, so these references are unverifiable. The main content itself is somewhat monolithic—the error handling table and examples could potentially be in referenced files to keep the main skill leaner. | 2 / 3 |
Total | 6 / 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
6e9558f
- 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.