Name: terraform
Rating: 49.6 (1 reviews)
Author: membranedev

terraform

Terraform integration. Manage data, records, and automate workflows. Use when the user wants to interact with Terraform data.

Quality

54%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/terraform/SKILL.md

Quality

Content

60%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 delivers concrete, executable Membrane CLI commands and a clear connection-readiness workflow with polling checkpoints, but it is weighed down by an unnecessary introductory explanation of what Terraform is and a few padded asides. No bundle files are present and structure is sound.

Suggestions

Remove the opening paragraph defining Terraform/IaC and listing its typical users; Claude already knows this and it consumes context for no gain.

Trim padded phrases such as 'so you can focus on the integration logic rather than auth plumbing' and tighten the 'fastest way to get a connection' aside.

Fix the dangling 'skip to Step 2' reference by labeling the subsequent sections as explicit numbered steps so the workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	Noticeably verbose: the opening paragraph explains what Terraform/IaC is and who uses it (concepts Claude already knows), and there are padded asides like 'so you can focus on the integration logic rather than auth plumbing.'	2 / 5
Actionability	Provides mostly executable, copy-paste-ready Membrane CLI commands for install, auth, connection, polling, action list/run, and proxy requests, but no Terraform-specific action example is shown (actionIds are left as placeholders).	4 / 5
Workflow Clarity	Clear sequence (install -> auth -> connect -> poll for READY -> search -> run) with explicit state-based checkpoints and a polling feedback loop for connection readiness; minor gaps include a dangling 'Step 2' reference and no validation on action results.	4 / 5
Progressive Disclosure	Well-organized into clear section headers with no bundle files and no nested references; content is appropriately placed inline, with only minor organization gaps such as the large clientAction object description that could be tightened.	4 / 5
	Total	14 / 20 Passed

Description

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

The description names the Terraform domain and includes a 'Use when' trigger, but its capabilities are stated generically rather than as concrete Terraform actions, and the trigger phrasing ('interact with Terraform data') is imprecise. It is distinguishable but under-specified.

Suggestions

Replace the generic actions ('Manage data, records, and automate workflows') with concrete Terraform-specific operations such as provisioning infrastructure, running terraform plan/apply, and managing state and workspaces.

Sharpen the trigger to name what users actually request, e.g. 'Use when the user wants to provision resources, run terraform plan/apply, or manage Terraform state, modules, or workspaces.'

Drop the vague noun 'data' from the trigger since Terraform is about infrastructure, not data, to avoid misleading activation.

Dimension	Reasoning	Score
Specificity	Names the domain ('Terraform integration') but the actions are generic ('Manage data, records, and automate workflows') rather than concrete Terraform operations like provisioning infrastructure, running plan/apply, or managing state.	2 / 5
Completeness	It has an explicit 'Use when the user wants to interact with Terraform data' trigger, but the 'what' is vague and does not clearly describe what the integration actually does, so it falls between the clear-what and both-present anchors.	3 / 5
Trigger Term Quality	Includes the natural keyword 'Terraform' but misses common variations and synonyms users would say (IaC, infrastructure, provisioning, plan/apply, state, workspaces); 'data' and 'records' are generic noise.	3 / 5
Distinctiveness Conflict Risk	Naming the specific tool 'Terraform' gives it a clear niche with minimal conflict risk, though the generic 'manage data, records, and workflows' phrasing leaves minor overlap with other integration skills.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/terraform/SKILL.md
Commit: f484c82

Reviewed: 4 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.