deployment-engineer

Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization. Use PROACTIVELY for CI/CD design, GitOps implementation, or deployment automation.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/deployment-engineer/SKILL.md

Quality

Content

35%Weight 40%Scale 1-5

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

The body is a persona-style enumeration that restates widely-known tooling and gives high-level rather than executable guidance. It is structured but padded, with weak validation checkpoints for production-affecting workflows.

Suggestions

Trim the Capabilities/Knowledge Base/Behavioral Traits enumerations to only non-obvious guidance, or move them into a separate reference file and keep SKILL.md as a concise overview.

Add concrete, executable artifacts (sample pipeline YAML snippets, exact commands, or config templates) for the common deployment tasks instead of high-level step descriptions.

Insert explicit validation/verification checkpoints into the Instructions and Response Approach workflows (e.g., validate pipeline in staging, verify rollout health before promoting) to support the destructive/batch nature of production deployments.

Dimension	Reasoning	Score
Conciseness	Large enumeration sections (Capabilities, Knowledge Base, Behavioral Traits) restate tools and concepts Claude largely already knows (GitHub Actions, ArgoCD, Helm, Terraform), adding notable padding; below 3 because the bulk is reference-style enumeration rather than tight, efficient guidance.	2 / 5
Actionability	Guidance stays at high-level hints ('Gather release requirements', 'Design pipeline stages with quality gates', 'Implement deployment strategy with rollback') with no concrete commands, configs, or executable examples; above 1 because a recognizable step sequence exists.	2 / 5
Workflow Clarity	A coherent 4-step and 9-step sequence is present, but validation checkpoints are mostly absent or implicit except for one 'validate in staging' mention; the destructive/batch-operation cap applies, holding this at 3.	3 / 5
Progressive Disclosure	Section headers provide structure and navigability, but extensive reference-style content (Capabilities, Knowledge Base) is inlined in a single file rather than split into separate reference files; above 2 due to clear headers, below 4 due to inlined bulk.	3 / 5
	Total	10 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it concretely states capabilities, provides explicit proactive trigger guidance, and occupies a distinct niche. Minor room to add synonyms and more granular action verbs.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions (zero-downtime deployments, security scanning, GitOps) and names the domain clearly, with only minor gaps in granularity; falls short of 5 because actions like 'specializing in' and 'Masters' are high-level rather than comprehensive concrete operations.	4 / 5
Completeness	Explicitly answers both what (deployment engineer for CI/CD, GitOps, automation) and when ('Use PROACTIVELY for CI/CD design, GitOps implementation, or deployment automation') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases ('CI/CD design', 'GitOps implementation', 'deployment automation') that users would plausibly say, with good but not exhaustive coverage; below 5 because common synonyms like 'release pipeline' or 'continuous deployment' are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear deployment-engineering niche with distinct, domain-specific triggers that are unlikely to fire for unrelated skills, minimizing conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/deployment-engineer/SKILL.md
Commit: 3eff4af

Reviewed: 1 day 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.