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.

Quality

43%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/examples/pi-pathfinder/skills/skill-adapter/SKILL.md

Quality

Content

55%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured with a clear six-step workflow, error table, and real one-level-deep references that exist in the bundle. It falls short of top marks because core instructions stay descriptive rather than executable and the bundle carries stale/empty stub artifacts.

Suggestions

Surface the bundled plugin_analyzer.py and skill_adaptation_template.py with concrete invocation examples in the body so the guidance is executable rather than descriptive.

Add an explicit validation/checkpoint step in the workflow before applying the synthesized skill (e.g. confirm extracted patterns are compatible with the target environment).

Fix stale 'pi-pathfinder' naming in the references/assets README files and either fill in or remove the empty examples.md stub so navigation is consistent.

Dimension	Reasoning	Score
Conciseness	The body is reasonably efficient with numbered steps and tables, but the Overview, Examples section, and references repeat capability extraction bullets that Claude already understands, adding some padding.	2 / 3
Actionability	It gives concrete file-globbing targets and a plugin component breakdown, but offers no executable code or commands in the main body — the actual scripts live in the bundle rather than inline, leaving the core instructions descriptive.	2 / 3
Workflow Clarity	A clear six-step sequence is present, but validation checkpoints are implicit; while an Error Handling table covers failures, the synthesis/apply steps lack explicit verify-before-apply feedback loops for batch or destructive adaptation.	2 / 3
Progressive Disclosure	References are signaled with ${CLAUDE_SKILL_DIR} paths and the bundle contains matching files (how-it-works.md, example-workflows.md, errors.md), but references/README.md and assets/README.md still carry a stale 'pi-pathfinder' name and examples.md is an empty stub, so navigation is inconsistent.	2 / 3
	Total	8 / 12 Passed

Description

32%

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 states what the skill does but relies on vague, self-referential trigger phrasing rather than concrete keywords a user would actually say. It reads as templated filler that obscures its niche and raises conflict risk.

Suggestions

Replace circular triggers ('skill adapter functionality', 'appropriate context detected') with concrete natural phrases users would say, e.g. 'Use when you want to reuse patterns from existing plugins to solve a new task'.

Drop the buzzword 'universal skill chameleon' and instead list the concrete actions (discover plugins, extract capabilities, synthesize patterns) to improve specificity and distinctiveness.

Add an explicit 'Use when...' clause naming the concrete triggering contexts (adapting another plugin's approach, learning from installed skills).

Dimension	Reasoning	Score
Specificity	Names the domain (existing plugins) and several actions (extract, adapt, apply), but 'adapts and applies those skills' and 'universal skill chameleon' are abstract and not comprehensive concrete actions.	2 / 3
Completeness	The 'what' is present, but the 'when' is only implied via vague phrasing ('Use when appropriate context detected') with no explicit user-facing triggers; per guidelines this caps completeness at 2.	2 / 3
Trigger Term Quality	Triggers are circular and generic — 'skill adapter functionality', 'appropriate context detected', 'relevant phrases based on skill purpose' — none are natural keywords a user would actually say.	1 / 3
Distinctiveness Conflict Risk	'Adapts and applies skills to the current task' and 'universal skill chameleon' are extremely generic and would overlap with almost any capability skill, risking false triggers.	1 / 3
	Total	6 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/examples/pi-pathfinder/skills/skill-adapter/SKILL.md
Commit: 15940c5

Reviewed: about 21 hours ago

Table of Contents

Discovery Implementation Validation

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.