CtrlK
BlogDocsLog inGet started
Tessl Logo

frozen-prior-schema-must-not-share-helpers

Use when widening a shared coralogix_dashboard widget schema helper like LineChartSchema(). Checks whether dashboard_schema/v1..v3 also use it; prior schemas must stay frozen.

69

Quality

83%

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

93%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 body is lean, highly actionable, and well-structured with an executable check, a concrete fix, and a validation test; the only minor gap is that the validation retry loop is implicit rather than an explicit numbered feedback loop.

DimensionReasoningScore

Conciseness

Lean Trigger/Fix/Why structure with no generic concept explanation; every section (the rg command, the Go fix snippet, the repo-specific rationale) earns its place and assumes Claude's competence.

5 / 5

Actionability

Fully executable guidance — a copy-paste `rg` search, a concrete Go fix line with naming/comment guidance, and a named test (TestPriorSchemasStayFrozen) with its path — covering the common case end to end.

5 / 5

Workflow Clarity

A clear sequence (widen -> rg check who calls it -> give prior version a frozen copy -> run the test) with an explicit validation checkpoint and failure diagnosis, but the fix-and-re-validate feedback loop is implied rather than spelled out as a numbered retry.

4 / 5

Progressive Disclosure

A short (<50 line), self-contained skill with no external references needed and well-organized Trigger/Fix/Why sections, qualifying for the simple-skill exception at the top of the scale.

5 / 5

Total

19

/

20

Passed

Description

73%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 has an explicit, concrete trigger and a distinct niche with near-zero conflict risk, but its "what" is somewhat narrow (describes the check rather than the full fix) and action coverage is limited to 1-2 concrete actions.

Suggestions

Expand the "what" to mention the remediation (e.g., "gives the prior version its own frozen copy") so the description conveys the full skill action, not just the check.

Add a synonym or two for discoverability (e.g., "versioned dashboard schema", "frozen snapshot") alongside the existing jargon.

DimensionReasoningScore

Specificity

Names the domain and concrete actions ("widening a shared coralogix_dashboard widget schema helper" and "Checks whether dashboard_schema/v1..v3 also use it"), but lists only 1-2 actions rather than comprehensive coverage, matching the anchor for naming a domain with 1-2 concrete actions.

3 / 5

Completeness

Both "what" ("Checks whether dashboard_schema/v1..v3 also use it; prior schemas must stay frozen") and an explicit "when" ("Use when widening a shared ... schema helper") are present, but the "what" is limited to the check rather than the full remediation, so it falls short of the fully comprehensive anchor.

4 / 5

Trigger Term Quality

Good keyword coverage for the niche — "widening a shared ... schema helper", "LineChartSchema()", "dashboard_schema/v1..v3", "prior schemas" are exactly what a developer in this repo would say, with only minor natural-term gaps.

4 / 5

Distinctiveness Conflict Risk

A clear, narrow niche tied to specific repo paths and symbols (coralogix_dashboard, dashboard_schema/v1..v3) with minimal overlap risk against other skills.

5 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
coralogix/terraform-provider-coralogix
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.