infrastructure-maintainer
Configures and maintains cloud infrastructure, monitoring systems, and automated operations. Sets up Prometheus/Grafana alerting, writes Terraform IaC for AWS/GCP/Azure resources, manages auto-scaling groups, load balancers, VPCs, and databases, and implements encrypted backup pipelines with S3 offload. Troubleshoots deployment failures, optimizes resource right-sizing, enforces security hardening (SOC2/ISO27001), and produces capacity planning and cost analysis reports. Use when the user asks about server setup, infrastructure provisioning, monitoring and alerting configuration, Terraform or CloudFormation, CI/CD pipeline issues, Kubernetes or container orchestration, cloud cost optimization, backup and disaster recovery, or database performance and scaling.
99
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that thoroughly covers specific capabilities, includes a comprehensive 'Use when...' clause with natural trigger terms, and clearly delineates a DevOps/cloud infrastructure niche. It uses proper third-person voice throughout and balances breadth of coverage with concrete, actionable detail. The only minor concern is that the description is quite long, but the density of useful information justifies the length.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists numerous specific concrete actions: sets up Prometheus/Grafana alerting, writes Terraform IaC, manages auto-scaling groups/load balancers/VPCs/databases, implements encrypted backup pipelines with S3 offload, troubleshoots deployment failures, optimizes resource right-sizing, enforces security hardening (SOC2/ISO27001), and produces capacity planning and cost analysis reports. | 3 / 3 |
Completeness | Clearly answers both 'what does this do' (configures cloud infrastructure, monitoring, Terraform IaC, backup pipelines, security hardening, etc.) AND 'when should Claude use it' with an explicit 'Use when...' clause listing nine distinct trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: server setup, infrastructure provisioning, monitoring and alerting, Terraform, CloudFormation, CI/CD pipeline, Kubernetes, container orchestration, cloud cost optimization, backup and disaster recovery, database performance and scaling, Prometheus, Grafana, AWS/GCP/Azure, VPCs, load balancers, SOC2/ISO27001. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear DevOps/infrastructure niche with highly specific triggers like Terraform, Prometheus/Grafana, auto-scaling groups, SOC2/ISO27001, and cloud cost optimization. While broad within the DevOps domain, the specificity of tools and compliance frameworks makes it unlikely to conflict with non-infrastructure skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality infrastructure skill that excels across all dimensions. It provides a clear, actionable workflow with explicit validation checkpoints and rollback procedures, while keeping the main file focused and delegating detailed configurations to well-described reference files. The content respects Claude's intelligence by jumping straight into executable commands and specific parameters without unnecessary explanation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Terraform, Prometheus, or AWS services are, assumes Claude's competence with these tools, and every section delivers actionable information without padding. | 3 / 3 |
Actionability | The workflow provides fully executable bash commands with specific flags, expected outputs (e.g., 'Expected: all healthy', 'Expected: empty'), and concrete tool invocations. The reference file descriptions include specific parameters like cipher algorithms, retention periods, and storage classes. | 3 / 3 |
Workflow Clarity | The 5-step infrastructure change procedure is clearly sequenced with explicit validation checkpoints (health checks after staging, post-change validation with expected outputs, monitoring verification). It includes a staged rollout pattern (staging → production) and a dedicated rollback procedure with specific commands. | 3 / 3 |
Progressive Disclosure | The skill cleanly separates concerns: the main file provides the workflow and default requirements while pointing to four well-described reference files for detailed configurations. References are one level deep and clearly signaled with descriptions of what each contains. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- OpenRoster-ai/awesome-agents
- Commit
010799b
- 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.