plugin-build-smoke-regression

Catch packaging-script regressions by asserting the real script exit path and current overlay surface.

1.13x

Quality

—

Does it follow best practices?

Impact

100%

1.13x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

87%

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

The body is concise, actionable, and well-organized for a small single-purpose skill, with concrete assertions and real example references. The only gap is the absence of an explicit sequenced workflow with validation checkpoints, which keeps workflow clarity at 2.

Dimension	Reasoning	Score
Conciseness	Lean bullet-pointed guidance with no padding and no explanation of concepts Claude already knows; every line earns its place.	3 / 3
Actionability	Gives concrete, specific guidance - assert 'exit code 0', assert current assets present and legacy files absent, prefer ASCII summaries - with real test-file and method-name examples, which is actionable for an instruction-only skill.	3 / 3
Workflow Clarity	Patterns are listed clearly as a checklist but there is no explicit sequenced multi-step workflow with validation checkpoints or feedback loops.	2 / 3
Progressive Disclosure	Under 50 lines, single-purpose, with no external references needed; well-organized into Context, Patterns, Examples, and Anti-Patterns sections.	3 / 3
	Total	11 / 12 Passed

Description

67%

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 concrete and occupies a distinct niche, but it omits explicit 'Use when' trigger guidance and relies on internal jargon rather than natural user keywords. Adding a trigger clause with user-facing terms would raise the weaker dimensions.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill, e.g. 'Use when a packaging or publish smoke test fails after a script or overlay change.'

Replace internal jargon ('overlay surface', 'script exit path') with terms a user would naturally say, such as 'build', 'publish script', or 'smoke test', to improve trigger-term quality.

Round out completeness by pairing the 'what' with a concrete 'when' trigger so both facets are explicitly answered.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions - 'Catch packaging-script regressions', 'asserting the real script exit path', and 'current overlay surface' - rather than vague language.	3 / 3
Completeness	Clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 2.	2 / 3
Trigger Term Quality	Contains some relevant keywords ('packaging-script regressions') but leans on internal jargon ('overlay surface', 'script exit path') that a user would not naturally say, missing common variations.	2 / 3
Distinctiveness Conflict Risk	Occupies a clear, narrowly bounded niche (plugin packaging smoke-test regressions) that is unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: sbroenne/mcp-server-excel
Commit: b268be5

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