New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Managing Subscriptions

by PostHog in PostHog/posthog-foss

Create and manage scheduled PostHog subscriptions for insight snapshots, dashboard snapshots, and AI prompt reports.

OfficialMITAuto-check passed

Install Managing Subscriptions

skills CLI
$ npx skills add PostHog/posthog-foss --skill managing-subscriptions -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install PostHog/posthog-foss managing-subscriptions --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .claude/skills && cp -r skills-src/products/subscriptions/skills/managing-subscriptions .claude/skills/managing-subscriptions && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
managing-subscriptions
GitHub stars
721
Token cost
~2.1k tokens
SKILL.md length
983 words
Files
4 (incl. references)
Skills in repo
213
Repo updated
First seen
Licence
MIT

At a glance

Create and manage scheduled PostHog subscriptions for insight snapshots, dashboard snapshots, and AI prompt reports.

  • Works in 9 steps: Call posthog:subscriptions-list and… → Select one resource type from… → Resolve the destination with… → …
  • A user wants recurring email
  • SKILL.md covers Read the relevant references, Choose the correct product, Tools and Create a subscription, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Managing Subscriptions is an agent skill from PostHog/posthog-foss, published by the product's own GitHub organization. Create and manage scheduled PostHog subscriptions for insight snapshots, dashboard snapshots, and AI prompt reports. Use when a user wants recurring email, Slack, or Microsoft Teams delivery; an AI summary; delivery history; schedule or recipient changes; a test delivery; pause, resume, or deletion; or help with subscription permissions, limits, billing, and failures. Use product alerts when delivery must depend on a threshold or anomaly.

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/destinations.md`, `references/operations.md` and `references/subscription-types.md`).

It works with PostHog, Microsoft Teams and Slack. The repository describes itself as: PostHog FOSS is a read-only mirror of PostHog, with all proprietary code removed. NOTE: This repo is synced automatically from the main PostHog repo. Please raise any issues and… The licence is MIT.

When your agent uses it

  • A user wants recurring email
  • Microsoft Teams delivery
  • Delivery history
  • Recipient changes

Example prompts

  • “/managing-subscriptions”

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Call posthog:subscriptions-list and check for a duplicate.
  2. Select one resource type from subscription-types.md.
  3. Resolve the destination with destinations.md.
  4. Resolve the schedule with operations.md.
  5. Ask whether the user wants an immediate delivery.
  6. Set send_test_now to the user's choice.
  7. Call posthog:subscriptions-create.
  8. Read the saved subscription and check each requested field.
  9. If the user approved an immediate delivery, check its delivery record.

What it can do on your machine

Read from SKILL.md and the folder at commit 2c48221. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Managing Subscriptions loads about 2.1k tokens when it runs, and up to ~5.9k if it reads all its reference files. Until then it costs about 116 tokens; SKILL.md has 983 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~116
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from PostHog/posthog-foss at commit 2c48221, republished under its MIT licence (© PostHog). 983 words, ~2,105 tokens.

Download SKILL.mdSave it as .claude/skills/managing-subscriptions/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
managing-subscriptions
description
Create and manage scheduled PostHog subscriptions for insight snapshots, dashboard snapshots, and AI prompt reports. Use when a user wants recurring email, Slack, or Microsoft Teams delivery; an AI summary; delivery history; schedule or recipient changes; a test delivery; pause, resume, or deletion; or help with subscription permissions, limits, billing, and failures. Use product alerts when delivery must depend on a threshold or anomaly.

Managing subscriptions

Subscriptions deliver product data on a fixed schedule. They support insight snapshots, dashboard snapshots, and AI prompt reports.

Read the relevant references

  • Read subscription-types.md before you select or change a resource type.
  • Read destinations.md before you create or change a destination.
  • Read operations.md for schedules, limits, billing, delivery checks, and failures.
  • Use creating-ai-subscription for the detailed prompt report creation workflow.

Choose the correct product

  • Use a subscription for fixed delivery, such as "send this dashboard every Monday."
  • Use a product alert for a condition, such as "notify me when conversion falls below 10%."
  • Use a reminder when the user wants a private prompt to inspect a resource later.
  • Use a Signals scout when an agent must decide what is important to report.

Subscriptions do not evaluate thresholds, recovery, consecutive breaches, or quiet hours. Snapshot subscriptions attempt each scheduled occurrence even when the saved results do not change.

Tools

ToolPurpose
posthog:subscriptions-listFind subscriptions
posthog:subscriptions-retrieveRead one subscription
posthog:subscriptions-createCreate a subscription
posthog:subscriptions-partial-updateChange, pause, or resume a subscription
posthog:subscriptions-test-delivery-createSend a test delivery
posthog:subscriptions-deliveries-listList delivery attempts
posthog:subscriptions-deliveries-retrieveRead one delivery
posthog:subscriptions-deleteStop all future deliveries
posthog:integrations-listFind a Slack integration
posthog:integrations-channels-retrieveFind Slack channels
posthog:dashboard-getRead dashboard tiles
posthog:insight-getResolve an insight ID

Create a subscription

  1. Call posthog:subscriptions-list and check for a duplicate.
  2. Select one resource type from subscription-types.md.
  3. Resolve the destination with destinations.md.
  4. Resolve the schedule with operations.md.
  5. Ask whether the user wants an immediate delivery.
  6. Set send_test_now to the user's choice.
  7. Call posthog:subscriptions-create.
  8. Read the saved subscription and check each requested field.
  9. If the user approved an immediate delivery, check its delivery record.

If creation times out or returns an uncertain result, list matching subscriptions before you retry. Creation is not idempotent. A blind retry can create a duplicate subscription and send a duplicate immediate delivery.

Do not infer missing recipients, channels, times, or time zones. Ask for these values before creation.

Find existing subscriptions

Use these list filters when they reduce ambiguity:

  • resource_type: insight, dashboard, or ai_prompt.
  • target_type: email, slack, or teams.
  • insight or insights: One insight ID or a comma-separated ID list.
  • dashboard: One dashboard ID.
  • dashboard_tiles: Insight subscriptions for live tiles on one dashboard.
  • created_by: One creator UUID.
Check for duplicates

Use search when the user supplied a title, insight name, dashboard name, or prompt text. Prompt subscriptions match their title and prompt text. Compare the resource, destination type, target, schedule, and enabled state.

A Teams result contains only the webhook host. One host can serve many channels. Do not use the host to identify a duplicate.

Show the title, schedule, creator, and creation date for possible Teams matches. Ask the user to select a subscription when these fields identify it. Create a new subscription when no field identifies the target channel.

Confirm the saved result

Check these fields after creation:

  • resource_type matches insight, dashboard, or ai_prompt.
  • target_type and the safe target label match the request.
  • enabled is true.
  • next_delivery_date matches the schedule and time zone.
  • The AI and delivery options match the user's choices.
Show full SKILL.md (471 more words)Show less

Change a subscription

Call posthog:subscriptions-retrieve before each update. Before an update that can send a delivery, list the current delivery IDs. Then call posthog:subscriptions-partial-update with the changed fields.

Ask before an update that can send an immediate delivery. The MCP update tool cannot suppress an immediate delivery for these changes. If the user does not approve delivery, do not make the update.

  • Set enabled: false to pause delivery.
  • Set enabled: true to resume delivery.
  • Send the complete new target when you change recipients.
  • Send target_type and target_value together when you change the destination type.
  • Omit target_value to keep a saved Teams webhook URL.
  • Send the full new Teams webhook URL when you replace it.

The resource type cannot change. Create a new subscription when the user wants a different resource type.

Check the new next_delivery_date after a schedule update. An exhausted schedule cannot resume until the user extends or removes its end condition.

After an update that sends a delivery, poll for a new target_change delivery ID. Read that delivery until it reaches a final state. Then retrieve the subscription and check its final enabled value.

Test and inspect delivery

  1. Ask for approval unless the user already requested a test.
  2. List the current delivery IDs.
  3. Call posthog:subscriptions-test-delivery-create.
  4. Poll for a new manual delivery ID.
  5. Read the new delivery when the list result needs more detail.

Wait between polls and stop after two minutes. If delivery does not reach a final state, report the last state and suggest another check later.

A test sends a real message. The tool returns 202 after it queues the delivery. It returns 409 when another test is active or the subscription is disabled.

Delivery states are starting, completed, failed, and skipped. Filter the delivery list by status when you investigate a failure. A queued workflow does not prove delivery. A completed delivery can contain partial recipient failures. The MCP tools hide per-recipient results. Do not claim that each recipient succeeded.

Stop a subscription

Confirm the subscription ID and safe destination label. Ask for approval unless the user already requested deletion or unsubscribe. Then call posthog:subscriptions-delete.

Deletion is a one-way soft delete through MCP. It stops future deliveries and frees a plan slot. Create a new subscription if the user needs it again.

Report the result

  • State the resource type, destination type, schedule, and next delivery date.
  • State whether the subscription is enabled.
  • State whether AI features can consume AI credits.
  • Do not repeat email addresses unless the user needs them for confirmation.
  • Never repeat a Teams webhook URL.
  • creating-ai-subscription: Create a report from a free-text AI prompt.
  • building-a-dashboard: Create a dashboard before you subscribe to it.
  • adding-product-alerting: Notify users when data meets a condition.
  • managing-reminders: Schedule a private prompt to inspect a resource.
  • understanding-billing-usage: Investigate PostHog AI credit use.

© PostHog, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in products/subscriptions/skills/managing-subscriptions of PostHog/posthog-foss.

  • SKILL.md
  • references/destinations.md
  • references/operations.md
  • references/subscription-types.md

Open the folder on GitHubat commit 2c48221

Compare with similar skills

Managing Subscriptions next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Managing Subscriptions compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Managing Subscriptions this skillPostHog/posthog-foss721—~2.1kAutomated safety check: PassMIT
Add Channel Setup Guidenovuhq/novu40k—~1.7kAutomated safety check: PassCustom licence
Soul Interviewldbumble/taskuary136—~1.4kAutomated safety check: PassMIT
Add Channel Whats Next Onboardingnovuhq/novu40k—~1.7kAutomated safety check: PassCustom licence
Teams App Developermicrosoft/work-iq1k—~1.8kAutomated safety check: NotesCustom licence
Taskuary Setupldbumble/taskuary136—~1.5kAutomated safety check: PassMIT

Similar skills

  • Add Channel Setup Guide

    novuhq/novu

    Add a new chat channel's layer-1 setup guide — the in-dashboard <ChannelSetupGuide that walks a developer through connecting the channel itself (create app/bot → save credentials → install/verify →…

    40k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Soul Interview

    ldbumble/taskuary

    Conduct a seven-question adaptive interview and turn the answers into Taskuary's SOUL.md.

    136 GitHub stars~1.4k tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Add Channel Whats Next Onboarding

    novuhq/novu

    Add a new chat channel's layer-2 dashboard onboarding — the connected-state "What's next" / "FOR YOUR USERS" developer-rollout guide plus its connected details page — in apps/dashboard, following…

    40k GitHub stars~1.7k tokensUpdated today
    Backend & APIsAuto-check passed

  • Teams App Developer

    microsoft/work-iq

    Official

    Build, test, and deploy code-based Teams apps using the M365 Agents Toolkit CLI.

    1k GitHub stars~1.8k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • Taskuary Setup

    ldbumble/taskuary

    Walk the owner through setting Taskuary up - the AI brain, where work arrives, the operator documents, reports and workflows - by reading the install's real state and using the screens that already…

    136 GitHub stars~1.5k tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Slack To Teams

    microsoft/work-iq

    Official

    Sub-skill of microsoft-365-agents-toolkit. An agent skill from microsoft/work-iq.

    1k GitHub starsUsed in 1 repo~2.3k tokens
    Documents & OfficeAuto-check passed

More from PostHog/posthog-foss

All 213 skills in this repo

  • Authoring Log Alerts

    PostHog/posthog-foss

    Official

    Author useful, low-noise log alerts on services in a PostHog project.

    721 GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Autoresolving PR Conflicts

    PostHog/posthog-foss

    Official

    Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…

    721 GitHub stars~4.2k tokensUpdated today
    Auto-check passed

  • Diagnosing Stacktrace Symbolication

    PostHog/posthog-foss

    Official

    Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM).

    721 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Exploring Apm Traces

    PostHog/posthog-foss

    Official

    Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.

    721 GitHub stars~3.5k tokensUpdated today
    Auto-check passed

  • Exploring LLM Traces

    PostHog/posthog-foss

    Official

    Debug and inspect LLM/AI agent traces using PostHog's MCP tools.

    721 GitHub stars~4.4k tokensUpdated today
    Auto-check passed

  • Investigate Metric

    PostHog/posthog-foss

    Official

    Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.

    721 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Works with

Questions about Managing Subscriptions

What does Managing Subscriptions do?

Create and manage scheduled PostHog subscriptions for insight snapshots, dashboard snapshots, and AI prompt reports. Managing Subscriptions is an agent skill from PostHog/posthog-foss, published by the product's own GitHub organization. Create and manage scheduled PostHog subscriptions for insight snapshots, dashboard snapshots, and AI prompt reports.

When should I use Managing Subscriptions?

Managing Subscriptions fits situations like: A user wants recurring email; microsoft Teams delivery; delivery history; recipient changes.

How do I install Managing Subscriptions in Claude Code?

Run `npx skills add PostHog/posthog-foss --skill managing-subscriptions -a claude-code`. Or copy the skill folder (products/subscriptions/skills/managing-subscriptions in PostHog/posthog-foss) into .claude/skills/managing-subscriptions in your project. Claude Code loads it when a task matches its description.

How do I install Managing Subscriptions in Codex?

Run `npx skills add PostHog/posthog-foss --skill managing-subscriptions -a codex`. Or copy the skill folder (products/subscriptions/skills/managing-subscriptions in PostHog/posthog-foss) into .agents/skills/managing-subscriptions in your project. Codex loads it when a task matches its description.

Can I use Managing Subscriptions in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PostHog/posthog-foss --skill managing-subscriptions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/managing-subscriptions, .gemini/skills/managing-subscriptions, .github/skills/managing-subscriptions and .opencode/skills/managing-subscriptions in your project.

What does Managing Subscriptions need to run?

SKILL.md names no scripts, command-line tools or credentials: Managing Subscriptions is instructions for the agent only.

Does Managing Subscriptions access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Managing Subscriptions safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Managing Subscriptions use?

Managing Subscriptions is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Managing Subscriptions use?

About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.8k tokens, read only when the agent opens those files.

What are the alternatives to Managing Subscriptions?

Skills that share tags, products or a category with Managing Subscriptions: Add Channel Setup Guide (novuhq/novu, 40k stars), Soul Interview (ldbumble/taskuary, 136 stars), Add Channel Whats Next Onboarding (novuhq/novu, 40k stars) and Teams App Developer (microsoft/work-iq, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Managing Subscriptions?

PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog-foss, which has 721 GitHub stars. The repository holds 213 skills in this directory. The repository was last updated on October 7, 2026.

Source: PostHog/posthog-foss on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.