CtrlK
BlogDocsLog inGet started
Tessl Logo

mcp-schema-enum-regression

Keep generated MCP schemas strict-client compatible by avoiding nullable enum signatures.

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/mcp-schema-enum-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 content is concise, well-structured, and actionable, but presents design rules rather than an ordered workflow and never wires the referenced regression test in as an explicit validation checkpoint for the batch scan it prescribes.

Suggestions

Add a short numbered workflow that ends with an explicit validation step: generate schemas, run GeneratedToolSchemaEnumRegressionTests, and only proceed when green.

Turn the 'scan every enum-bearing property' batch directive into a checklist with a verify step so the destructive/batch cap is lifted.

Include one runnable command or snippet (e.g. the dotnet test invocation for the regression test) to close the actionability gap to a 5.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — Context, Patterns, Examples, and Anti-Patterns each earn their place with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient' anchor.

5 / 5

Actionability

Directives are concrete and anchored to real file paths (McpToolGenerator.cs, the regression test) with specific transforms (required action enum, optional enum-like inputs as strings, local parse); the minor gap is that guidance is prose with no runnable command, sitting just below the fully copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

Patterns read as a design checklist rather than a sequenced workflow, and although the Examples section references a regression test, there is no explicit validate->fix->retry checkpoint; because 'scan every enum-bearing property across the tool catalog' is a batch operation, the missing-validation cap holds it at 3.

3 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files, yet is cleanly sectioned (Context, Patterns, Examples, Anti-Patterns) with one-level inline file references, satisfying the simple-skill exception for a 5.

5 / 5

Total

17

/

20

Passed

Description

55%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 is specific and clearly niche but reads as a capability statement rather than a discovery trigger: it lacks an explicit 'Use when...' clause and leans on technical jargon instead of natural user phrasing.

Suggestions

Add an explicit trigger clause, e.g. 'Use when an MCP client rejects tool schemas because enum arrays contain null or empty-string sentinels.'

Include natural-language keywords a user would actually say (e.g. 'MCP client rejects tool', 'enum null in schema') alongside the technical terms.

Keep the existing what-statement but reframe it so the 'when' is as concrete as the 'what'.

DimensionReasoningScore

Specificity

Names the MCP schema domain with two concrete actions — 'Keep generated MCP schemas strict-client compatible' and 'avoiding nullable enum signatures' — which sits just above the 1-2-actions anchor but below the comprehensive multi-action anchor 5.

4 / 5

Completeness

It states a clear 'what' but has no 'Use when...' clause or explicit trigger, so per the missing-trigger guidance it caps at 3 ('clear what but when missing').

3 / 5

Trigger Term Quality

The only keywords are technical jargon ('MCP schemas', 'nullable enum signatures') that a user would rarely say verbatim; natural trigger phrases like 'client rejects tool schemas' appear in the body but not the description, matching the 'one or two generic keywords, missing natural phrases' anchor.

2 / 5

Distinctiveness Conflict Risk

The scope is a narrow niche (nullable enum signatures in generated MCP schemas) with distinct triggers and minimal overlap with other skills, matching the 'clear niche with distinct triggers' anchor.

5 / 5

Total

14

/

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.