terramate-best-practices
Terramate CLI, Cloud, and Catalyst best practices and usage guides. This skill should be used when working with Terramate stacks, orchestration, code generation, Cloud integration, or Catalyst components and bundles.
47
48%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/terramate-best-practices/SKILL.mdQuality
Discovery
75%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 is well-structured with a clear 'Use when' clause and targets a distinct niche (Terramate ecosystem), making it easy to distinguish from other skills. However, it lacks specificity in concrete actions—it describes topic areas rather than listing what the skill actually does (e.g., create, configure, deploy). Adding more natural trigger terms related to the broader IaC/Terraform ecosystem would also improve discoverability.
Suggestions
Replace 'best practices and usage guides' with specific concrete actions like 'Create and manage Terramate stacks, generate HCL code, configure orchestration pipelines, deploy Catalyst bundles'.
Add broader trigger terms that users might naturally say, such as 'infrastructure as code', 'IaC', 'Terraform orchestration', 'drift detection', or 'deployment automation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Terramate CLI, Cloud, Catalyst) and mentions some areas like stacks, orchestration, code generation, Cloud integration, and Catalyst components/bundles, but it doesn't list concrete actions (e.g., 'create stacks', 'generate HCL code', 'deploy bundles'). It reads more like a topic list than an action list. | 2 / 3 |
Completeness | The description answers both 'what' (best practices and usage guides for Terramate CLI, Cloud, and Catalyst) and 'when' with an explicit trigger clause ('This skill should be used when working with Terramate stacks, orchestration, code generation, Cloud integration, or Catalyst components and bundles'). | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Terramate', 'stacks', 'orchestration', 'code generation', 'Cloud integration', 'Catalyst', and 'bundles', which are terms users in this domain would use. However, it misses common variations and related terms like 'IaC', 'infrastructure as code', 'Terraform', 'HCL', 'drift detection', or 'deployment'. | 2 / 3 |
Distinctiveness Conflict Risk | Terramate is a specific tool ecosystem, and the description clearly scopes to Terramate CLI, Cloud, and Catalyst with distinct trigger terms like 'stacks', 'Catalyst bundles', and 'Terramate'. This is unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a table of contents pointing to rule files that are not provided in the bundle. It contains no actionable code, commands, or concrete guidance—Claude would gain almost nothing from reading it without the referenced files. The organizational structure is reasonable but the body content fails to deliver any executable or instructive value on its own.
Suggestions
Add at least 2-3 concrete, executable examples inline (e.g., a basic stack configuration block, a `terramate run` command, a `generate_hcl` snippet) so the skill provides immediate value even without the referenced rule files.
Include a quick-start workflow with explicit steps and commands (e.g., 'Create a stack: `terramate create stacks/my-stack` → Configure: add stack block → Run: `terramate run terraform init`') with validation checkpoints.
Remove or condense the 'When to Apply' section and priority table, which add little actionable value—replace with a brief one-liner scope statement and jump straight to concrete guidance.
Ensure bundle files (the referenced rule files and AGENTS.md) are actually included so the progressive disclosure structure is functional rather than pointing to missing content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is moderately efficient but includes unnecessary framing (e.g., 'Comprehensive guide for Terramate CLI, Cloud, and Catalyst, maintained by Terramate') and the 'When to Apply' section largely restates what the table of contents already conveys. The priority table and quick reference lists are useful but could be tighter. | 2 / 3 |
Actionability | The skill provides no concrete code, commands, or executable examples. It is entirely a table of contents and organizational overview, describing what rules exist rather than instructing Claude how to do anything. There are zero copy-paste-ready snippets or specific commands. | 1 / 3 |
Workflow Clarity | There are no multi-step workflows, no sequenced processes, and no validation checkpoints. The content is purely an index/catalog of rule files with no guidance on how to execute any task. | 1 / 3 |
Progressive Disclosure | The skill clearly references external rule files and an AGENTS.md compiled document, which is good structure. However, no bundle files were provided, so we cannot verify these references exist. The SKILL.md itself is almost entirely an index with very little substantive content at the top level, making it an empty shell rather than a useful overview with actionable quick-start content. | 2 / 3 |
Total | 6 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- terramate-io/agent-skills
- Commit
fb28900
- 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.