infra-cloud

Infra Cloud Agent. AWS/GCP/Azure 인프라, IaC 관리를 담당합니다.

Install with Tessl CLI

npx tessl i github:shaul1991/shaul-agents-plugin --skill infra-cloud

What are skills?

Review — 18%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

22%

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 description is too vague and lacks the specificity needed for effective skill selection. It names the domain (cloud infrastructure) but fails to list concrete actions or provide explicit trigger guidance. The Korean language mixed with English acronyms may also limit discoverability for some users.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about cloud infrastructure, deploying to AWS/GCP/Azure, Terraform, CloudFormation, or IaC configurations'

List specific concrete actions such as 'Provisions cloud resources, manages Terraform/CloudFormation templates, configures IAM policies, deploys infrastructure changes'

Include more natural trigger terms users would say: 'cloud deployment', 'terraform', 'cloudformation', 'kubernetes', 'EC2', 'S3', 'VPC', 'infrastructure as code'

Dimension	Reasoning	Score
Specificity	The description only mentions 'AWS/GCP/Azure 인프라, IaC 관리를 담당합니다' (handles AWS/GCP/Azure infrastructure, IaC management) which is vague and abstract. No concrete actions like 'provision servers', 'deploy resources', or 'manage Terraform configurations' are listed.	1 / 3
Completeness	The description weakly addresses 'what' (manages infrastructure/IaC) but completely lacks a 'when' clause or explicit trigger guidance. There is no 'Use when...' statement to help Claude know when to select this skill.	1 / 3
Trigger Term Quality	Includes some relevant keywords (AWS, GCP, Azure, IaC, 인프라/infrastructure) that users might mention, but missing common variations like 'cloud', 'terraform', 'cloudformation', 'kubernetes', 'deploy', 'provision', or specific service names.	2 / 3
Distinctiveness Conflict Risk	The mention of specific cloud providers (AWS/GCP/Azure) and IaC provides some distinctiveness, but 'infrastructure management' is broad enough to potentially overlap with DevOps, deployment, or other cloud-related skills.	2 / 3
	Total	6 / 12 Passed

Implementation

14%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill content is essentially a role description stub rather than actionable guidance. It lists responsibilities and output locations but provides zero concrete instructions, code examples, or workflows for actually performing cloud infrastructure tasks. For a domain involving potentially destructive operations (IaC, cloud resource management), the complete lack of validation steps and concrete procedures is particularly problematic.

Suggestions

Add executable code examples for common Terraform operations (e.g., init, plan, apply workflow with validation checkpoints)

Include a clear multi-step workflow with validation gates for infrastructure changes (plan review -> approval -> apply -> verify)

Provide concrete guidance on cloud provider CLI commands or IaC patterns specific to this project

Add references to detailed documentation files for each major responsibility (e.g., 'See [TERRAFORM.md](docs/infra/cloud/TERRAFORM.md) for module conventions')

Dimension	Reasoning	Score
Conciseness	The content is brief and doesn't over-explain concepts Claude knows, but it's so minimal that it borders on being a placeholder rather than efficiently conveying necessary information.	2 / 3
Actionability	No concrete code, commands, or executable guidance provided. The content only lists abstract responsibilities (Terraform/Pulumi IaC, cloud resource management) without any specific instructions on how to perform these tasks.	1 / 3
Workflow Clarity	No workflows, sequences, or validation steps are defined. For infrastructure operations which are often destructive and require careful validation, this complete absence of process guidance is a significant gap.	1 / 3
Progressive Disclosure	While output locations are mentioned, there are no references to detailed documentation, examples, or guides. The skill provides no navigation to learn more about any of the listed responsibilities.	1 / 3
	Total	5 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

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