CtrlK
BlogDocsLog inGet started
Tessl Logo

api-schema-inferrer

This skill should be used when the user asks to "infer schemas", "generate schemas from examples", "add schemas", "bootstrap schemas", or mentions inferring, generating, or adding schemas to OpenAPI/OAS specifications that have examples but missing schema definitions.

72

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable with executable commands and a concrete before/after example, and it is well-structured with real bundle references. It is slightly held back by minor verbosity and the absence of an explicit validate-fix-retry loop in the apply workflow.

Suggestions

Add an explicit feedback loop for the apply path, e.g. 'run --dry-run first; if the preview is wrong, adjust examples and re-run --dry-run before applying'.

Tighten the 'What It Does' bullet list and trim the inline before/after example to the minimal diff that illustrates type/format/required inference.

Link the bundled references/example-missing-schemas.yaml from the body so users can try the commands against a known sample.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands and a justifiable before/after example, but the "What It Does" bullets and the large inline example include minor over-explanation that could be trimmed, fitting the "efficient; minor instances" anchor rather than a lean 5.

4 / 5

Actionability

Provides copy-paste ready commands (dry-run and apply invocations with real script paths), a pip prerequisite, and a complete before/after YAML example covering the common case, matching the fully executable anchor.

5 / 5

Workflow Clarity

Clear sequence (dry-run preview, apply with backup, numbered post-inference checklist including "Run validation") with the dry-run acting as a validation checkpoint, but it lacks an explicit validate-fix-retry feedback loop in the apply path, so it sits at "most checkpoints present" rather than 5.

4 / 5

Progressive Disclosure

Well-organized into clear sections with real, correctly-pathed references to the bundled script and related skills; the bulk inline before/after example is justified for a transform skill but keeps it just below the ideal one-level-deep reference structure.

4 / 5

Total

17

/

20

Passed

Description

95%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 strong: it states concrete actions, gives comprehensive natural trigger phrases, and explicitly covers both what the skill does and when to use it, all scoped to a distinct niche. Only minor specificity gaps keep it from a perfect score across every dimension.

DimensionReasoningScore

Specificity

Lists several concrete actions — "infer schemas", "generate schemas from examples", "add schemas", "bootstrap schemas" — with only minor gaps in coverage, matching the "several specific actions" anchor rather than the fully comprehensive 5.

4 / 5

Completeness

Explicitly answers both "what" (generate/add schemas from examples to OAS specs with missing schema definitions) and "when" ("when the user asks to... or mentions..."), with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases including synonyms ("infer", "generate", "add", "bootstrap") plus the file/domain context (OpenAPI/OAS), matching the anchor for comprehensive coverage of natural terms.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (schema inference for OpenAPI/OAS specs with examples but missing schemas) with distinct triggers, giving minimal conflict risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mulesoft/mulesoft-dx
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.