CtrlK
BlogDocsLog inGet started
Tessl Logo

terraform-tfvars

Creates the terraform.tfvars file for the Buildkite build agent Terraform stack. Documents how to retrieve the Buildkite agent token from Buildkite UI (via Chrome DevTools MCP) and AWS SSM Parameter Store, validate tokens, and populate the tfvars file. Use when users say "create tfvars", "set up terraform variables", "deploy buildkite agents", "configure buildkite token", or need to recreate the terraform.tfvars after a fresh checkout.

73

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 strong, highly actionable body: complete executable commands, a validation-rich workflow with an explicit token-comparison decision tree, and project-specific details Claude could not infer. Its main weakness is redundancy — critical warnings are repeated two to three times each, which inflates token cost without adding information.

Suggestions

State the 'NEVER commit terraform.tfvars' warning once (e.g., in the Security Reminders section) and reference it elsewhere rather than repeating it in the intro, the HCL comment, and the reminders list.

Consolidate the min_size = 0 requirement into the variable-reference table (or the cost-check section) instead of fully explaining the cost rationale in both places.

Drop the DYLD_LIBRARY_PATH/AWS_CA_BUNDLE export lines from the SSM snippet since the run.sh wrapper section already documents those workarounds, keeping only what the raw command needs.

DimensionReasoningScore

Conciseness

Mostly efficient and rich in project-specific detail, but the 'NEVER commit' warning appears three times (intro, HCL comment, Security Reminders), the min_size=0 cost rationale is given twice in full, and the DYLD_LIBRARY_PATH/AWS_CA_BUNDLE exports duplicate what run.sh already handles — clearly tightening material beyond 'minor'.

3 / 5

Actionability

Every step ships copy-paste-ready commands: the full aws ssm get-parameter invocation, cp from the example template, a grep min_size check, a concrete HCL snippet, ./run.sh apply, and terraform output; Chrome MCP steps name the actual tools to call.

5 / 5

Workflow Clarity

A clearly sequenced retrieve → validate → create → verify → deploy → verify workflow with explicit validation checkpoints: a match/differ/fails decision tree for tokens, the grep min_size guard, plan review before confirming, and post-deploy verification steps.

5 / 5

Progressive Disclosure

Well-organized single-file skill whose only references are real repo files (terraform.tfvars.example, variables.tf, run.sh) and the browser-auth skill; however, at ~157 lines everything is inline and the variable-reference table and security reminders could live in a separate reference file, so it fits the 'minor organization gaps' anchor rather than a fully split structure.

4 / 5

Total

17

/

20

Passed

Description

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

Excellent description: concrete third-person action statements, an explicit 'Use when' clause with five natural trigger phrases including the exact filename, and a highly specific niche that eliminates conflict risk. It is a model of the top-anchor pattern from the rubric's good examples.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with named technologies — 'Creates the terraform.tfvars file', 'retrieve the Buildkite agent token from Buildkite UI (via Chrome DevTools MCP) and AWS SSM Parameter Store', 'validate tokens', 'populate the tfvars file' — comprehensively covering the task with no observable gaps.

5 / 5

Completeness

Explicitly answers both 'what' (create/retrieve/validate/populate) and 'when' ('Use when users say...') with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Five natural multi-word trigger phrases ('create tfvars', 'set up terraform variables', 'deploy buildkite agents', 'configure buildkite token', 'recreate the terraform.tfvars after a fresh checkout') plus the exact filename — phrases users would actually say.

5 / 5

Distinctiveness Conflict Risk

A clear niche (Buildkite build agent Terraform stack, terraform.tfvars, agent token) with distinctive triggers that virtually no other skill would claim; minimal conflict risk.

5 / 5

Total

20

/

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
mock-server/mockserver-monorepo
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.