CtrlK
BlogDocsLog inGet started
Tessl Logo

plugin-build-smoke-regression

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

75

1.13x
Quality

63%

Does it follow best practices?

Impact

100%

1.13x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.squad/skills/plugin-build-smoke-regression/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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.

The body is concise, well-structured, and gives concrete, specific test-authoring guidance for its narrow niche. Its main gap is the absence of an explicit validate-fix-retry workflow sequence.

Suggestions

Add an ordered workflow with an explicit validation checkpoint (run real script -> assert exit 0 + summary -> on failure, inspect overlay diff -> fix -> re-run).

Include one copy-paste-ready test snippet or command invocation to lift actionability to fully executable.

Clarify how to detect which overlay asset drifted when a smoke test fails, giving Claude a concrete remediation path.

DimensionReasoningScore

Conciseness

Lean, ~24-line body with no concept re-explanation; every bullet is actionable and assumes Claude's competence, matching the 'lean and efficient' anchor.

5 / 5

Actionability

Concrete, specific guidance (assert exit code 0, ASCII summary for PowerShell, real test names and file paths) but no copy-paste-ready commands or code; minor gaps keep it below fully executable.

4 / 5

Workflow Clarity

Patterns list what to assert but present a checklist rather than a sequenced workflow with explicit validation/fix/retry checkpoints; validation gaps keep it at the anchor for listed steps without clear checkpoints.

3 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no bundle files, with well-organized Context/Patterns/Examples/Anti-Patterns sections — meets the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

46%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 states a clear purpose and concrete actions but omits any explicit 'Use when...' trigger guidance and leans on jargon rather than natural user keywords. It is distinct but not optimally discoverable.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when a packaging or publish smoke test silently regressed but file-copy assertions still passed').

Replace or augment jargon ('overlay surface') with natural user-facing terms ('shipped plugin files', 'bootstrap assets').

Name a third concrete action to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain ('packaging-script regressions') and two concrete actions ('asserting the real script exit path and current overlay surface'), but coverage is not comprehensive — matches the anchor for 1-2 concrete actions.

3 / 5

Completeness

Has a clear 'what' (catch regressions via exit-path and overlay assertions) but no 'Use when...' trigger clause; per guidelines a missing trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Relies on technical jargon ('overlay surface', 'script exit path') with no natural phrases a user would actually say; missing the common terms users use to request this.

2 / 5

Distinctiveness Conflict Risk

'Packaging-script regressions' and 'overlay surface' carve a specific niche with minimal overlap risk against other skills, though phrasing is technical.

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.