CtrlK
BlogDocsLog inGet started
Tessl Logo

normalizing-modifier-marks-computed-unknown

Use when a plan is never empty and an attribute the user never configured shows (known after apply) forever, next to a JSON/normalized attribute that shows as unchanged. Explains the framework rule and the two fixes.

68

Quality

82%

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

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.

A tight, expert debugging writeup that adds only non-obvious Terraform-framework knowledge and gives concrete named fixes with tradeoffs and an explicit pre-check. It could be slightly more actionable with a small code snippet and a post-apply verification step.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's knowledge of Terraform internals, spending tokens only on non-obvious causal mechanics ("it never checks the planned value, so a known value is overwritten too") and exact symbol names; every token earns its place with no padding.

5 / 5

Actionability

Names concrete, applicable guidance — specific modifiers ("NullWhenContentJSONManaged plans null", avoid plain "UseStateForUnknown()"), the root-fix tradeoff, and preconditions ("attributes with a Default"); not a 5 because, as an instruction-only skill, it provides no copy-paste code showing where to wire the modifier.

4 / 5

Workflow Clarity

Clear diagnostic sequence — Trigger, Cause, Fix (pick one), anti-pattern, then an explicit "Check first" checkpoint for immune attributes; not a 5 because there is no post-apply verification step confirming the diff converges.

4 / 5

Progressive Disclosure

A short (~19-line) self-contained body with well-labeled sections (Trigger, Cause, Fix, Check first) and no bundle files; per the under-50-line, no-external-references exception, well-organized sections earn a 5.

5 / 5

Total

18

/

20

Passed

Description

78%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 specific, well-triggered description that names concrete Terraform-plan symptoms and distinguishes itself sharply from other skills. Its only weakness is that the "what" side is brief and does not enumerate the two fixes it references.

DimensionReasoningScore

Specificity

Quotes concrete conditions — "attribute the user never configured shows (known after apply) forever", "JSON/normalized attribute that shows as unchanged" — naming several specific behaviors; not a 5 because "Explains the framework rule and the two fixes" enumerates neither the rule nor the fixes.

4 / 5

Completeness

Explicitly answers both: "Use when a plan is never empty..." (when, with concrete triggers) and "Explains the framework rule and the two fixes" (what); not a 5 because the what-side is terse and does not state what the two fixes are.

4 / 5

Trigger Term Quality

Uses natural diagnostic phrases a Terraform user would say — "plan is never empty", "(known after apply)", "shows as unchanged" — giving good keyword coverage; not a 5 because synonyms like "drift" or "plan keeps showing changes" are absent.

4 / 5

Distinctiveness Conflict Risk

The trigger is an extremely specific combination — plan never empty plus a never-configured attribute stuck on (known after apply) beside an unchanged normalized attribute — carving a clear niche with minimal conflict risk.

5 / 5

Total

17

/

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.