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.

68

Quality

85%

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

81%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 well-structured, highly actionable workflow with excellent sequencing and validation feedback loops. The main weakness is that the referenced bundle files (two reference docs and the baseline_stats.py helper script) are missing, which breaks both the progressive-disclosure navigation and the executability of the core baseline step.

Suggestions

Ship the missing bundle files — at minimum scripts/baseline_stats.py (central to step 3), references/threshold-defaults.md, and references/volume-floor-alerts.md — so the referenced navigation and the baseline-threshold pipeline actually work.

If baseline_stats.py cannot be bundled, inline its percentile-to-threshold logic or give a self-contained fallback so the baseline step is executable without an external dependency.

Tighten the few emphasis/framing sentences (e.g. the opening 'measurement problem' paragraph, 'An alert with no destination is silent') to push conciseness toward fully lean.

DimensionReasoningScore

Conciseness

The body is dense and information-rich with tight decision tables and specific parameters, assuming Claude's competence throughout; only minor framing/emphasis sentences ('An alert with no destination is silent', the philosophical opener) could be trimmed, keeping it just short of fully lean.

4 / 5

Actionability

Guidance is concrete with exact tool names, parameters, default-value tables, and a copy-paste bash invocation; however the central baseline step depends on scripts/baseline_stats.py, which is referenced but not present in the bundle, leaving an execution gap that prevents a top score.

4 / 5

Workflow Clarity

A clearly sequenced six-step workflow (triage, narrow, baseline, draft & simulate, iterate, ship) with explicit validation via simulate, feedback loops driven by the fire_count and health-flag decision tables, a 3-round iteration cap, and a confirmation checkpoint before wiring to production channels.

5 / 5

Progressive Disclosure

Structure and signaling are strong — lean inline overview with clearly marked one-level-deep references to threshold-defaults.md, volume-floor-alerts.md, and baseline_stats.py — but the referenced bundle files (references/, scripts/) do not exist, so the navigation is broken rather than 'easy', capping the score below 5.

4 / 5

Total

17

/

20

Passed

Description

88%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 description that clearly states what the skill does and when to use it, with concrete domain-specific actions and natural trigger phrases. The only soft spots are slightly incomplete synonym coverage for triggers and minor overlap with related PostHog alerting skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions across the full lifecycle — 'service triage, baseline characterisation, threshold drafting, back-testing via simulate, and shipping with a notification destination' — giving comprehensive coverage rather than vague abstraction.

5 / 5

Completeness

It explicitly answers both what ('Author useful, low-noise log alerts on services in a PostHog project') and when ('Use when the user asks to set up alerts... suggest alerts... evaluate whether a service is worth monitoring') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural trigger phrases are present ('Use when the user asks to set up alerts for their logs, suggest alerts they should add'), but coverage of synonyms (e.g. 'log monitoring', 'configure/add alerts') is partial, falling just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The 'log alerts on services in a PostHog project' niche is distinct and the triggers are specific, but acknowledged sibling skills (investigating-logs, authoring-error-tracking-alerts) create minor overlap risk around generic 'set up alerts' phrasing.

4 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

14

/

16

Passed

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.