plugin-surface-wording
Describe plugin release mechanics without overclaiming client-specific installation behavior.
56
46%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.squad/skills/plugin-surface-wording/SKILL.mdQuality
Discovery
7%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 very weak across all dimensions. It reads more like an internal constraint or meta-instruction ('without overclaiming') than a functional skill description. It fails to list concrete actions, lacks natural trigger terms, and provides no guidance on when Claude should select this skill.
Suggestions
Replace the abstract phrase 'release mechanics' with specific concrete actions such as 'Generate changelogs, tag versions, publish plugin packages, and create release notes for plugin distributions.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about releasing a plugin, publishing a package, versioning, or creating release notes.'
Move the constraint about not overclaiming installation behavior into the skill body rather than the description, as it is an internal instruction, not a capability description.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'release mechanics' without listing any concrete actions. It does not specify what the skill actually does (e.g., build, package, publish, version bump). The phrase 'without overclaiming client-specific installation behavior' is a constraint, not an action. | 1 / 3 |
Completeness | The description weakly addresses 'what' (describe plugin release mechanics) and completely omits 'when' — there is no 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The description lacks natural keywords a user would say. Terms like 'release mechanics' and 'overclaiming client-specific installation behavior' are unusual jargon. Users would more likely say 'publish plugin', 'release', 'deploy', or mention specific plugin ecosystems. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'plugin release' provides some domain specificity that narrows the scope beyond generic document or code skills. However, 'release mechanics' is still broad enough to overlap with deployment, CI/CD, or publishing skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that clearly communicates documentation language guidelines for plugin release mechanics. Its main weakness is that it provides guidance at the phrasing/pattern level rather than offering concrete, copy-paste-ready documentation templates or examples that Claude could directly use. The anti-patterns section adds valuable guardrails.
Suggestions
Add a concrete documentation template or snippet showing a complete, well-written release section that Claude could adapt, rather than only providing individual phrase-level examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every sentence earns its place. No unnecessary explanations of what plugins are or how publishing works. The content is lean and assumes Claude understands the domain. | 3 / 3 |
Actionability | Provides clear guidance on language patterns and anti-patterns, but lacks concrete code examples, specific commands, or copy-paste ready templates for documentation. The examples are illustrative phrases rather than executable documentation snippets. | 2 / 3 |
Workflow Clarity | This is a simple, single-purpose skill about documentation language choices rather than a multi-step process. The single task (choosing accurate terminology for plugin releases) is unambiguous, with clear patterns, examples, and anti-patterns providing sufficient guidance. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into logical sections (Context, Patterns, Examples, Anti-Patterns) that are easy to scan and navigate. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%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
- sbroenne/mcp-server-excel
- Commit
468809e
- 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.