CtrlK
BlogDocsLog inGet started
Tessl Logo

dashboard-variables-v2-wire-shape

Use when expanding/flattening coralogix_dashboard variables_v2, or editing static values[].label defaults. Build typed SDK VariableV2 structs from flat TF models; wrap value/label, promql, dataprime, scope, and spans shapes.

66

Quality

78%

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 ./.claude/skills/dashboard-variables-v2-wire-shape/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 an efficient, expert-grade reference with concrete mapping rules and edge cases tightly organized. Adding an explicit validation step and one executable code example would push actionability and workflow clarity to full marks.

DimensionReasoningScore

Conciseness

Lean and dense — every bullet states a concrete mapping rule or edge case with no padding and no explanation of concepts Claude already knows.

5 / 5

Actionability

Concrete executable guidance via named SDK functions and struct shapes (e.g. ExpandDashboardUUID, SingleStringValue{Value: &StringValueLabel{...}}), though it lacks copy-paste code blocks that would fully cover common cases.

4 / 5

Workflow Clarity

Clear Fix/Why framing with edge-case checkpoints (drift, AtLeastOneOfChildren, omit→set→omit), but no explicit validate-then-retry feedback loop despite the operations touching plan/state round-tripping.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no external references needed, and well-organized into Trigger/Fix/Why sections — meeting the simple-skill exception for a clean 5.

5 / 5

Total

18

/

20

Passed

Description

71%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-scoped with an explicit trigger clause, but leans on internal/technical vocabulary that limits natural trigger-term quality. Rounding out with more user-facing phrasing would lift the trigger-term dimension.

Suggestions

Add user-facing synonyms alongside the technical terms (e.g. "dashboard query variables", "variable labels") so the trigger matches what a user would naturally say.

Move the internal file paths (variables_v2.go, dashboard_schema/variables_v2.go) out of the description and into the body, keeping the description focused on user intent.

Tighten the 'when' clause to reference the user goal (e.g. "when editing dashboard variable labels or wiring variable shapes") rather than source filenames.

DimensionReasoningScore

Specificity

Lists several concrete actions — "expanding/flattening", "build typed SDK VariableV2 structs", and wrapping value/label, promql, dataprime, scope, and spans shapes — with only minor coverage gaps relative to the comprehensive 5 anchor.

4 / 5

Completeness

Explicitly answers both what (build typed SDK structs, wrap shapes) and when ("Use when expanding/flattening..."), though the when clause is narrowly scoped to internal file paths rather than user-facing triggers.

4 / 5

Trigger Term Quality

Relevant domain terms are present ("expanding/flattening", "static values[].label") but heavily technical jargon (VariableV2, TF models) dominates and common natural variations users would actually say are missing.

3 / 5

Distinctiveness Conflict Risk

Targets a precise niche (coralogix_dashboard variables_v2 wire shape) with distinct triggers and minimal risk of firing for an unrelated skill.

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.