CtrlK
BlogDocsLog inGet started
Tessl Logo

authoring-log-alerts

Author useful, low-noise log alerts on services in a PostHog project. Use when the user asks to set up alerts for their logs, suggest alerts they should add, or evaluate whether a service is worth monitoring. Covers service triage, baseline characterisation, threshold drafting, back-testing via simulate, and shipping with a notification destination.

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

High

Do not use without reviewing

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.

The body is a tight, actionable workflow that respects Claude's intelligence while supplying exactly the domain-specific knowledge it lacks — exact tool names, a baseline-stats script, decision tables, and iteration caps with feedback loops. Bundle references are real, one level deep, and clearly signaled.

DimensionReasoningScore

Conciseness

Lean and efficient — opens with 'Authoring an alert is a measurement problem, not a guessing problem' and assumes Claude's competence; no padding or explanation of basic concepts, every section earns its place.

3 / 3

Actionability

Provides a fully executable command ('echo ... | python3 scripts/baseline_stats.py --window-minutes 5'), concrete JSON examples, exact tool names, and specific parameter values — copy-paste ready guidance.

3 / 3

Workflow Clarity

A six-step numbered workflow with explicit validation checkpoints: simulate fire_count must land in the 0–3 band, a health-flag decision table, and a hard 'three rounds then ship or skip' feedback loop for error recovery.

3 / 3

Progressive Disclosure

The body is an overview with well-signaled, one-level-deep references (threshold-defaults.md, volume-floor-alerts.md) and a helper script (baseline_stats.py) — all verified to exist as real bundle files, appropriately split out.

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.

The description is concise, specific, and uses third-person voice throughout, clearly stating what the skill does and when to invoke it with natural trigger language. It carves a distinct niche (PostHog log-alert authoring) that minimizes conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions including 'Author useful, low-noise log alerts', 'service triage, baseline characterisation, threshold drafting, back-testing via simulate, and shipping with a notification destination' — concrete verbs and specific sub-tasks rather than vague language.

3 / 3

Completeness

Clearly answers both what (authoring log alerts on PostHog services) and when (explicit 'Use when' triggers for set-up, suggestion, and evaluation requests).

3 / 3

Trigger Term Quality

The 'Use when the user asks to set up alerts for their logs, suggest alerts they should add, or evaluate whether a service is worth monitoring' clause uses natural phrasings a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Scoped to 'log alerts on services in a PostHog project' with distinct triggers, making it unlikely to fire for unrelated alerting or PostHog skills.

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.