CtrlK
BlogDocsLog inGet started
Tessl Logo

framework-optional-computed-nested-object

Use when Create fails with 'Received unknown value' on an Optional+Computed SingleNestedAttribute Path targeting a Go struct pointer. Model that field as types.Object.

69

Quality

84%

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.

An extremely lean, well-structured fix recipe that gets straight to the trigger, the concrete API calls, and the underlying rationale without padding. The only gap is the absence of a complete copy-paste code example and an explicit post-fix verification step.

Suggestions

Add a short copy-paste Go snippet showing the model field declaration plus the decode/flatten calls so the fix is fully executable, not just named.

Include a one-line verification cue (e.g., confirm the omitted-block create path no longer surfaces 'Received unknown value') to close the workflow with a checkpoint.

Show the matching Plan/Update-state flatten call alongside the create fix so the round-trip is covered in one place.

DimensionReasoningScore

Conciseness

The 13-line body assumes Claude's competence — no boilerplate about what HCL/Terraform is — and the only explanatory line ('Why:') conveys a non-obvious gotcha rather than generic padding, so every token earns its place.

5 / 5

Actionability

It names concrete, executable APIs ('types.Object', '.As()', '!IsNull() && !IsUnknown()', 'types.ObjectValueFrom' / 'ObjectNull') with a precise guard condition, but offers no complete copy-paste code block, leaving it just below the fully-executable anchor 5.

4 / 5

Workflow Clarity

The Fix section gives a clear ordered sequence — store as types.Object, decode conditionally, flatten — for an unambiguous single-purpose task; it lacks an explicit verification checkpoint, but the destructive/batch cap does not apply to this code-modeling fix, so it sits at 4 rather than 5.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed for this under-50-line single-task skill, which is organized into three clearly labeled sections (Trigger/Fix/Why), satisfying the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

82%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 tight, niche description that pairs an explicit, concrete trigger with an explicit fix, in the accepted third-person imperative 'Use when...' form. Its only weakness is that it describes a single corrective action rather than enumerating several.

DimensionReasoningScore

Specificity

It names the domain (Terraform framework Optional+Computed SingleNestedAttribute, Go) and one concrete action — 'Model that field as types.Object' — but does not list multiple actions, fitting the '1-2 concrete actions, not comprehensive' anchor rather than the multi-action anchor 4.

3 / 5

Completeness

It explicitly answers both — 'when' via the 'Use when Create fails with...' trigger clause and 'what' via 'Model that field as types.Object' — matching the anchor that requires concrete trigger phrases for both.

5 / 5

Trigger Term Quality

It surfaces the exact natural error text 'Received unknown value' plus the attribute and type vocabulary a provider developer would actually search for; strong keyword coverage, just shy of the comprehensive-synonym anchor 5.

4 / 5

Distinctiveness Conflict Risk

The trigger is a highly specific error condition tied to Optional+Computed SingleNestedAttribute semantics, giving it a clear niche with minimal overlap risk against other skills.

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.