CtrlK
BlogDocsLog inGet started
Tessl Logo

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). 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.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A tight, highly actionable body that gives copy-paste gating expressions, clear gate/don't-gate decision rules, real example files, and a verification step, all without padding. It is well-organized and needs no external references.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: 'Gate every such step or it publishes/deploys from the wrong place' and dense YAML patterns with no padding or explanation of concepts Claude already knows (e.g. what a workflow is). It is not score 2 because there is no unnecessary explanation to tighten.

3 / 3

Actionability

Provides copy-paste-ready executable YAML (`if: github.repository_owner == 'PostHog' && vars.CD_DEPLOY_ENABLED == 'true'`), several distinct patterns keyed to job/step/PR+master arms, named example files, and a concrete lint command (`actionlint`), matching the fully-executable anchor. It is not score 2 because the code is complete rather than pseudocode.

3 / 3

Workflow Clarity

Though not a multi-step pipeline, this single-action skill is unambiguous: explicit 'Gate these'/'Don't gate' lists, a decision test ('The test is pushes a prod image or triggers a deploy'), a pre-merge ordering note, and a verification step (lint with `actionlint`). It is not capped at 2 because a verification step is present, and the simple-skill note permits 3 for an unambiguous single action.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the ~58-line body is organized into clear sections (Gate these / Don't gate / The gate / Patterns) with no nested references, satisfying the well-organized-sections allowance for compact reference-free skills. It is not score 2 because organization is clear and content is appropriately inline rather than dumped into unnecessary files.

3 / 3

Total

12

/

12

Passed

Description

100%

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 precise, well-scoped description that states concrete actions, opens with an explicit 'Use when' trigger, and disambiguates with a negative-scope clause. It is concise, third-person, and unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: '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)', matching the anchor for multiple specific concrete actions rather than vague domain naming.

3 / 3

Completeness

Explicitly answers both what (gating container-image pushes and Charts deploy dispatches via the CD_DEPLOY_ENABLED variable) and when via an explicit 'Use when adding or editing...' clause plus a 'Does NOT apply to...' negative trigger, so it is not capped at 2 for a missing trigger clause.

3 / 3

Trigger Term Quality

Covers natural terms a user would say when editing these workflows ('GitHub Actions workflow', 'container image', 'registry', 'production deploy') plus concrete variants (ECR/ghcr/Docker Hub, build-push-action); not merely jargon but the actual phrasing of the need. It is not score 2 because coverage is broad and domain-accurate, not missing common variations.

3 / 3

Distinctiveness Conflict Risk

A sharply scoped niche (single canonical deploy repo, CD_DEPLOY_ENABLED, PostHog/charts dispatch) with an explicit exclusion list (GitHub releases, npm, crates, Homebrew) makes it unlikely to trigger for the wrong skill, matching the clear-niche anchor.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
PostHog/posthog
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.