SKILLEMALL.ai

AC terraform-skill

Diagnoses and designs safe Terraform releases, provisioners (remote-exec/local-exec/file, cloud-init, Compose, Caddy), multi-environment isolation, and fresh-host bootstrap. Use when writing or reviewing plan/apply wrappers or provisioners; when staging/production config may differ; when a rollout can mutate a shared gateway; or debugging drift, TLS, container restarts, DNS duplication, or snapshot contamination.

daymade/claude-code-skills Agent Skills author: daymade MIT 6 files · 1 script body ≈ 4 807 tokens Open the sourcegithub.com↗ analyzed 33 h ago

Diagnoses and designs safe Terraform releases, provisioners (remote-exec/local-exec/file, cloud-init, Compose, Caddy), multi-environment isolation, and…

As a process C 56/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

AnalyzerTerraformDockerPostgreSQLCloudflareInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
88
Run on models
none yet
Process rating
C
56/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
30
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 56/100

    • 0Result and completion. Does not say what the result is
    • 30Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 45 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 70Execution cost. Instruction body is 4807 tokens
    • 100Steps. 16 steps
    • 100Consistency. Name and required fields are in place
    • 100Progress reporting. Reports progress

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 416: enough signal without eating the budget
    • +4Structure: 20 headings
    • +3Step-by-step instructions: 16 items
    • +4Has examples (15 code blocks)
    • +4Reference files are cited in the instructions (4 of 4)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.