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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

50%

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

The body is a well-structured overview with real, signaled references and a clear workflow, but it is held back by reference duplication, abstract synthesis guidance, missing inline validation, and orphaned bundle files.

Suggestions

Link the scripts/ and assets/ bundle files (e.g. plugin_analyzer.py, plugin_selection_rules.yaml, example_plugin_analysis.json) from the body so they are discoverable instead of orphaned.

Add inline validation checkpoints to the workflow (e.g. 'confirm at least one relevant plugin was found before extracting', 'verify extracted patterns are compatible with the current environment before applying').

De-duplicate the Instructions and Examples sections against how-it-works.md and example-workflows.md, keeping the body a true overview that defers detail to the references.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, but the Overview carries buzzword padding ('universal skill chameleon') and the Instructions/Examples sections duplicate content that also appears in how-it-works.md and example-workflows.md, so it could be tightened.	2 / 3
Actionability	It gives concrete paths and per-component extraction guidance (e.g. 'globbing across plugins/community/ ... Match on plugin.json descriptions'), but the executable commands live only in references and the synthesis step ('merging complementary approaches, simplifying where possible') stays abstract.	2 / 3
Workflow Clarity	A clear 6-step sequence (Analyze, Search, Extract, Synthesize, Apply, Report) is present with a reactive error table, but there are no inline validation checkpoints before proceeding between steps, so it stays at the sequence-with-gaps level.	2 / 3
Progressive Disclosure	References are real, one-level-deep, and well-signaled with a Resources section, but the body duplicates reference content and the scripts/ and assets/ bundle files (plugin_analyzer.py, templates, example JSON) are never linked from the body, leaving navigation incomplete.	2 / 3
	Total	8 / 12 Passed

Description

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 states what the skill does but relies on circular, non-natural trigger language and buzzword padding. It is distinguishable in concept yet vague enough to risk mis-triggering.

Suggestions

Replace circular triggers ('appropriate context detected', 'relevant phrases based on skill purpose') with concrete natural phrases users would say, e.g. 'Use when adapting another plugin's approach to a new task' or 'when you want to reuse patterns from existing commands/agents/skills'.

Drop the 'universal skill chameleon' fluff and instead enumerate specific concrete actions (discover plugins, extract command/agent/skill patterns, synthesize an adapted workflow).

Make the 'when' clause explicit and bounded so the skill is unlikely to fire for unrelated tasks.

Dimension	Reasoning	Score
Specificity	Names some concrete actions ('analyzes existing plugins to extract their capabilities, then adapts and applies those skills') but stays abstract and pads with fluff ('universal skill chameleon'), so it is not a comprehensive list of specific actions.	2 / 3
Completeness	The 'what' is clearly stated, and a 'Use when' clause exists, but the 'when' guidance is vague and circular rather than explicit triggers, so it does not reach the both-what-and-when-with-explicit-triggers level.	2 / 3
Trigger Term Quality	Triggers are circular or generic — 'skill adapter' is the skill's own name, 'appropriate context detected' and 'relevant phrases based on skill purpose' are not natural phrases a user would say when needing this skill.	1 / 3
Distinctiveness Conflict Risk	The plugin-analysis niche is somewhat specific, but the 'universal skill chameleon' framing and generic triggers ('appropriate context detected') mean it could still overlap with or trigger for the wrong skill.	2 / 3
	Total	7 / 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
Commit: 3022dd3

Reviewed: 2 days 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.