production-deployment

Plan, execute, and validate production deployments when rollout safety, health checks, observability, rollback, or production-parity verification is required.

Quality

77%

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/agent-ops/production-deployment/SKILL.md

Quality

Content

67%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 content is a lean, well-structured governance skill with clear sequencing and explicit validation/feedback loops, but it stays at a high-level policy register with no concrete commands or executable examples. Progressive disclosure is well-signaled despite one unverified deep legacy reference.

Suggestions

Add at least one concrete, copy-paste-ready example block (e.g., a sample deploy/health-check/rollback command template) so the guidance is executable rather than purely directive.

Tighten the Philosophy and Anti-Patterns sections by removing generic process advice that overlaps with Workflow and Constraints.

Verify the Infrastructure/references/deferred-skill-context/agent-ops-production-deployment/ path exists and resolves, or replace it with a one-level-deep reference inside the bundle.

Dimension	Reasoning	Score
Conciseness	The body is efficient terse bullets with no concept-explanation, but the Philosophy and Anti-Patterns sections contain mild generic process padding that could be trimmed, fitting "efficient; minor instances of over-explanation."	4 / 5
Actionability	The workflow gives sequenced directives ("Confirm target environment", "Identify deploy mechanism, health checks, and rollback criteria") but provides no concrete deploy, health-check, or rollback commands or templates, leaving executable specifics missing.	3 / 5
Workflow Clarity	A clear workflow sequence pairs with a dedicated Validation section containing an explicit fail-fast feedback loop ("stop at first failed gate; do not proceed until it is fixed and rerun"), but validation is sectioned separately rather than inline-gated and the steps are abstract, a minor gap below 5.	4 / 5
Progressive Disclosure	A Progressive Disclosure section signals each reference with its purpose and the three references/ files (contract.yaml, evals.yaml, task-profile.json) exist one level deep, but the legacy Infrastructure/references/deferred-skill-context/ path is deeper/external and unverified, a minor organization gap below 5.	4 / 5
	Total	15 / 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 states concrete actions, provides explicit condition-based triggers, answers both what and when, and occupies a clear production niche. Main weakness is missing natural synonyms (deploy/release/ship) in the trigger set.

Dimension	Reasoning	Score
Specificity	"Plan, execute, and validate production deployments" lists three concrete domain actions, matching the "several specific actions; minor gaps" anchor; not comprehensive enough for 5 and more than the 1-2 actions of 3.	4 / 5
Completeness	It explicitly answers what ("Plan, execute, and validate production deployments") and when ("when rollout safety, health checks, observability, rollback, or production-parity verification is required") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	"production deployments, rollout, health checks, observability, rollback, production-parity" are natural terms users say, but common synonyms (deploy, release, ship, canary) are missing, fitting the "good coverage, a few terms missing" anchor.	4 / 5
Distinctiveness Conflict Risk	The production scope plus distinct safety/rollback/observability/parity triggers carve a clear niche with minimal conflict risk against dev or generic deploy skills.	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: jscraik/Agent-Skills
Path: Skills/agent-ops/production-deployment/SKILL.md
Commit: f1f2f21

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.