Name: run-posthog
Rating: 73.6 (1 reviews)
Author: PostHog

run-posthog

Start, inspect, and drive the PostHog dev stack. Use for /run and /verify on this repo — when asked to launch PostHog, check whether the stack is healthy, inspect a running process, or verify a UI change against the live app.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

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

An information-dense, highly actionable operational skill with clear sequenced workflows, explicit validation checkpoints, and a strong error-recovery catalog. It is self-contained and well-structured; the only lever is splitting some reference material into bundle files and tightening the longest gotcha paragraph.

Suggestions

Split the Gotchas and Troubleshooting sections into a referenced reference file (e.g. references/troubleshooting.md) to shorten the main SKILL.md and lift progressive_disclosure to the top anchor.

Break the migrate-clickhouse gotcha into a short trigger line plus a numbered fix sequence to improve scanability and tighten conciseness.

Consider extracting the diff→URL mapping table into references/url-mapping.md with a one-line pointer, keeping the rule inline.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes competence — it never explains what PostHog/Django/Vite are — and nearly every sentence is non-obvious operational knowledge; a few passages (notably the migrate-clickhouse gotcha paragraph) are very dense and could be tightened.	4 / 5
Actionability	Copy-paste ready throughout: exact hogli commands, curl probes, complete JS fetch snippets for setup_test and in-page login, and named MCP tools with arguments — specific examples cover the common cases.	5 / 5
Workflow Clarity	Distinct /run and /verify flows are clearly sequenced with explicit validation checkpoints (curl probes, phrocs ready:true, data-attr hydration signal, status-code meanings) and a troubleshooting catalog that provides error-recovery feedback loops; the destructive dev:reset is flagged as a last resort.	5 / 5
Progressive Disclosure	No bundle files exist; the skill is a single well-organized SKILL.md with clear section headers and no nested references, but at ~138 lines the gotchas/troubleshooting and diff→URL reference material could arguably live in separate files.	4 / 5
	Total	18 / 20 Passed

Description

92%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, third-person description that explicitly states capabilities and concrete use triggers scoped to a specific repo. It is comprehensive on what and when; only minor synonym coverage keeps trigger quality off the top anchor.

Dimension	Reasoning	Score
Specificity	"Start, inspect, and drive the PostHog dev stack" names the domain plus multiple concrete actions, reinforced by "launch PostHog, check whether the stack is healthy, inspect a running process, or verify a UI change against the live app" — comprehensive coverage of specific actions.	5 / 5
Completeness	Explicitly answers both what ("Start, inspect, and drive the PostHog dev stack") and when ("Use for /run and /verify on this repo — when asked to launch PostHog...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural triggers are present ("launch PostHog", "check whether the stack is healthy", "inspect a running process", "verify a UI change") plus the repo's /run and /verify commands, but a few natural synonyms (debug, logs, restart) are missing.	4 / 5
Distinctiveness Conflict Risk	"PostHog dev stack" scoped to "this repo" with /run and /verify triggers is a clear niche with distinct triggers and minimal conflict risk 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: .agents/skills/run-posthog/SKILL.md
Commit: 6fca5f8

Reviewed: 3 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.