PostHog's CI writes a deploy marker into the project as an annotation every time a commit ships to an environment. These annotations are hidden_in_user_interface: true, so they don't show in the UI and are easy to forget — but they are the source of truth for "when did this go out". Always check them when staff ask about deploy timing, rather than inferring from when a metric or event volume changed (that conflates a capture change with a query/code change).
Checking Deploy Timing is a community-contributed Claude Code skill in the devops sub-category. It ships as a SKILL.md file that Claude Code auto-discovers under ~/.claude/skills/checking-deploy-timing/ and loads when your prompt matches the skill's trigger.
When to invoke it: 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.
The Checking Deploy Timing Claude Code skill is built for software engineers, backend developers, full-stack teams, and technical leads building and maintaining production systems. It's part of ClaudSkills (also referred to as Claude Skills or Claude Code Skills) — the open community-curated registry of 196,000+ SKILL.md files for Anthropic's Claude Code agent and the wider Claude ecosystem (Claude API, Claude Agent SDK).
mkdir -p ~/.claude/skills/checking-deploy-timing curl -L https://claudskills.com/skills/checking-deploy-timing/SKILL.md \ -o ~/.claude/skills/checking-deploy-timing/SKILL.md
Or just download SKILL.md directly and drop it into ~/.claude/skills/checking-deploy-timing/. Claude Code auto-discovers it on next session.
Skills live at ~/.claude/skills/checking-deploy-timing/SKILL.md on macOS/Linux, or %USERPROFILE%\.claude\skills\checking-deploy-timing\SKILL.md on Windows. See the full install guide for step-by-step instructions.
Open @claudskills_bot on Telegram, tap Open Desktop App, and the desktop app installs this skill for you. Or share the bot link with a colleague — they get the same one-tap install. Learn more →
The ClaudSkills desktop app installs any skill directly into ~/.claude/skills/ with one click — no terminal required. Pro starts at $9/mo or $149 lifetime.
For the full experience including quality scoring and one-click install features for each skill — upgrade to Pro.
SKILL.md from the source repository to ~/.claude/skills/checking-deploy-timing/SKILL.md and restart Claude Code. Both flows are detailed at claudskills.com/install/.SKILL.md file that lives under ~/.claude/skills/<name>/ and tells the Claude Code CLI agent how to perform a specific task (instructions, prompts, allowed tools). Skills are auto-discovered at session start. Checking Deploy Timing is one of 67,000+ skills indexed in the open ClaudSkills catalog, classified under the Engineering category. Learn more at /learn/what-is-a-claude-skill/.If you reference this skill in a blog post, paper, or documentation, you can cite it as:
@misc{checking-deploy-timing-2026,
author = {PostHog},
title = {Checking Deploy Timing [Claude Code skill]},
year = {2026},
publisher = {ClaudSkills},
url = {https://claudskills.com/skills/checking-deploy-timing/}
}Grade A · scanned 2026-09-28 — free static scan against the OWASP Agentic Skills Top 10.
No risk patterns were found in any of the ten OWASP-aligned categories. How grading works ›
Browse all Engineering skills in the ClaudSkills registry, or explore these other picks from the same category:
Part of Acreator Store — Adam Lankamer's AI tools: PerfectStudio · Ucaption · UTagger · AutoXPoster · TestYourSkills · AutomationFlows · Au Naturel · Telegram @acreatorstore
SKILL.md files, not affiliated with, endorsed by, or sponsored by Anthropic.