CtrlK
BlogDocsLog inGet started
Tessl Logo

plugin-surface-wording

Describe plugin release mechanics without overclaiming client-specific installation behavior.

58

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.squad/skills/plugin-surface-wording/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

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

A tight, well-structured instruction-only skill: concrete do/don't patterns and examples with no padding. The only gap is actionability settling at 4 because the guidance is wording/phrasing rather than executable code, though that is appropriate for this skill type.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — four short Pattern bullets, two concrete Example do/don't pairs, and two Anti-Pattern bullets with no padding or explanation of concepts Claude already knows, matching anchor 5 ('Lean and efficient; every token earns its place').

5 / 5

Actionability

Concrete, specific guidance ('Describe the release output as plugin artifacts...', 'Keep install commands only for the clients you have actually verified') plus copy-ready wording examples; for an instruction-only skill this is actionable, but it is wording guidance rather than executable code with minor coverage gaps, fitting anchor 4.

4 / 5

Workflow Clarity

This is a simple single-purpose skill with clear organization (Context, Patterns, Examples, Anti-Patterns) and an unambiguous single action; it is not a sequenced or destructive workflow, so the simple-skill exception applies but there are no checkpoints to push it to 5, settling at anchor 4.

4 / 5

Progressive Disclosure

At ~25 lines with no need for external references and well-organized section headers, it meets the rubric's under-50-lines exception where progressive disclosure can score 5 with just well-organized sections; no bundle files exist to verify.

5 / 5

Total

18

/

20

Passed

Description

48%Weight 40%Scale 1-5

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 identifies a clear, distinctive niche but is light on concrete capabilities and omits any 'Use when...' trigger clause, which caps completeness. It reads as a meta-instruction about how to write rather than an enumeration of actions.

Suggestions

Add a 'Use when...' trigger clause, e.g. 'Use when documenting repos that publish plugin bundles for agent/plugin clients.'

Replace the generic verb 'Describe' with one or two concrete actions such as 'Phrase release notes' or 'Scope install commands' to lift specificity from anchor 2 to 3.

Include natural synonyms users say ('plugin bundles', 'marketplace', 'install commands') alongside the technical terms to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The phrase names the domain ('plugin release mechanics') but the only action verb is the generic 'Describe', with no enumerated concrete capabilities — matching anchor 2 ('Names the domain but actions are minimal or generic') better than anchor 3, which expects 1-2 concrete actions.

2 / 5

Completeness

It states a clear 'what' (describe plugin release mechanics without overclaiming) but includes no 'Use when...' or equivalent trigger clause; per the rubric guideline a missing 'when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords ('plugin', 'release', 'installation') appear, but they are wrapped in technical phrasing ('release mechanics', 'overclaiming', 'client-specific installation behavior') and lack natural synonyms a user would say, fitting anchor 3 ('Some relevant keywords but missing common variations or synonyms').

3 / 5

Distinctiveness Conflict Risk

The niche (plugin release documentation wording, client-specific install scoping) is fairly distinct with only minor overlap risk against other documentation/release skills, matching anchor 4 ('Mostly distinct; minor overlap risk').

4 / 5

Total

12

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
sbroenne/mcp-server-excel
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.