framework-import-dynamic-attributes

Use when a Terraform Plugin Framework resource import reads required DynamicAttribute values. Handle imported partial state before converting dynamic values.

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

80%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, well-organized instruction skill that assumes Claude's competence and gives specific, executable guidance. The only real gap is workflow clarity: overwriting imported state is a state-mutating operation that would benefit from an explicit validation checkpoint.

Suggestions

Add an explicit validation checkpoint in the Fix, e.g. 'Only overwrite fetched state with prior dynamic state after confirming the prior value is known; otherwise keep the fetched value.'

Include a short copy-paste Go snippet showing the null/unknown/zero-value check and conditional overwrite in the Read function to raise actionability from instruction-only to fully executable.

Clarify the recovery path when the backend read fails to populate the dynamic value (skip overwrite vs. error out) so the workflow has a feedback loop.

Dimension	Reasoning	Score
Conciseness	Lean body with no padding and no explanation of concepts Claude already knows; every line (Trigger/Fix/Why) earns its place. Not below 5 because there is no unnecessary explanation to trim.	5 / 5
Actionability	Concrete, specific instruction naming the `Read` function, exact value states (null/unknown/zero-value), and a precise conditional overwrite rule. Not a 5 because it is instruction-only with no copy-paste executable code; not a 3 because the guidance is far more specific than pseudocode.	4 / 5
Workflow Clarity	A single sequenced rule ('In Read, treat ... as absent ... fetch backend values, and only overwrite ... when the prior value is known') with an implicit guard but no explicit validation checkpoint or error-recovery loop. Capped at 3 per the destructive/batch-operation rule, since overwriting Terraform state is state-mutating and lacks an explicit validate step.	3 / 5
Progressive Disclosure	A simple under-50-line skill with no external bundle files (references/scripts/assets absent) and clearly labeled Trigger/Fix/Why sections, matching the simple-skill exception for a 5. Not below 5 because organization is clean and no nested references exist.	5 / 5
	Total	17 / 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 focused, well-scoped description that explicitly pairs a concrete 'Use when...' trigger with the action it performs. Trigger-term and completeness are strong; only specificity trails slightly because the description front-loads two of several concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('Terraform Plugin Framework resource import') and two concrete actions ('Handle imported partial state', 'before converting dynamic values'), but coverage is not comprehensive — the overwrite-only-when-known nuance lives in the body, not the description. Not a 4 because the listed actions are limited and leave minor coverage gaps.	3 / 5
Completeness	Explicitly answers both 'what' ('Handle imported partial state before converting dynamic values') and 'when' ('Use when a Terraform Plugin Framework resource import reads required DynamicAttribute values') with a concrete trigger phrase. Not below 5 because the 'when' clause is specific and explicit rather than vague or merely implied.	5 / 5
Trigger Term Quality	Good natural keyword coverage ('Terraform', 'import', 'resource', 'Plugin Framework', 'DynamicAttribute', 'dynamic values') that a plugin developer would actually say. Not a 5 because it omits common synonyms/variants a user might phrase (e.g. 'state', 'schema', 'attribute').	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (framework resource import with required DynamicAttribute) with distinct triggers and minimal overlap with other skills. Not below 5 because the combination of 'Plugin Framework', 'import', and 'required DynamicAttribute' is highly specific.	5 / 5
	Total	17 / 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/framework-import-dynamic-attributes/SKILL.md
Commit: d49bc4c

Reviewed: 5 days ago

Table of Contents

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.