check-schemas

Detect breaking changes in schema-form.json plugin descriptors; run the schema compatibility checker, interpret findings, and guide fixes.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./docs/agent-standards/skills/check-schemas/SKILL.md

Quality

Content

78%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 clear CI workflow, and it is reasonably concise for the density of information. Its main weakness is progressive disclosure: a large inlined reference table and EE details would be better split into separate referenced files.

Suggestions

Move the full breaking-change category table into a references file (e.g. references/breaking-changes.md) and keep only a short summary plus a clear link in SKILL.md.

Extract the Gravitee AM EE plugin coordinates detail into its own reference file, leaving a brief pointer and the single essential command inline.

Add an explicit 'if the checker reports breaking changes, apply the matching fix from the table and re-run until exit 0' feedback loop to make the validate→fix→retry cycle unmistakable.

Dimension	Reasoning	Score
Conciseness	The body is dense and tool-specific (baseline resolution, exemption logic, fixture categories) without explaining concepts Claude already knows; a few sections like the EE coordinates table could be trimmed, keeping it just below the lean anchor.	4 / 5
Actionability	Provides copy-paste ready bash, node, and mvn commands with concrete flags covering the common cases (explicit --base, --use-head false, single-pair checks, ZIP extraction), matching the fully executable anchor.	5 / 5
Workflow Clarity	Clear sequencing exists ('Run OSS check first — only proceed to EE check if OSS passes'), the test suite runs as a first-step checkpoint, and the 'How to fix' table plus exit-code semantics give a feedback loop; minor validation gaps remain around the manual external-repo flow.	4 / 5
Progressive Disclosure	Section headers are well organized, but no bundle reference files exist and large reference material (the 40+ row breaking-change table, EE coordinate details) is inlined in SKILL.md rather than split into one-level-deep referenced files.	3 / 5
	Total	16 / 20 Passed

Description

70%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, actionable, and well-scoped to a distinct niche, but it omits an explicit 'Use when...' trigger clause, which caps its completeness. Adding trigger guidance would lift the strongest remaining weakness.

Suggestions

Append an explicit 'Use when...' clause (e.g. 'Use when modifying schema-form.json plugin descriptors or preparing a release that may introduce breaking schema changes').

Add natural trigger synonyms users might say, such as 'schema migration', 'API compatibility', or 'plugin descriptor changes', to broaden keyword coverage.

Make 'guide fixes' more concrete by naming the fix outcome (e.g. 'interpret findings and apply the matching fix from the breaking-change table').

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Detect breaking changes in schema-form.json plugin descriptors; run the schema compatibility checker, interpret findings, and guide fixes' — with only 'guide fixes' being mildly generic, so it sits just below the fully comprehensive anchor.	4 / 5
Completeness	The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Strong domain keywords ('breaking changes', 'schema-form.json', 'schema compatibility checker', 'plugin descriptors') that a user would naturally say, though a few natural phrasings or synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche — breaking changes in schema-form.json plugin descriptors — with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	16 / 20 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
referenced_paths_exist	Referenced path issues: 9 missing, 9 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: gravitee-io/gravitee-access-management
Path: docs/agent-standards/skills/check-schemas/SKILL.md
Commit: 7022872

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