Name: checking-deploy-timing
Rating: 76 (1 reviews)
Author: PostHog

checking-deploy-timing

Determine when a PostHog code change reached a given environment by reading the hidden GIT deploy annotations in the project and correlating them with the merge commit on GitHub. Use when PostHog staff ask "when was X deployed", "is my change live in the US/EU yet", "has my PR shipped", "did the fix roll out to prod-us", or otherwise want to know whether/when a commit, PR, or feature went out to a region. Do not answer deploy-timing questions from event/data volume alone — that only shows when data changed, not when code shipped.

Quality

93%

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

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

Tight, actionable content with executable commands and a well-validated multi-step workflow including error-recovery feedback loops. Only minor redundancy with the description's boundary guidance keeps conciseness just below perfect.

Suggestions

Trim the repeated warning about inferring timing from event/data volume (it already appears in the description) to tighten the intro paragraph and Notes.

Dimension	Reasoning	Score
Conciseness	Largely lean with executable commands and minimal padding, though the intro paragraph and the Notes repeat the description's negative guidance about event/data volume, which could be trimmed slightly.	4 / 5
Actionability	Provides copy-paste ready, fully executable commands (posthog:annotations-list, gh search prs, gh pr view, gh api compare with --jq) plus concrete annotation field examples covering the common cases.	5 / 5
Workflow Clarity	Four-step workflow is clearly sequenced with an explicit validation checkpoint (verify ancestry via behind_by) and a feedback loop (move to the next newer deploy and re-check until one passes).	5 / 5
Progressive Disclosure	A single-purpose skill under 50 lines with no external bundle files, organized into well-labeled sections (deploy annotations, Workflow, Notes), so progressive disclosure is satisfied by clear structure alone.	5 / 5
	Total	19 / 20 Passed

Description

95%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, well-scoped description that answers both what and when with concrete trigger phrases and explicit boundary guidance. Minor room to broaden the listed actions, but trigger coverage and distinctiveness are excellent.

Dimension	Reasoning	Score
Specificity	Names concrete actions ('reading the hidden GIT deploy annotations', 'correlating them with the merge commit on GitHub') within a clear domain, but coverage is limited to two actions rather than a comprehensive list.	4 / 5
Completeness	Explicitly states what the skill does (determine deploy timing via GIT annotations correlated with merge commits) and when to use it with concrete trigger phrases, plus negative boundary guidance.	5 / 5
Trigger Term Quality	Quotes multiple natural phrases users actually say ('when was X deployed', 'is my change live in the US/EU yet', 'has my PR shipped', 'did the fix roll out to prod-us') with synonym and regional variations.	5 / 5
Distinctiveness Conflict Risk	Clear narrow niche (PostHog deploy timing via hidden GIT annotations) with distinct triggers and explicit boundary guidance, minimizing overlap with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: PostHog/posthog
Path: products/posthog_ai/skills/checking-deploy-timing/SKILL.md
Commit: 5b94e47

Reviewed: about 10 hours 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.