deploy

Deployment automation skill for CI/CD pipelines

Quality

22%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./cli/test/fixtures/testskills/skills/deploy/SKILL.md

Quality

Content

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 placeholder with no actionable content. It lists three high-level steps without any concrete commands, tool references, configuration examples, or validation checkpoints. For a deployment automation skill covering CI/CD pipelines, this is critically insufficient and would not enable Claude to perform any meaningful deployment task.

Suggestions

Add concrete, executable commands or code for each step (e.g., specific build commands, test runners, deployment CLI tools like `kubectl apply`, `aws deploy`, or `docker push`).

Include validation checkpoints between steps, such as verifying test results before deploying and performing a health check after deployment with rollback instructions on failure.

Provide at least one complete example workflow for a specific deployment target (e.g., deploying a Node.js app to AWS ECS) with copy-paste ready configuration snippets.

Add references to supporting files for environment-specific configurations, rollback procedures, and secrets management guidance.

Dimension	Reasoning	Score
Conciseness	The content is short and doesn't over-explain concepts Claude knows, but the opening line 'Automate deployments with this skill' is filler that adds no value. It's brief but not because it's efficient—it's brief because it lacks substance.	2 / 3
Actionability	The steps are entirely vague and abstract with no concrete commands, code examples, configuration snippets, or specific tools mentioned. 'Build the project' and 'Deploy to production' are not actionable instructions.	1 / 3
Workflow Clarity	While three steps are listed in sequence, there are no validation checkpoints, no error handling, no feedback loops, and no specifics about what each step entails. Deploying to production is a destructive/risky operation with zero verification steps.	1 / 3
Progressive Disclosure	The content is short and not a monolithic wall of text, but there are no references to supporting files, no links to detailed guides for each step, and no bundle files to support the skill. For a deployment skill, references to configuration examples or environment-specific guides would be expected.	2 / 3
	Total	6 / 12 Passed

Description

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 generic to effectively guide skill selection. It names a broad domain (CI/CD) without specifying concrete actions, supported tools, or explicit trigger conditions. It would benefit significantly from listing specific capabilities and adding a 'Use when...' clause.

Suggestions

Add specific concrete actions, e.g., 'Generates CI/CD pipeline configurations, writes GitHub Actions workflows, configures deployment stages, sets up automated testing and build steps.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about CI/CD, deployment pipelines, GitHub Actions, Jenkins, GitLab CI, automated deployments, or build workflows.'

Include supported platforms or tools to improve distinctiveness and reduce conflict risk with other DevOps-related skills.

Dimension	Reasoning	Score
Specificity	The description is vague — 'deployment automation' and 'CI/CD pipelines' are broad domain labels without any concrete actions listed (e.g., no mention of configuring pipelines, writing YAML, deploying to specific platforms, etc.).	1 / 3
Completeness	The description weakly addresses 'what' (deployment automation) but provides no 'when' clause or explicit trigger guidance. The lack of a 'Use when...' clause caps this at 2 per the rubric, and the 'what' is also too vague, resulting in a score of 1.	1 / 3
Trigger Term Quality	It includes some relevant keywords like 'deployment', 'CI/CD', and 'pipelines' that users might naturally say, but misses common variations such as 'GitHub Actions', 'Jenkins', 'deploy', 'continuous integration', 'continuous delivery', 'build pipeline', '.yml', etc.	2 / 3
Distinctiveness Conflict Risk	While 'CI/CD pipelines' narrows the domain somewhat, 'deployment automation' is broad enough to overlap with infrastructure-as-code skills, Docker/container skills, cloud platform skills, or general DevOps skills.	2 / 3
	Total	6 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	10 / 11 Passed

Repository: andrewyng/context-hub
Commit: 67dcbeb

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