deploy

Deployment automation skill for CI/CD pipelines

Quality

18%

Does it follow best practices?

Impact

Pending

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

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 both concrete actions and explicit trigger guidance. It names a domain (CI/CD pipelines) but fails to specify what the skill actually does or when Claude should select it. Without a 'Use when...' clause and specific capabilities, it would be difficult for Claude to reliably choose this skill from a larger set.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Generates CI/CD pipeline configurations, writes GitHub Actions workflows, configures deployment stages, and sets up automated testing 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, build automation, or .yml workflow files.'

Narrow the scope to reduce conflict risk by specifying which CI/CD platforms or deployment targets are supported (e.g., GitHub Actions, GitLab CI, AWS CodePipeline).

Dimension	Reasoning	Score
Specificity	The description names a domain ('CI/CD pipelines') but does not list any concrete actions. 'Deployment automation' is abstract and does not specify what the skill actually does (e.g., configure pipelines, trigger deployments, write YAML configs, monitor rollouts).	1 / 3
Completeness	The description weakly addresses 'what' (deployment automation) but completely lacks a 'when' clause or any explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also too vague, so this scores a 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', or specific file types like '.yml'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'CI/CD pipelines' provides some specificity, but 'deployment automation' is broad enough to overlap with infrastructure-as-code skills, DevOps configuration skills, or general automation 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 is essentially a placeholder with no actionable content. It provides three vague steps that any developer already knows without offering concrete commands, tool configurations, validation steps, or references to detailed documentation. A deployment skill should include specific CI/CD tooling, environment configuration, rollback procedures, and verification checkpoints.

Suggestions

Add concrete, executable commands or code for each step (e.g., specific build commands, test runners, deployment CLI invocations with example flags and configuration).

Include validation checkpoints and rollback procedures — e.g., health checks after deployment, how to verify success, and what to do if deployment fails.

Add references to environment-specific configuration files or detailed guides (e.g., 'See [ENVIRONMENTS.md](ENVIRONMENTS.md) for staging vs production config').

Specify which CI/CD tools or platforms are targeted (GitHub Actions, GitLab CI, etc.) and provide a concrete pipeline configuration example.

Dimension	Reasoning	Score
Conciseness	The content is short, but the opening line 'Automate deployments with this skill' is filler that adds no value. The steps themselves are lean but lack substance, so brevity here is a symptom of emptiness rather than efficiency.	2 / 3
Actionability	The steps are entirely vague and abstract — 'Build the project', 'Run tests', 'Deploy to production' provide no concrete commands, code, configuration examples, or tool-specific guidance. This describes rather than instructs.	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 'deploy to production' entails. For a deployment workflow involving destructive/production operations, this is critically insufficient.	1 / 3
Progressive Disclosure	The content is a monolithic stub with no references to detailed guides, no links to configuration files, CI/CD pipeline examples, or environment-specific documentation. There is no structure beyond a single flat list.	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
metadata_version	'metadata.version' is missing	Warning

	Total	10 / 11 Passed

Repository: andrewyng/context-hub
Commit: eeb895b

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