CtrlK
BlogDocsLog inGet started
Tessl Logo

creating-ai-subscription

Create a recurring AI-generated PostHog report — schedule a free-text prompt to run on a cron, with the LLM-synthesized markdown delivered to email or Slack on each tick. Use when the user wants a recurring AI summary of X on any cadence (daily, weekly, monthly, yearly) rather than a one-off report. (To attach an AI summary to an existing insight/dashboard subscription instead of a free-text prompt, see `managing-subscriptions` and its `summary_enabled` option.)

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable, well-structured skill body with concrete arguments, examples, and validation checkpoints. The main gaps are mild verbosity in the 'When to use' blockquote and reference-style rather than sequential workflow presentation.

Suggestions

Tighten the 'Prefer a dashboard or insight subscription first' blockquote and the longer Pitfalls clauses to remove repetition with the description.

Add an explicit numbered end-to-end create workflow (check gates -> gather args -> Slack 3-step if needed -> create -> verify) so the reference sections hang off a single sequence.

Consider splitting the detailed Pitfalls into a references file once the skill grows, to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

Dense and information-rich, assuming Claude knows PostHog/HogQL, but the long 'Prefer a dashboard or insight subscription first' blockquote and some explanatory clauses in Pitfalls could be trimmed.

4 / 5

Actionability

Provides exact tool names, required and optional arguments as yaml, a 3-step Slack target procedure, and two copy-paste-ready yaml examples covering the email and Slack common cases.

5 / 5

Workflow Clarity

Pre-flight gates ('stop and tell the user... re-calling the tool will not help') and an 'After it lands' verification checklist give explicit validation, but the body is reference-style sections rather than one end-to-end numbered sequence.

4 / 5

Progressive Disclosure

Well-organized into clear headers in a single ~178-line file with no external bundle references, but there is no file-splitting and the under-50-line simple-skill exception does not apply.

4 / 5

Total

17

/

20

Passed

Description

87%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 with explicit what/when guidance and good disambiguation from sibling subscription skills. It could broaden trigger synonyms and the parenthetical redirect adds mild noise, but it squarely meets the top anchors for completeness and distinctiveness.

DimensionReasoningScore

Specificity

Names the PostHog domain and concrete mechanics (schedule a free-text prompt on cron, LLM-synthesized markdown delivered to email or Slack), but it is one cohesive workflow rather than multiple distinct actions, so it stops short of comprehensive coverage.

4 / 5

Completeness

Explicitly answers both what (create/schedule/deliver an AI-generated report) and when (a 'Use when...' clause with concrete recurring-vs-one-off triggers), matching the top anchor.

5 / 5

Trigger Term Quality

Includes a natural 'Use when the user wants a recurring AI summary of X on any cadence (daily, weekly, monthly, yearly)' trigger with cadence variants, but misses common synonyms like 'scheduled report' or 'automated digest'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche and actively disambiguates from insight/dashboard subscriptions, redirecting that case to managing-subscriptions, so conflict risk with the sibling skill is minimal.

5 / 5

Total

18

/

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.