deployment-infrastructure

Configures deployment pipelines, manages environment variables, schedules cron jobs, applies security headers, implements caching strategies. Use when working with Docker, Vercel, AWS, Dockerfile, nginx.conf, or platform deployment configs.

Quality

86%

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

Quality

Content

85%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 tight, mostly actionable, and its release/rollback workflow is exemplary with explicit validation and a feedback loop. The main weakness is progressive disclosure: the single external reference is broken and its promised content overlaps what is already inlined.

Suggestions

Create the referenced deployment-config.md bundle file (or correct the ../../.opencastle/stack/deployment-config.md path) so the 'See ... for full architecture, env vars, cron jobs, caching headers' link resolves; it currently points to a file that does not exist.

Resolve the overlap between the inlined Environment Variables / CI/CD / Caching sections and what deployment-config.md claims to hold: keep only a concise summary in SKILL.md and move detail to the bundle, or drop the reference and treat SKILL.md as the source of truth.

Add a concrete code snippet for the Zod startup validation and a framework headers() example so the env-var and caching guidance is fully executable rather than directive.

Dimension	Reasoning	Score
Conciseness	The body is lean and dense—env-var precedence, CI stages, a Cache-Control table, and release/rollback steps are stated as directives with no concept re-explanation—so every token earns its place and Claude's competence is assumed.	5 / 5
Actionability	Concrete, copy-paste commands are present ('curl -sI https://example.com \| grep -E \'HTTP\|Strict\'', 'git revert -m 1 HEAD && git push', 'Bearer ${process.env.CRON_SECRET}') plus a ready-to-use Cache-Control table, but the Zod startup validation and framework 'headers()' configuration remain directive without executable snippets, leaving minor gaps.	4 / 5
Workflow Clarity	The release/rollback process is a clearly sequenced workflow with explicit validation checkpoints (lint+test+build exiting 0, no draft PRs, the 'curl -sI' check) and a feedback loop (rollback immediately, re-run the curl check before calling it resolved), matching the anchor-5 pattern; the destructive rollback is validated so the destructive-operation cap does not apply.	5 / 5
Progressive Disclosure	Sections are well-organized and the reference is clearly signaled at one level deep, but the sole link targets a non-existent file ('../../.opencastle/stack/deployment-config.md') and the inlined Environment Variables, CI/CD cron, and Caching content overlaps what that reference promises to hold, leaving a navigation/organization defect beyond a minor gap.	3 / 5
	Total	17 / 20 Passed

Description

88%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.

A strong description: it pairs five concrete, third-person capabilities with an explicit, platform-anchored trigger clause that clearly signals when to use the skill. The only gaps are a few missing natural synonyms and minor overlap with a sibling security skill on the headers action.

Dimension	Reasoning	Score
Specificity	Five concrete third-person verbs ('Configures deployment pipelines, manages environment variables, schedules cron jobs, applies security headers, implements caching strategies') give comprehensive coverage of the deployment domain, matching the anchor-5 example of multiple specific concrete actions.	5 / 5
Completeness	It explicitly answers both 'what' (five concrete actions) and 'when' (a concrete 'Use when working with...' trigger clause), mirroring the anchor-5 example structure exactly.	5 / 5
Trigger Term Quality	The 'Use when' clause lists natural platform and file terms ('Docker, Vercel, AWS, Dockerfile, nginx.conf, or platform deployment configs') a user would say, but omits common synonyms/verbs such as 'deploy', 'CI/CD', 'cron', and 'environment variables' as triggers, so it is good but not fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	The platform-specific triggers (Docker, Vercel, AWS, Dockerfile, nginx.conf) carve a clear deployment niche, but the 'applies security headers' action overlaps a closely related security skill the body itself defers to, so overlap risk is minor rather than absent.	4 / 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
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: monkilabs/opencastle
Path: src/orchestrator/skills/deployment-infrastructure/SKILL.md
Commit: fa0c341

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.