check-schemas

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

1.31x

Quality

72%

Does it follow best practices?

Impact

95%

1.31x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

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

Quality

Content

77%

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

This is a highly actionable and well-structured skill with excellent executable examples and clear workflows. Its main weakness is length — the comprehensive breaking-changes table and EE-specific sections make it verbose for a single SKILL.md file, and the content would benefit from splitting into a concise overview with references to detailed sub-documents. The workflow clarity is strong with good sequencing and implicit validation through tool exit codes.

Suggestions

Move the full breaking-changes table to a separate BREAKING_CHANGES_REFERENCE.md and keep only a summary (top 5-6 most common) in SKILL.md

Extract the EE plugin and external repo sections into a separate EE_PLUGINS.md reference file, linking from the main skill

Dimension	Reasoning	Score
Conciseness	The skill is quite long (~200 lines) and includes extensive detail on EE plugin coordinates, Maven dependency resolution, and a comprehensive breaking-changes table. While most content is useful reference material, some sections (e.g., the EE plugin coordinate table, the lengthy external plugin repo section) could be more concise. The breaking-changes table is borderline — useful as a reference but very long.	2 / 3
Actionability	The skill provides fully executable bash and node commands throughout, with concrete examples for every use case (CI check, explicit baseline, single schema pair, EE plugins, external repos, test suite). The fix table gives specific, actionable remediation steps. Commands are copy-paste ready.	3 / 3
Workflow Clarity	Multi-step processes are clearly sequenced (e.g., the external plugin check has numbered steps 1-3, the EE check shows OSS-first-then-EE chaining with &&). The CI exemption logic is well-explained. Validation is inherent in the tool (exit codes), and the 'Understanding findings' section shows how to interpret results. The 'How to fix' table closes the feedback loop.	3 / 3
Progressive Disclosure	The content is structured with clear headers and sections, but it's essentially a monolithic document. The breaking-changes table, EE plugin details, and external repo instructions could be split into separate reference files. References to fixture directories and scripts exist but there are no bundle files to support progressive disclosure. For a skill this long, more content should be offloaded.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 in specificity and distinctiveness, clearly naming concrete actions and a very specific domain (schema-form.json plugin descriptors). However, it lacks an explicit 'Use when...' clause, and the trigger terms are somewhat technical, which may not match how users naturally phrase their requests.

Suggestions

Add a 'Use when...' clause such as 'Use when the user modifies schema-form.json files, asks about backward compatibility of plugin descriptors, or needs to validate schema changes.'

Include more natural trigger terms like 'backward compatibility', 'schema validation', 'plugin schema migration', or 'schema changes' to improve discoverability.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: detect breaking changes, run the schema compatibility checker, interpret findings, and guide fixes. These are clear, actionable capabilities.	3 / 3
Completeness	Clearly answers 'what does this do' (detect breaking changes, run checker, interpret findings, guide fixes) but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric.	2 / 3
Trigger Term Quality	Includes some relevant terms like 'breaking changes', 'schema-form.json', 'schema compatibility checker', and 'plugin descriptors', but these are fairly technical. Missing common user phrasings like 'backward compatibility', 'schema validation', or 'migration'. Users might not naturally say 'schema-form.json plugin descriptors'.	2 / 3
Distinctiveness Conflict Risk	Very specific niche targeting 'schema-form.json plugin descriptors' and a specific 'schema compatibility checker' tool. Unlikely to conflict with other skills due to the highly specialized domain.	3 / 3
	Total	10 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: gravitee-io/gravitee-access-management
Commit: 9821842

Reviewed: about 2 months 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.