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

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) but fails to specify what the skill does or when Claude should select it. Without actionable details or a 'Use when...' clause, 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 setting up CI/CD, writing pipeline YAML, configuring GitHub Actions, Jenkins, GitLab CI, or automating deployments.'

Include common file types and tool names users would mention, such as '.yml', 'GitHub Actions', 'Jenkins', 'GitLab CI', 'Docker', 'Kubernetes deployments' to improve trigger term coverage and distinctiveness.

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 should Claude use it' clause. There are no explicit triggers or usage guidance, which per the rubric caps completeness at 2 at best, and the 'what' is too vague to even reach that level.	1 / 3
Trigger Term Quality	It includes some relevant keywords like 'deployment', 'CI/CD', and 'pipelines' that users might naturally say, but it misses common variations such as 'GitHub Actions', 'Jenkins', 'deploy', 'continuous integration', 'continuous delivery', 'build pipeline', '.yml config'.	2 / 3
Distinctiveness Conflict Risk	While 'CI/CD pipelines' narrows the domain somewhat, 'deployment automation' is broad enough to overlap with DevOps, infrastructure-as-code, container orchestration, or general automation skills.	2 / 3
	Total	6 / 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 extremely thin and provides almost no actionable guidance for deployment automation. It reads more like a placeholder or outline than a functional skill. The three steps are generic enough to apply to any software project but lack the concrete commands, tool references, validation steps, and error handling that would make this useful for CI/CD pipeline automation.

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 — e.g., verify build artifacts exist, confirm test pass rate, run a smoke test after deployment, and define rollback procedures if deployment fails.

Add environment-specific configuration examples (staging vs production) and reference supporting files for pipeline templates (e.g., `.github/workflows/deploy.yml` or `Jenkinsfile`).

Remove the generic tagline 'Automate deployments with this skill' and replace it with a brief scope statement specifying which tools, platforms, or deployment targets this skill covers.

Dimension	Reasoning	Score
Conciseness	The content is short but includes a filler phrase ('Automate deployments with this skill') that adds no value. It's not verbose, but it's also not earning its tokens since the actual content is too thin to be useful.	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 recovery, no specifics on what 'deploy to production' means, and no feedback loops for a process that involves destructive/irreversible operations (production deployment).	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 configuration examples, pipeline templates, or advanced topics. For a deployment skill, there should be references to environment configs, rollback procedures, etc.	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: 04c149c

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