plugins

Plugin management, installation, and lifecycle control

Quality

48%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/plugins/SKILL.md

Quality

Discovery

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 is too terse and generic, providing only a high-level summary of the domain without concrete actions or explicit trigger guidance. It lacks a 'Use when...' clause, platform specificity, and natural user-facing keywords, making it difficult for Claude to reliably select this skill from a large pool.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks to install, enable, disable, update, or remove plugins.'

Specify the platform or system context (e.g., 'WordPress plugins', 'IDE extensions', 'application add-ons') to reduce conflict risk with other plugin-related skills.

Replace vague terms like 'lifecycle control' with concrete actions such as 'enable/disable plugins, check for updates, resolve plugin dependencies, configure plugin settings.'

Dimension	Reasoning	Score
Specificity	Names the domain ('plugin') and some actions ('management, installation, lifecycle control'), but these are somewhat abstract. 'Lifecycle control' is vague, and it doesn't list concrete actions like 'enable/disable plugins', 'update versions', or 'resolve dependencies'.	2 / 3
Completeness	Describes what it does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' portion is also weak, so this scores a 1.	1 / 3
Trigger Term Quality	Includes 'plugin', 'installation', and 'management' which are relevant keywords, but misses common variations users might say like 'extension', 'add-on', 'package', 'enable', 'disable', 'uninstall', or 'update'. 'Lifecycle control' is jargon users wouldn't naturally use.	2 / 3
Distinctiveness Conflict Risk	'Plugin' narrows the domain somewhat, but without specifying which platform, framework, or system the plugins belong to, it could easily conflict with other plugin-related skills (e.g., WordPress plugins vs. IDE plugins vs. application plugins).	2 / 3
	Total	7 / 12 Passed

Implementation

64%

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

This skill provides comprehensive, actionable API reference content for plugin management with good executable code examples. Its main weaknesses are the monolithic structure that could benefit from progressive disclosure into separate files, and the lack of explicit validation/verification workflows for plugin operations like installation and updates. The best practices section is somewhat generic and could be more specific to the Clodds plugin ecosystem.

Suggestions

Add explicit validation steps for plugin operations (e.g., verify installation succeeded, check compatibility before enabling, validate settings schema before applying)

Split into overview SKILL.md with references to separate files: COMMANDS.md for chat commands, API.md for TypeScript reference, CUSTOM-PLUGINS.md for plugin creation guide

Remove the best practices section or replace with Clodds-specific gotchas that Claude wouldn't already know

Dimension	Reasoning	Score
Conciseness	The content is reasonably structured but includes some unnecessary verbosity—console.log statements in examples that don't add instructional value, and the lifecycle events section is somewhat redundant with the enable/disable section. The best practices section states obvious things Claude already knows.	2 / 3
Actionability	The skill provides fully executable TypeScript code examples and concrete chat commands. The custom plugin creation example is complete and copy-paste ready, including the full class implementation, package.json structure, and directory layout.	3 / 3
Workflow Clarity	While individual operations are clear, there's no explicit workflow for the plugin lifecycle (install → configure → enable → validate). For operations like uninstall or update, there are no validation checkpoints or error recovery steps mentioned. The plugin creation process lacks a clear sequential workflow with verification steps.	2 / 3
Progressive Disclosure	The content is organized into logical sections with clear headers, but it's a monolithic document (~200 lines) that could benefit from splitting the API reference, custom plugin creation guide, and chat commands into separate files. No references to external files for deeper topics.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: alsk1992/CloddsBot
Commit: e71a5f6

Reviewed: 11 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.