Every line is actionable (commands, env vars, ordered options); the single opening definition ('An acceptance test is a Go test function with the prefix `TestAcc`') anchors a domain-specific convention rather than explaining generic knowledge, matching anchor 3 ('every token earns its place').

Provides fully executable, copy-paste-ready commands (`go test -run=TestAccFeatureHappyPath`, `TF_ACC=1`, `-count=1`, `-v`, `TF_LOG=debug`, `TF_ACC_WORKING_DIR_PERSIST=1`), matching anchor 3; not 2 because there is no pseudocode or missing key detail.

The diagnose flow is an explicit ordered cumulative sequence, and the flip flow has a validation feedback loop ('If the test fails, then undo the edit and report a successful flip. Else...'), matching anchor 3; the editing operations carry their own verification so no cap applies.

A sub-50-line single-purpose skill with no need for external references, organized into three clearly demarcated task flows (run / diagnose / flip); the simple-skills carve-out in the scoring notes lets this score 3 without external file references.

Quotes 'Guide for running acceptance tests for a Terraform provider' — it names the domain and a single action but does not list multiple concrete actions, matching anchor 2 ('Processes PDF files and extracts content') rather than 3 ('Extract text and tables..., fill forms, merge documents').

It answers both 'what' ('Guide for running acceptance tests for a Terraform provider') and 'when' with an explicit 'Use this when...' clause, matching anchor 3; it is not 2 because the trigger is explicit, not merely implied.

'Use this when asked to run an acceptance test or to run a test with the prefix `TestAcc`' provides natural phrasings a user would actually say, including the domain-specific `TestAcc` prefix, matching anchor 3's 'good coverage of natural terms.'

The narrow niche (Terraform provider acceptance tests gated on the `TestAcc` prefix) gives distinct triggers unlikely to fire for unrelated skills, matching anchor 3.