CtrlK
BlogDocsLog inGet started
Tessl Logo

authoring-error-tracking-alerts

Author error tracking alerts that fire when an issue is created, reopened, or starts spiking. Use when the user asks to set up error notifications, route exceptions to Slack/webhook/Linear, or evaluate which error events are worth alerting on. Covers trigger-event selection, integration choice, dedup against existing alerts, and shipping with the canonical message body shape.

73

Quality

90%

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

92%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 skill body with a clear multi-step workflow, explicit validation/confirmation checkpoints, and clean one-level-deep references to real bundle files. The main residual is minor wording tightening, not structural gaps.

DimensionReasoningScore

Conciseness

The body is largely lean and assumes Claude's competence — tool tables, trigger trade-offs, and a copy-paste JSON payload earn their tokens — with only minor passages (e.g. explaining 'Multiple alerts on the same event for the same channel produce duplicate Slack messages — the user almost never wants this') that could be tightened.

4 / 5

Actionability

Provides a fully executable create-call JSON payload, concrete MCP tool names with their job, exact filter property shapes ($exception_issue_id, $exception_types), and copy-verbatim block templates — copy-paste ready guidance covering the common cases.

5 / 5

Workflow Clarity

A clearly sequenced 5-step workflow with explicit validation checkpoints: confirm intent before creating, dedupe against existing alerts (stop if duplicate), verify-after-create step, plus feedback guidance (use partial-update or skip on conflict). The destructive/batch cap is satisfied since batch-create is explicitly forbidden and confirmation precedes each create.

5 / 5

Progressive Disclosure

SKILL.md is an overview with well-signaled one-level-deep references to real bundle files ([references/block-templates.md] and [references/event-triggers.md]) for the bulk detail; both referenced files exist, so navigation is clean and appropriately split.

5 / 5

Total

19

/

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, concrete description that names specific actions, destinations, and trigger events with an explicit 'Use when' clause. It is sharply scoped to error tracking alerts and avoids vague fluff, with only minor room for additional casual trigger synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'set up error notifications', 'route exceptions to Slack/webhook/Linear', 'trigger-event selection', 'integration choice', 'dedup against existing alerts', 'shipping with the canonical message body shape' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers 'what' (author error tracking alerts that fire on created/reopened/spiking) and 'when' via a clear 'Use when the user asks to set up error notifications, route exceptions..., or evaluate which error events are worth alerting on' clause.

5 / 5

Trigger Term Quality

Natural user phrases like 'set up error notifications' and 'notify me when this happens' are well represented, and destinations (Slack/webhook/Linear) are named, but it leans slightly technical and omits a few casual synonyms a user might say; just short of fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

The 'error tracking alerts' niche with specific trigger events and routing targets (Slack/webhook/Linear) is clearly distinct and unlikely to collide with adjacent skills; scope is sharply bounded.

5 / 5

Total

19

/

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.

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.