CtrlK
BlogDocsLog inGet started
Tessl Logo

managing-subscriptions

Manage PostHog subscriptions — scheduled email, Slack, or webhook deliveries of insight or dashboard snapshots, optionally with an AI-written summary attached to each delivery. Use when the user wants to subscribe to an insight or dashboard, get an AI summary attached to those deliveries, check existing subscriptions, change delivery frequency, add or remove recipients, or stop receiving updates.

72

Quality

88%

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

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 body with executable examples, a clear sequenced workflow, and thorough validation/error-handling guidance. Minor conciseness tightening and a touch more content separation would round it out.

Suggestions

Consolidate the AI-summary consent/budget caveats into one place (step 6) and reference it from the update and error-handling sections instead of restating the gates three times.

Consider trimming the 'happy path' essay to the essential decision rule plus one example sentence to reduce discursiveness.

If the happy-path comparison and parameter mapping grow further, move them into a reference file and link to it from SKILL.md to strengthen progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean — it skips explaining PostHog/Slack/subscriptions and uses tables and code blocks — but the discursive 'happy path' framing and repeated AI-summary consent caveats across three sections could be trimmed.

4 / 5

Actionability

It provides copy-paste-ready JSON for insight, dashboard, and Slack creation, a parameter-mapping table, concrete MCP tool names, and explicit defaults, fully covering the common cases.

5 / 5

Workflow Clarity

The numbered steps (1–6) include explicit validation checkpoints — verifying Slack availability before creating, duplicate checks, Slack-not-connected refusal with an email fallback, and quota/budget gates — with clear error-recovery feedback loops.

5 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-organized with clear section headers and appropriate one-level links to two sibling skills, though the inlined happy-path essay and parameter table could arguably be split out.

4 / 5

Total

18

/

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, well-structured description that clearly answers both 'what' and 'when' with concrete actions and natural trigger phrases. Its only gaps are a few missing synonyms and lack of in-description disambiguation against the related AI-subscription skill.

DimensionReasoningScore

Specificity

The description names multiple concrete actions — subscribe, attach an AI summary, check existing subscriptions, change delivery frequency, add or remove recipients, and stop updates — giving comprehensive coverage of the subscription lifecycle.

5 / 5

Completeness

It explicitly states both what the skill does ('Manage PostHog subscriptions — scheduled email, Slack, or webhook deliveries of insight or dashboard snapshots') and when to use it, with concrete trigger phrases following the 'Use when...' clause.

5 / 5

Trigger Term Quality

It surfaces natural phrases users say ('subscribe to an insight or dashboard', 'get an AI summary', 'change delivery frequency', 'stop receiving updates') but omits common synonyms like 'track', 'follow', or 'daily updates' that the body itself uses.

4 / 5

Distinctiveness Conflict Risk

'PostHog subscriptions' is a clear niche with distinct triggers, but the AI-summary trigger overlaps a sibling skill (creating-ai-subscription) that the description does not itself disambiguate.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

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.