posthog/posthog/creating-ai-subscription
Claude Code and agent skill by posthog/posthog
- community
Checking that the SKILL.md file is still in the repository.
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, Slack, or Microsoft Teams 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.)
Install
npx vskill@latest install posthog/posthog/creating-ai-subscriptionSKILL.md
The same SKILL.md was published earlier as posthog/posthog/creating-ai-subscription.
Creating a prompt subscription
When to use this
A subscription delivers a PostHog report to email, Slack, or Microsoft Teams on a recurring schedule. There are three kinds, distinguished by which field you set — the kind is derived and returned as the read-only resource_type:
- `insight` — periodic snapshots of one existing insight (
resource_type: "insight") - `dashboard` — periodic snapshots of a dashboard's tiles (
resource_type: "dashboard") - `prompt` — a recurring AI-generated report from a free-text prompt: an LLM
plans and runs HogQL over the project's data and synthesizes a fresh markdown report each tick (resource_type: "ai_prompt")
Use this skill for the prompt kind — i.e. when the user wants a recurring AI summary of X (on any cadence — daily, weekly, monthly, yearly) rather than a recurring snapshot of one existing insight/dashboard, or a single one-off report. Pick a prompt subscription when the value is the _analysis itself_ (the LLM deciding what to query and writing it up), not a fixed chart they already built. For an insight/dashboard subscription, set insight/dashboard instead of prompt and the AI gates below don't apply.
Prefer a dashboard or insight subscription first. A prompt subscription is theheaviest option, and the LLM composes its own HogQL, so its numbers can drift fromwhat a saved insight or dashboard already shows. Reach for it only when (a) the userspecifically asks for a free-text / AI-written report, or (b) no existing insightor dashboard covers the ask and the value really is the analysis itself. If the userwants the key numbers from an existing dashboard or insight delivered on aschedule — even phrased as "set up a scout/bot to post this daily" — adashboard (or insight) subscription with `summary_enabled: true` is usually thebetter fit. Respect a user who's sure they want a prompt subscription, but when it'sambiguous, suggest that and confirm first. Seemanaging-subscriptionsfor the happypath.
This skill covers creating the subscription. Once it exists you manage its lifecycle with the same subscriptions-* tools (see below): list it, edit/disable/ re-enable it, send a test delivery, or delete it.
Tools
| Tool | Purpose | |
|---|---|---|
posthog:subscriptions-create | Create the recurring prompt subscription | |
posthog:subscriptions-list | Confirm it landed; inspect existing subscriptions | |
posthog:subscriptions-partial-update | Edit, disable (enabled: false), or re-enable it | |
posthog:subscriptions-test-delivery-create | Send an immediate test delivery to its target(s) | |
posthog:subscriptions-delete | Soft-delete it (stops all future deliveries) | |
posthog:integrations-list | Find a Slack integration_id (filter kind=slack) | |
posthog:integrations-channels-retrieve | List a Slack integration's channels (id + name) |
What you need before calling
The endpoint enforces three create-time gates and will return 400 if any fails:
- PostHog Cloud, or `DEBUG=true` — self-hosted production deployments are not
eligible (the LLM call routes through a PostHog-managed key).
- Org-level "AI data processing approved" — must be toggled on in
Org settings → Data → AI data processing. The user must opt in to AI features for the organization first.
- Prompt subscriptions enabled for the organization — a PostHog-managed rollout
flag. If it's off, the org has not been granted access yet; tell the user to reach out to PostHog to enable it (there is no self-serve toggle).
If any of the three is missing, stop and tell the user which one to fix — re-calling the tool will not help.
Your access token also needs the `query:read` scope in addition to subscription:write: a prompt subscription runs LLM-generated HogQL over the project's data, so the backend requires query access to create, edit/re-enable, test-deliver, or delete one. A subscription:write-only token is rejected with a 403.
Required arguments
There is no resource_type argument to send — the kind is derived from which field you set (prompt ⇒ AI report) and returned as the read-only resource_type.
Optional arguments
Slack target
target_value must be <channel_id>|<channel_name> (the format the integration returns). Build it in three steps:
posthog:integrations-listfiltered bykind=slack→ pick the Slack
integration's id.
posthog:integrations-channels-retrievewith thatid→ pick a channel; it
returns each channel's id and name, which you assemble into target_value as <id>|<name>.
- Pass that integration's
idasintegration_id— the subscription is pinned
to one specific Slack integration so reconnections elsewhere don't accidentally re-route deliveries.
Slack report formatting
Prompt subscriptions send report Markdown in a Slack markdown block. Slack reads a table row only when the row starts on its own line. A pipe-separated table written as one line appears as plain text.
When a Slack report needs a table, state the column names and require a Markdown header, separator, and one data row per line. Require every row to use the same number and order of cells as the header. Put a blank line before and after the table, and do not wrap it in a code fence.
Use this shape in the prompt as a concrete example:
Keep related values in the same cell. For example, put the absolute and percentage change together in one WoW change cell. Do not add cells that have no matching header.
Teams target
target_value must be the full webhook URL of the channel you want reports in. The user adds the Workflows app to that channel, picks the template for posting to a channel when a webhook request is received, then pastes the URL back to you. A URL from a different template saves without an error, but the report never reaches the channel. There is no Teams integration to look up, so leave integration_id out.
The URL must be https. If subscriptions-create rejects target_value, the URL is not a Teams webhook — ask the user to create it again with the same template and paste the whole URL. On a later update, omit target_value to keep the saved URL, because the API reads it back as its host only and rejects that masked value.
Before creation
List matching subscriptions before you create one. Compare the prompt, title, destination, schedule, and enabled state. Prompt text and titles both match search.
Creation is not idempotent. If the create request times out or returns an uncertain result, list matching subscriptions before you retry. Do not use a masked Teams webhook host to identify a duplicate.
Ask whether the user approves an immediate delivery. Set send_test_now: false unless the user approves it.
Examples
Weekly Monday-morning AI summary by email
Daily Slack report at 9am
Pitfalls
- A Teams webhook URL is a credential. Anyone who has it can post in the channel, which is
why the API only ever returns its host. Pass it only as target_value. Do not echo it back to the user, and do not copy it into a confirmation message, a summary, or an error report.
- The kind is immutable. It's derived from which relation is set, so you can't flip an
insight or dashboard sub into a prompt sub after the fact (or vice versa) — a PATCH that adds a prompt to an insight sub is rejected. Pick the right kind at create time.
- Re-enabling a previously auto-disabled prompt sub has two preconditions, both
enforced on the PATCH: (1) a valid prompt — already persisted on the row, or a new one in the PATCH body (so bare {"enabled": true} works when the stored prompt is still valid, but is rejected when the disable cause was an invalid prompt until you supply a good one); and (2) the original creator is still an active user — if that account was deactivated the sub cannot be re-enabled at all (no prompt will help; re-create it instead).
- `next_delivery_date` is server-computed from the rrule. Don't try to set it
manually — it's read-only. The first delivery fires at the first start_date occurrence that is at least a short buffer (currently ~15 minutes) in the future, so a start_date only seconds ahead rolls to the next occurrence.
- Transient send failures retry; only permanent failures auto-disable. A
transient failure (Slack rate limit, SMTP blip, network) fails that delivery and is retried by Temporal within the run, then re-fires on the next scheduled tick — it does not auto-disable the subscription, so a persistently-failing channel will keep retrying every tick until you fix it. Only permanent/structural causes auto-disable: a disconnected Slack integration, a revoked channel permission, an invalid prompt, or revoked AI data-processing consent. (For multi-recipient email, a delivery only fails when _every_ recipient fails; partial successes still send.) Within a single delivery run the rendered markdown is cached, so Temporal retries of that run don't re-run the LLM pipeline — but each new scheduled tick generates a fresh report.
After it lands
subscriptions-list will return the new row. Confirm resource_type: "ai_prompt", enabled: true, next_delivery_date is in the future, and prompt matches what you sent. The first scheduled tick will run the planner → HogQL → synthesis pipeline and deliver the rendered markdown to the channel you chose.
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingproducts/subscriptions/skills/creating-ai-subscription/SKILL.md
Popularity
- Repository stars
- 39,987
- Repository forks
- 3,435
- 7-day trend score
- 53
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/posthog/posthog/creating-ai-subscription)