CtrlK
BlogDocsLog inGet started
Tessl Logo

adding-product-alerting

Recommended repo-engineering guide when adding alerting to a PostHog product or extending the shared alerts platform. Routes lifecycle state machines, AlertPolicy, destinations, HogFunction dispatch, email, fixed-cadence and calendar scheduling, insight evaluation, the AlertWizard, and shared alert editor components. Use for product alert implementations, shared destination types, lifecycle or scheduling options, advanced alert settings, and platform alert infrastructure. Not for configuring alerts in an existing product.

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 well-engineered routing skill: a dense route-first decision table, a concrete invariant checklist, explicit current-limits guardrails, and clean one-level-deep references to verified bundle files. It assumes competence and avoids concept explanation padding.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — it names AlertPolicy, HogFunction dispatch, and state machines without explaining what they are — and contains no concept padding; the only mild redundancy is the reference appendix re-listing links already in the route table.

3 / 3

Actionability

Concrete, specific guidance throughout: named modules ("common/alerting/state_machine.py", "products/alerts/backend/scheduling.py"), named functions ("apply_outcome"), and a request-to-reference routing table; as an instruction-only skill the absence of copy-paste code is not penalized because the pointers are actionable.

3 / 3

Workflow Clarity

A clear sequenced entry process (the "Route first" decision table), an explicit nine-item invariant checklist, and an embedded feedback loop (invariant 4: restore the pre-check outcome when production fails) together meet the anchor for clear sequence plus validation and error recovery.

3 / 3

Progressive Disclosure

SKILL.md is a lean overview that points to four real, one-level-deep reference files (adopting-platform-alerting.md, architecture.md, extending-platform-alerting.md, frontend-alerting.md — all verified present) via two well-signaled navigation tables, splitting detail appropriately.

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 strong third-person description that states concrete capabilities, gives explicit use-for triggers, and carves out a distinct niche with a not-for exclusion. It does not pad with vague claims or over-claim.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — "Routes lifecycle state machines, AlertPolicy, destinations, HogFunction dispatch, email, fixed-cadence and calendar scheduling, insight evaluation, the AlertWizard, and shared alert editor components" — matching the anchor for enumerating specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ("Recommended repo-engineering guide ... Routes ...") and when via an explicit "Use for ..." clause, plus a "Not for ..." exclusion — clearly above the cap of 2 for missing trigger guidance.

3 / 3

Trigger Term Quality

Natural trigger phrases a PostHog engineer would actually say ("adding alerting to a PostHog product", "advanced alert settings", "lifecycle or scheduling options") appear alongside the domain-specific terms, giving good coverage.

3 / 3

Distinctiveness Conflict Risk

Narrow PostHog alerting niche with an explicit "Not for configuring alerts in an existing product" exclusion that actively disambiguates it from sibling alert skills, so conflict risk is low.

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.