CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

72

Quality

90%

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

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.

A high-quality operational runbook: executable commands, explicit validation checkpoints, and thorough error-recovery guidance tied to specific source locations. The only real weakness is conciseness drift in a few gotchas and the absence of any bundle-file split for progressive disclosure.

DimensionReasoningScore

Conciseness

Dense operational guidance that assumes Claude's competence (no explaining what Kafka/Django/Vite are) with every section earning its place; a few elaborated gotcha explanations could be trimmed, fitting 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

Fully executable, copy-paste-ready bash commands, JS fetch snippets, exact MCP tool-call syntax, and source paths with line numbers covering launch, readiness probes, UI driving, and diff-to-URL mapping.

5 / 5

Workflow Clarity

Clear sequences with explicit validation checkpoints (curl probes with expected HTTP codes, status-code interpretations), feedback loops via the Gotchas and Troubleshooting sections, and a 6-step numbered UI recipe; destructive ops like 'dev:reset' are explicitly gated and labeled.

5 / 5

Progressive Disclosure

Well-organized sections with one-level-deep, clearly signaled references to repo source files (paths plus line numbers) and easy navigation; scored 4 rather than 5 because all content lives in a single monolithic file with no split into bundle files.

4 / 5

Total

18

/

20

Passed

Description

87%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-structured description that clearly states what the skill does and when to use it with concrete, natural trigger phrases tied to a distinct niche. Minor room to expand trigger synonyms and sharpen the generic verb 'drive'.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Start, inspect, and drive', 'launch PostHog', 'check whether the stack is healthy', 'inspect a running process', 'verify a UI change') with only the verb 'drive' being slightly generic, so it sits at 'several specific actions; minor gaps' rather than the fully comprehensive anchor.

4 / 5

Completeness

Explicitly answers both 'what' ('Start, inspect, and drive the PostHog dev stack') and 'when' ('Use for /run and /verify... when asked to launch PostHog...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural user-facing phrases ('launch PostHog', 'check whether the stack is healthy', 'inspect a running process', 'verify a UI change against the live app') give good keyword coverage, but a few common synonyms/variations are absent, fitting 'good coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

'PostHog dev stack' is a clear niche with distinct, repo-specific triggers (/run, /verify), giving minimal conflict risk with other skills.

5 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

PostHog/posthog

Path

.agents/skills/run-posthog/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.