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.

60

1.13x
Quality

40%

Does it follow best practices?

Impact

100%

1.13x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

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

Quality

Content

72%

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

This is a focused, concise skill that clearly communicates testing patterns for packaging script regressions. Its main weakness is the lack of executable code examples—the Examples section references file paths and test names but doesn't show actual test code, which would significantly improve actionability. The workflow could also benefit from explicit sequencing of steps.

Suggestions

Add a concrete, executable code example showing a complete smoke test (e.g., a C# test method that invokes the script, asserts exit code 0, and checks output), rather than only referencing file paths and test names.

Restructure the Patterns section into a numbered step-by-step workflow: 1) write test that invokes real entry point, 2) assert exit code 0, 3) assert expected output/summary, 4) add negative assertions for legacy files.

DimensionReasoningScore

Conciseness

The content is lean and efficient. Every bullet point conveys a specific, non-obvious testing pattern. There's no explanation of basic concepts like what exit codes are or how testing frameworks work.

3 / 3

Actionability

The skill provides concrete file paths and test names as examples, and specific patterns like asserting exit code 0 and checking for legacy file absence. However, it lacks executable code snippets—no actual test code, assertions, or commands are shown, leaving Claude to infer implementation details.

2 / 3

Workflow Clarity

The patterns describe what to do but not in a clear sequential workflow. There's no explicit ordering of steps (e.g., first run the script, then check exit code, then validate output). For a skill involving test creation for packaging scripts, a clearer step-by-step process with validation checkpoints would be beneficial.

2 / 3

Progressive Disclosure

For a simple, focused skill under 50 lines with no need for external references, the content is well-organized into clear sections (Context, Patterns, Examples, Anti-Patterns) that are easy to navigate and scan.

3 / 3

Total

10

/

12

Passed

Description

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 heavily jargon-laden and fails to communicate concrete actions or trigger conditions in language a user or Claude could reliably match against. It lacks a 'Use when...' clause, uses no natural keywords, and the technical terms ('exit path', 'overlay surface') are opaque without additional context.

Suggestions

Replace jargon with plain-language descriptions of what the skill does, e.g., 'Runs regression tests on packaging scripts to verify correct exit codes and UI overlay behavior.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions packaging scripts, build regressions, exit code testing, or overlay verification.'

Include specific file types, tools, or frameworks involved (e.g., npm, shell scripts, CI pipelines) to improve trigger term coverage and distinctiveness.

DimensionReasoningScore

Specificity

The description uses vague, jargon-heavy language like 'asserting the real script exit path' and 'current overlay surface' without listing concrete, understandable actions. It's unclear what specific tasks this skill performs.

1 / 3

Completeness

There is no explicit 'Use when...' clause or equivalent trigger guidance. The 'what' is vaguely stated and the 'when' is entirely missing, making it unclear when Claude should select this skill.

1 / 3

Trigger Term Quality

The terms used ('script exit path', 'overlay surface', 'packaging-script regressions') are highly technical jargon that users would not naturally say when seeking help. No common or natural trigger terms are present.

1 / 3

Distinctiveness Conflict Risk

The description is niche enough in its domain (packaging scripts, regressions) that it's unlikely to broadly conflict with many other skills, but the vague terminology could still cause confusion with other testing or CI-related skills.

2 / 3

Total

5

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

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.