acc-test-helper-client-without-provider-meta

Use when an acceptance test panics with 'interface {} is nil, not *clientset.ClientSet' in a CheckDestroy or check helper, or a helper calls testAccProvider.Meta().

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

100%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.

The body is a model of lean, high-signal skill writing: a precise trigger with the exact panic string and reproduction conditions, an executable fix snippet with error handling, and a root-cause explanation that is genuinely non-obvious. Nothing is padded, nothing is missing for the single task it covers.

Dimension	Reasoning	Score
Conciseness	Nineteen lines in a Trigger/Fix/Why structure with zero padding; every token earns its place. The 'Why' section explains a genuinely non-obvious mechanism — 'testAccProvider is the SDKv2 provider, and it is only configured once some earlier test in the same process has used it' — not a concept Claude already knows. Anchor 5.	5 / 5
Actionability	The fix is fully executable, copy-paste-ready Go with error handling ('cs, err := testAccNewClientSet() / if err != nil { return err }') and explicitly states the substitution ('instead of reading it from testAccProvider.Meta()'). Matches anchor 5; not 4 because there are no gaps for the common case — the change is a complete three-line snippet.	5 / 5
Workflow Clarity	A simple single-purpose skill where the single action — build the client in the helper instead of calling testAccProvider.Meta() — is unambiguous, so the simple-skill exception applies. No destructive or batch operation is involved, so no validation cap applies. Anchor 5.	5 / 5
Progressive Disclosure	Under 50 lines with no need for external references (the skill ships no bundle files, and nothing in the body points to any), organized into clear Trigger/Fix/Why sections. Per the under-50-lines guideline this scores 5.	5 / 5
	Total	20 / 20 Passed

Description

63%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.

An exceptionally precise trigger description — the exact panic string and function names make it both highly triggerable and highly distinctive — but it is trigger-only: it never states what the skill does, which anchors completeness at the low end and leaves specificity middling. Adding a short 'what' clause (e.g., 'Fixes the helper by building the client with testAccNewClientSet() instead of Meta()') would make it complete without sacrificing conciseness.

Suggestions

Lead with a brief capability statement before the trigger, e.g., 'Fixes Terraform acceptance-test helpers that panic because the provider Meta() is nil: build the client in the helper via testAccNewClientSet(). Use when...'.

State the remedy explicitly in the description so the skill is discoverable by what it does, not only by the error it matches.

Consider mentioning the equivalent diagnostic cue 'interface conversion' alongside the panic text, since users may paste only the first line of the panic.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete trigger conditions — 'acceptance test panics with interface {} is nil, not *clientset.ClientSet', 'CheckDestroy or check helper', 'testAccProvider.Meta()' — but lists no actions the skill performs. Anchor 3 (domain plus 1-2 concrete items, not comprehensive) fits; not 4 because no capability actions are stated at all.	3 / 5
Completeness	The 'Use when...' trigger is present and highly explicit, but the description never states what the skill does; scoring only what is explicitly stated, this matches anchor 2 ('only when is present without what'). Not 3, because there is no 'what' at all — not even a weakly implied one — and not 1 since the 'when' is concrete and specific.	2 / 5
Trigger Term Quality	Includes the exact panic string users would hit and paste, plus 'CheckDestroy', 'check helper', and 'testAccProvider.Meta()' — comprehensive natural-term coverage for this failure mode, matching anchor 5. Not lower: nothing a debugging user would say is missing.	5 / 5
Distinctiveness Conflict Risk	The exact Go panic message and SDK-specific function names carve out a clear niche with minimal overlap risk against other skills, matching anchor 5.	5 / 5
	Total	15 / 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/acc-test-helper-client-without-provider-meta/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.