Tessl • The package manager for agent skills

SkillPublic

missing-enum-stays-null

Use when a missing enum reads as its first value, or a field with x-coralogix-presence flattens to a business value. Keep that reading on the field default.

Quality

81%

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

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.

An exceptionally lean, well-structured micro-skill that states its trigger, fix, and rationale with zero padding. Its main weakness is actionability: the fix directives rely on undefined jargon ("reading", "field line") and include no example showing what the string `default` looks like in practice, leaving a maintainer to reconstruct key details.

Suggestions

Add a short schema snippet showing the field line with the string `default` applied, plus a counterexample for a field with presence, to make the Fix copy-paste ready.

Define or replace the term "reading" (e.g., "the value the SDK returns for the field") so the directives are unambiguous to a reader without prior context.

Include a verification step, such as regenerating and confirming a missing enum round-trips as null, to close the workflow loop.

Dimension	Reasoning	Score
Conciseness	"Presence means the value was not set" is the only explanatory sentence and it encodes domain-specific semantics (x-coralogix-presence) rather than general knowledge. Three lean sections (Trigger/Fix/Why) with no padding — every token earns its place.	5 / 5
Actionability	"Put the resource's reading on the field line as a string `default`" gives concrete directives, but there is no schema snippet or example of the field line, and referents like "the resource's reading" and "that reading" are undefined — key details for execution are missing. Not 4 because the gaps are more than minor; not 2 because the guidance is specific rather than high-level hints.	3 / 5
Workflow Clarity	A simple single-purpose skill with a clear Trigger → Fix → Why structure and an explicit presence exception ("Do not apply that reading when the field has presence"). It falls short of unambiguous because "reading" is never defined and no verification step (e.g., regenerate and confirm the null round-trip) is given.	4 / 5
Progressive Disclosure	The skill is under 50 lines, needs no external references (no references/scripts/assets exist in the bundle), and is organized into clear Trigger/Fix/Why sections — per the simple-skill guideline this earns a 5.	5 / 5
	Total	17 / 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.

A highly distinctive, niche description with an explicit trigger clause and domain-precise keywords. Its weaknesses are a thin statement of what the skill actually does — one terse directive whose referent ("that reading") is unclear — and missing natural synonym variations in the trigger terms.

Suggestions

Lead with a clear statement of the action, e.g., "Keeps a missing enum reading as null and moves the resource's default onto the field line as a string `default`", so the 'what' is explicit before the trigger clause.

Add natural trigger synonyms such as "null/nil enum", "unset enum", or "enum defaults to its first value" to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	"Keep that reading on the field default" is the single stated action; the remainder is trigger conditions. The description names a precise domain ("missing enum", "x-coralogix-presence", "field default") with 1-2 concrete actions but not comprehensive coverage. Not 4 because it does not list several specific actions; not 2 because the domain is precise rather than generic.	3 / 5
Completeness	It has an explicit "Use when..." clause with two concrete trigger conditions (the when) plus "Keep that reading on the field default" (the what). Not 5 because the what is terse and its referent ("that reading") is ambiguous; not 3 because the when is explicit with concrete triggers, not weakly implied.	4 / 5
Trigger Term Quality	Multiple distinct, natural trigger phrases for this domain: "missing enum", "reads as its first value", "x-coralogix-presence flattens to a business value", "field default". Good coverage, but synonyms and variations ("null/nil enum", "defaults to the first value") are absent, so it falls between anchors 3 and 4, noticeably above the midpoint.	4 / 5
Distinctiveness Conflict Risk	"x-coralogix-presence" and "a missing enum reads as its first value" carve out a clear niche with distinct triggers; minimal risk of firing for any other skill.	5 / 5
	Total	16 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: coralogix/terraform-provider-coralogix
Path: .claude/skills/missing-enum-stays-null/SKILL.md
Revision: 8110e9e

Reviewed: 7 days ago

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.

missing-enum-stays-null

Table of Contents

Is this your skill?