CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gating-production-deploys

Use when adding or editing a GitHub Actions workflow that pushes a container image to a registry (ECR/ghcr/Docker Hub via build-push-action) or dispatches a production deploy (a `commit_state_update` repository_dispatch to PostHog/charts). Also use for adding an ordered image release for a new worker or a new consumer of the shared image. Those run from a single canonical deploy repo, gated by the CD_DEPLOY_ENABLED variable. Does NOT apply to workflows that publish GitHub releases, npm, crates, or Homebrew — those stay on the public repo.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 core gating content is exemplary — terse, decision-oriented, and copy-paste executable with named real-workflow examples. The skill is undermined by its bundle: the entire ordered-image-release section leans on a references/ordered-image-releases.md file that is absent, leaving that use case non-actionable and its dense policy prose unsupported.

Suggestions

Ship the missing references/ordered-image-releases.md (including the referenced 'bound work before activation' anchor) or inline its essential steps — the body currently directs a primary use case to a nonexistent file.

Add an explicit pre-merge validation step, e.g., verify `CD_DEPLOY_ENABLED` is set on the intended deploy repo before merging, complementing the existing `actionlint` lint guidance.

The ordered-image section uses undefined jargon ("destination frontier", "seed and consumer binding"); define these inline or ensure the restored reference introduces them before use.

DimensionReasoningScore

Conciseness

The body is lean and operational throughout — gate/don't-gate lists, the decision test ("The test is 'pushes a prod image or triggers a deploy' — not 'builds on master'"), copy-paste gate patterns, and terse policy facts like "A receipt proves the origin, not regional availability". Nothing explains concepts Claude already knows, and every token carries repo-specific information. Matches the 5 anchor; there is no padding to trim for 4.

5 / 5

Actionability

The gating guidance is fully executable — five copy-paste-ready `if:`/`push:` YAML variants covering whole-job, master-keyed, mixed PR+master, push-step, and reusable-input cases, plus named example workflows and an `actionlint` lint command. It falls short of 5 because the ordered-image-release use case (named in the description) has no executable steps in the body and defers entirely to a reference file that is missing from the bundle.

4 / 5

Workflow Clarity

A clear sequence is present: apply the decision test, pick the matching gate pattern, "Set CD_DEPLOY_ENABLED on the repo that should ship **before merging**, or master pushes skip the build/deploy", then "Lint with `actionlint`" — a concrete validation checkpoint. Minor gaps (no step verifying the variable is actually set on the target repo, no fix-and-retry loop) keep it at the 4 anchor rather than 5.

4 / 5

Progressive Disclosure

The body is well-sectioned and the reference is clearly signaled ("read [Ordered image releases](references/ordered-image-releases.md)" plus an anchor link), but the bundle contains no `references/` directory — the linked file does not exist. Since a primary use case depends on that dangling reference, navigation is broken rather than merely imprecise, matching the 2 anchor's structurally deficient organization; it is not a 3, where references are at least real but weakly signaled.

2 / 5

Total

15

/

20

Passed

Description

83%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, highly specific description with explicit trigger conditions and clear boundary exclusions. Its main weakness is that the skill's actual action (applying the CD_DEPLOY_ENABLED gate) is implied rather than stated, and a few natural synonym phrases are absent.

Suggestions

State the skill's action explicitly, e.g., "Adds the CD_DEPLOY_ENABLED repository-owner gate to image-push and deploy-dispatch steps", so the 'what' is as explicit as the 'when'.

Include a few more natural synonyms users might say, such as "docker image", "publish/push an image", or "CI/CD pipeline", alongside the existing registry names.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with precise technical detail — "pushes a container image to a registry (ECR/ghcr/Docker Hub via build-push-action)", "dispatches a production deploy (a `commit_state_update` repository_dispatch to PostHog/charts)", "adding an ordered image release for a new worker or a new consumer of the shared image" — with comprehensive coverage of the skill's scope. It exceeds the 4 anchor because there are no noticeable coverage gaps within its niche.

5 / 5

Completeness

The "when" is explicit and highly specific ("Use when adding or editing a GitHub Actions workflow that pushes a container image...", "Also use for..."), and exclusions sharpen it. The "what" is present but indirect — "gated by the CD_DEPLOY_ENABLED variable" implies the gating action without stating it — so it does not reach the 5 anchor's explicit what+when, but clearly exceeds the 3 anchor's weakly-implied trigger.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "GitHub Actions workflow", "container image", "registry", "production deploy", "Docker Hub", "build-push-action", plus explicit negative triggers. A few natural phrasings a user might say are missing (e.g., "CI/CD", "docker image", "publish image"), so it falls short of the comprehensive-synonym 5 anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche (registry image pushes and Charts deploy dispatches in the PostHog deploy-repo context) with explicit exclusions — "Does NOT apply to workflows that publish GitHub releases, npm, crates, or Homebrew" — giving distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

PostHog/posthog

Path

.agents/skills/gating-production-deploys/SKILL.md

Reviewed

Table of Contents

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.