Skills.
Give your AI a better way to work.
A skill is a set of written instructions that teaches an AI how to do one job the way it should be done: review a pull request, plan a migration, write the release notes.
Install one here and it travels with your account into Claude, Claude Code, Cursor and every other client you sign in with.
Filter by category
52,958 results · page 50 of 1,766
- View details
triaging-error-issuesSkillDev tools
Triage PostHog error tracking issues during a daily or on-call review. Use when the user asks "what's broken?", "what new errors do we have?", "show me top errors today", "what should I look at this morning", or wants a prioritized list of active issues to work on. Surfaces new and high-impact issue
Ready to connect★ 40k
- View details
triaging-warehouse-sync-ticketsSkillDatabases & data
Debug a customer's data warehouse source, schema, or table from a support ticket, using PostHog's own production data. Use when a ticket says a warehouse table is stale, empty, stuck, duplicated, missing rows, or failing to sync, and you need the real state of the sync rather than the customer's des
Ready to connect★ 40k
- View details
triaging-web-analytics-supportSkillDatabases & data
Triage web analytics support tickets end to end: enumerate open tickets from the in-app conversations product and their Zendesk mirrors, classify each into a diagnostic shape (frontend crash, "two numbers don't match", traffic count drop, tracker not loading / undercounting vs a competitor, ad-platf
Ready to connect★ 40k
- View details
turning-engineering-analytics-into-insightsSkillDatabases & data
Converts engineering analytics (PR / CI) data into saved PostHog insights, dashboards, and subscriptions, and explains how to query the product data directly with SQL. Covers discovering per-team GitHub warehouse tables via engineering-analytics-sources, replicating curated column semantics in HogQL
Ready to connect★ 40k
- View details
understanding-billing-usageSkillMonitoring & ops
Explains PostHog billing usage and spend from the customer's visible Billing MCP tools. Use when the user asks why usage or spend is high, which product or project is driving usage, what a usage type means, how to reduce usage, what changed over time, why they got a usage change alert, or whether a
Ready to connect★ 40k
- View details
using-kea-disposablesSkillDocs & knowledge
Use when adding timers (`setInterval`, `setTimeout`), event listeners (`window.addEventListener`, `document.addEventListener`, `MediaQueryList.addEventListener`), or any other resource that needs cleanup inside a kea logic. Every logic has `cache.disposables.add(setup, key?, options?)` and `cache.di
Ready to connect★ 40k
- View details
using-redis-token-bucketsSkillDatabases & data
Use when adding a bucket-like rate limit backed by Redis: a per-caller budget with burst capacity and continuous refill, a refund path for requests that did no work, or a limit whose Retry-After must be a real wait rather than a window edge. `posthog/token_bucket.py` provides an atomic Lua token buc
Ready to connect★ 40k
- View details
validating-and-publishing-canvasesSkillDev tools
Validate and publish a canvas source project safely: the source-project shape, declared capabilities, reading the current version pointer, iterating on validation diagnostics, guarded publishing with expected_current_version_id, staging a draft build and promoting it, waiting out the queued build, a
Ready to connect★ 40k
- View details
visualizing-change-over-timeSkillDatabases & data
Helps PostHog engineers and agents pick the right chart when a request is about visualizing change over time, before/after comparisons, or period-over-period movement while building UI with @posthog/quill-charts (dashboards, reports, the mcp_analytics frontend, custom visualizations). Use when a use
Ready to connect★ 40k
- View details
warehouse-source-new-versionSkillDatabases & data
Add support for a new vendor API version to an existing Data warehouse import source, or deprecate an old one. Use when a vendor ships a new API version (Stripe date versions, Shopify quarterly versions, header-pinned revisions, /vN/ URL bumps), when implementing a version-update or deprecation task
Ready to connect★ 40k
- View details
writing-clickhouse-queriesSkillDatabases & data
Guide for writing performant ClickHouse queries in PostHog product code. Use when writing HogQL query runners, designing a ClickHouse table for a new product, adding materialized columns or skip indexes, or choosing a row ID format. For optimizing an existing query that is already too slow, use `/op
Ready to connect★ 40k
- View details
writing-code-commentsSkillDatabases & data
Gates whether a code comment should exist and forces the ones that stay to explain why, not what. Use ALWAYS before writing or editing a comment in any language (Python, TypeScript, Go, Rust, SQL), and when reviewing a diff that adds comments. Removes the comment types that clutter the codebase: nar
Ready to connect★ 40k
- View details
writing-dataclassesSkillDev tools
House rules for Python dataclasses in PostHog: when to reach for one instead of a tuple or `dict[str, Any]`, which decorator to use (`@frozen` from `posthog.dataclasses`), how to name, construct, consume and evolve them, how to keep secrets out of `repr`, and when a function should accept a dataclas
Ready to connect★ 40k
- View details
writing-evalsSkillCloud & infra
Teaches how to write and run evals on the `products/posthog_ai/eval_harness/` harness — sandboxed agent suites that execute the real coding agent in a Docker or Modal sandbox against a seeded Hedgebox project, and one-shot suites that score a single in-process model invocation per case. Use when add
Ready to connect★ 40k
- View details
writing-kea-logicsSkillFiles & storage
Guide for writing or reviewing PostHog kea logic files (`*Logic.ts` / `*Logic.tsx`). Use when creating a new logic, adding actions/reducers/selectors/listeners/loaders/forms/router bindings, choosing between reducer vs selector vs cache, deciding between listeners and `kea-subscriptions`, wiring Rea
Ready to connect★ 40k
- View details
writing-pr-descriptionsSkillDev tools
Shapes a PR body into something a reviewer understands at a glance. Use ALWAYS before writing or editing a PR description, before `gh pr create` or `gh pr edit --body`, and when asked to improve an existing description. Puts the effect a person sees in the first line and the mechanism under it, rout
Ready to connect★ 40k
- View details
writing-skillsSkillAI & models
Guide for writing PostHog agent skills — job-to-be-done templates that teach agents how to use MCP tools to achieve a goal. Use when adding new product functionality that agents should know how to work with, creating a new skill, or updating existing skills in products/*/skills/.
Ready to connect★ 40k
- View details
writing-ui-componentsSkillFiles & storage
Structure and abstraction rules for PostHog UI code — any React component or frontend file under `frontend/src/` or `products/*/frontend/`. Use ALWAYS before creating, moving, splitting, or restructuring a component or frontend file, extracting a shared/generic component, promoting a component to `l
Ready to connect★ 40k
- View details
writing-user-facing-copySkillCommunication
Sets the voice and word choices for any text a person reads in PostHog: UI labels, buttons, tooltips, empty and error states, notifications, in-app messages, onboarding, docs, and support replies. Use ALWAYS before writing or editing user-facing copy, and whenever a code change adds or changes a str
Ready to connect★ 40k
- View details
incident-runbook-templatesSkillDatabases & data
Lets your agent create incident response runbooks with step-by-step procedures, escalation paths, and recovery actions.
Ready to connect★ 40k
- View details
acquire-codebase-knowledgeSkillDocs & knowledge
Lets your agent map and document an existing codebase when you ask it to onboard you to a repo.
Ready to connect★ 39k
- View details
acreadiness-assessSkillMedia
Lets your agent score a repository's AI readiness and generate an HTML report dashboard.
Ready to connect★ 39k
- View details
acreadiness-generate-instructionsSkillFiles & storage
Lets your agent create AI instruction files like copilot-instructions.md that guide coding assistants in your repo.
Ready to connect★ 39k
- View details
acreadiness-policySkillDev tools
Helps your agent pick, write, or apply an AgentRC policy that customises readiness scoring with custom checks, weights, and thresholds.
Ready to connect★ 39k
- View details
add-educational-commentsSkillFiles & storage
Lets your agent add educational comments explaining code to a file you specify.
Ready to connect★ 39k
- View details
adobe-illustrator-scriptingSkillDocs & knowledge
Lets your agent write and debug scripts that automate Adobe Illustrator documents, layers, and artwork.
Ready to connect★ 39k
- View details
agent-governanceSkillDatabases & data
Gives your agent guidance on adding safety, access control, and governance rules to systems that call external tools.
Ready to connect★ 39k
- View details
agent-owasp-complianceSkillCloud & infra
Lets your agent check an AI agent codebase against the OWASP Agentic Security Top 10 risks.
Ready to connect★ 39k
- View details
agent-skill-stackSkillAI & models
Helps your agent find and pick the smallest set of skills needed to complete a multi-step task.
Ready to connect★ 39k
- View details
agent-supply-chainSkillFiles & storage
Lets your agent check that installed plugins and tool files haven't been tampered with by verifying checksums.
Ready to connect★ 39k
What is a skill?
A skill is plain text, usually a SKILL.md file and the scripts it refers to, written for an AI rather than for a person. It carries the steps, the house rules and the examples a good answer needs, so you stop pasting the same briefing into every new chat.
52,524 of the 52,958 skills listed here can be served through ahel today, and they come from public repositories. Each one has its own page with the instructions themselves on it, so you can read what a skill will tell your AI to do before you install it.
Install one and every AI you use gets it
Installing a skill adds it to your gateway and turns it on in the same step. Claude Code surfaces it as a slash command; any client can read the full instructions with the skill_read tool.
Nothing is copied into a project folder. The instructions are served from your account, so the same skill is there in every AI you connect, and turning it off removes it from all of them at once.