CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

framework-set-item-modifier-reads-wrong-config

Use when a plan modifier on an attribute inside a SetNestedAttribute item reads req.ConfigValue or req.StateValue, or a set item's value turns (known after apply) with no config change.

Quality

80%

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/framework-set-item-modifier-reads-wrong-config/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 exemplary lean diagnostic skill: it captures the non-obvious root cause, the exact framework fields to use instead, and a testing recipe that reproduces the real-Terraform-only bug. The only gaps are a small time-sensitive version pin and the absence of a short code snippet for matching the configured item via req.Path.

DimensionReasoningScore

Conciseness

Nearly every token earns its place — root cause (items sorted separately, paired by index), exact fix fields (req.PlanValue, AtSetValue step of req.Path), and a source-file pointer. The pinned 'v1.17' version number is time-sensitive detail not placed in an old-patterns/deprecated section, keeping it just below the lean anchor-5 exemplar.

4 / 5

Actionability

Concrete, specific guidance throughout: 'use req.PlanValue as the prior value', 'the AtSetValue step of req.Path holds it', pointers to fwserver/attribute_plan_modification.go and setItemConfig, plus a resource.UnitTest recipe with two items. It stops short of fully executable copy-paste code for the item-matching step, which the reader must still implement.

4 / 5

Workflow Clarity

A simple single-purpose skill with an unambiguous Trigger → Fix (two sequenced bullets) → Why/verify structure; the 'Cover it with resource.UnitTest and two items' line is an explicit validation checkpoint for the fix, so the simple-skill exception applies fully.

5 / 5

Progressive Disclosure

Under 50 lines with no bundle files needed; sections are well-organized (Trigger / Fix / Why) and the single external reference ('see setItemConfig in tools/iac-codegen/.../schema.go.tmpl') is clearly signaled and one level deep.

5 / 5

Total

18

/

20

Passed

Description

65%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 concrete, distinctive trigger description that nails the 'when' but omits the 'what'. Adding a brief statement of what the skill provides (e.g., root-cause explanation and fix guidance for this framework bug) would raise completeness and specificity.

Suggestions

Add a leading 'what' clause before the 'Use when' trigger, e.g. 'Explains why SetNestedAttribute plan modifiers read the wrong item's config/state and how to fix them.'

Include the words 'Terraform' and 'framework' so users searching with those broader natural terms can find the skill.

Mention a common synonym or variation such as 'wrong config value' or 'sibling item' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Phrases like 'a plan modifier on an attribute inside a SetNestedAttribute item reads req.ConfigValue or req.StateValue' name the exact domain with concrete API identifiers, but the description lists no actions the skill itself performs — it describes only the triggering symptom, falling between the domain-only anchor and the 1-2-concrete-actions anchor.

3 / 5

Completeness

The 'Use when...' clause is explicit and highly concrete, but the description never states what the skill does — the 'what' is only implied by the described symptom. This sits between anchor 2 ('when' present without 'what') and anchor 4 (both present, 'when' could be more specific).

3 / 5

Trigger Term Quality

Strong natural terms a plugin developer would actually say: 'plan modifier', 'SetNestedAttribute', 'req.ConfigValue', 'req.StateValue', '(known after apply)', 'set item'. However 'Terraform' and 'framework' never appear and no synonyms or variations are covered, so it does not reach the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The trigger describes an extremely niche Terraform plugin-framework scenario (SetNestedAttribute plan modifiers reading ConfigValue/StateValue), a clear niche with distinct triggers and minimal conflict risk with any other skill.

5 / 5

Total

15

/

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

Path

.claude/skills/framework-set-item-modifier-reads-wrong-config/SKILL.md

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.