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.
Category: Dev tools
16,378 results · page 9 of 546
- View details
binanceSkillDev tools
Lets your agent trade crypto on Binance, including spot and futures orders, wallet checks, and currency conversions.
Ready to connect★ 44k
- View details
meme-rushSkillDev tools
Lets your agent track brand-new and trending meme token launches and hot market topics on launchpads like Pump.fun.
Ready to connect★ 44k
- View details
new-exchangeSkillDev tools
Scaffolds a new crypto exchange integration in TypeScript for the CCXT library, following its certified template.
Ready to connect★ 44k
- View details
query-address-infoSkillDev tools
Lets your agent look up all tokens held by a crypto wallet, with prices and 24h changes.
Ready to connect★ 44k
- View details
i-have-adhdSkillDev tools
Lets your agent format answers for ADHD readers: next action first, numbered steps, clear time estimates.
Ready to connect★ 39k
- View details
clerk-nextjs-patternsSkillDev tools
Guides your agent to write Next.js code with Clerk authentication using middleware, Server Actions, and caching patterns.
Ready to connect★ 71
- View details
adding-ingestion-warningsSkillDev tools
How to add a new ingestion warning type to the event ingestion pipeline. Use when emitting a new warning from nodejs ingestion code (emitIngestionWarning, captureIngestionWarning, pipeline `warnings` arrays, `drop()` with warnings), when adding a warning type, category, or severity, or when a typech
Ready to connect★ 40k
- View details
adding-project-secret-api-key-authSkillDev tools
How to gate a PostHog API endpoint with project secret API key (PSAK) auth — a project-scoped, user-less service credential. Use when adding PSAK support to a viewset action, allowing a new scope for PSAKs, handling synthetic users (ProjectSecretAPIKeyUser), or choosing PSAK-aware rate throttles. Tr
Ready to connect★ 40k
- View details
analyzing-experiment-query-performanceSkillDev tools
Pull and interpret production experiment query-performance data from the staff-only `/api/debug_ch_queries` endpoints backing the `/experiments/staff` scene: slowest experiment queries, precompute read/build health, and preaggregation cache footprint. Covers prod-US and prod-EU via a `query_performa
Ready to connect★ 40k
- View details
analyzing-experiment-session-replaysSkillDev tools
Analyze session replay patterns across experiment variants to understand user behavior differences. Use when the user wants to see how users interact with different experiment variants, identify usability issues, compare behavior patterns between control and test groups, or get qualitative insights
Ready to connect★ 40k
- View details
auditing-endpointsSkillDev tools
Audit every endpoint in a PostHog project for staleness, failed materialisations, and unused materialised versions. Use when the user asks "what endpoints can I clean up?", "are any of my endpoints broken?", "which materialised versions are still being called?", or wants a one-shot cleanup pass over
Ready to connect★ 40k
- View details
authoring-ci-workflowsSkillDev tools
Use when adding or editing a GitHub Actions workflow, composite action, or reusable workflow under `.github/` — new CI jobs, triggers, matrices, checkout/clone tuning, action pinning, GitHub App token auth, concurrency groups, `timeout-minutes`, `paths` filters, caching, or runner choice. Covers Pos
Ready to connect★ 40k
- View details
building-product-empty-statesSkillDev tools
Guide for adding a product setup empty state — the skippable first-run screen a product scene shows until real data arrives, built on the shared ProductEmptyState component. Use when adding an empty state or first-run/setup screen to a product scene, declaring `emptyState` on a `SceneExport`, writin
Ready to connect★ 40k
- View details
cleaning-up-stale-feature-flagsSkillDev tools
Identify and clean up stale feature flags in a PostHog project. Use when the user wants to find unused, fully rolled out, or abandoned feature flags, review them for safety, and then disable or delete them. Covers staleness detection, dependency checking, and safe removal workflows.
Ready to connect★ 40k
- View details
configuring-experiment-rolloutSkillDev tools
Configures the rollout shape of a PostHog experiment — the variant split (50/50, 80/20, A/B/C ratios), the overall rollout percentage that gates how many users enter the experiment, and the disambiguation when a percentage like "roll out to 25%" could mean either. Use when the user mentions a rollou
Ready to connect★ 40k
- View details
consuming-endpoints-from-client-codeSkillDev tools
Wire a PostHog endpoint into a client app or SDK. Covers fetching the OpenAPI spec, generating a typed client with openapi-generator or @hey-api/openapi-ts, sending the right auth header, shaping the variables payload (HogQL code_name vs insight breakdown property), handling rate-limit and materiali
Ready to connect★ 40k
- View details
copying-endpoints-across-projectsSkillDev tools
Copy a PostHog endpoint (a saved HogQL/insight query exposed as an API route) to another project in the same organization, or duplicate it under a new name in the same project. Use when the user wants to duplicate an endpoint, promote an endpoint from staging to production, replicate an endpoint's q
Ready to connect★ 40k
- View details
creating-an-endpointSkillDev tools
Create a PostHog endpoint with the right shape on the first try — covers query kind choice, name conventions, what to expose as variables (HogQL code_name vs insight breakdown), data_freshness_seconds, and whether to materialise on day one. Use when the user says "create an endpoint", "expose this q
Ready to connect★ 40k
- View details
debugging-ci-failuresSkillDev tools
Debugs failing GitHub Actions CI runs for PostHog PRs, commits, and branches, and answers broad CI-health questions ("is CI red?", "is master green today?", "what's broken right now?"). Use when the user asks why CI is red, asks for the current CI or master status, or mentions a failing check, GitHu
Ready to connect★ 40k
- View details
debugging-experimentsSkillDev tools
Debug and support PostHog Experiments (A/B tests) for a customer looking at their own results. Use whenever an experiment support ticket is pasted or a customer asks a results question, most commonly "why aren't my exposures even?", "why is one variant getting no traffic?", "why am I missing / seein
Ready to connect★ 40k
- View details
depot-ciSkillDev tools
Configures and manages Depot CI, a drop-in replacement for GitHub Actions that runs workflows entirely within Depot. Use when migrating GitHub Actions workflows to Depot CI, running `depot ci migrate`, managing Depot CI secrets and variables, running workflows with `depot ci run`, debugging Depot CI
Ready to connect★ 40k
- View details
depot-github-runnersSkillDev tools
Configures Depot-managed GitHub Actions runners as a drop-in replacement for GitHub-hosted runners. Use when setting up or migrating GitHub Actions workflows to use Depot runners, choosing runner sizes (CPU/RAM), configuring runs-on labels, setting up ARM or Windows or macOS runners, troubleshooting
Ready to connect★ 40k
- View details
diagnosing-endpoint-performanceSkillDev tools
Diagnose why a PostHog endpoint is slow or expensive and propose a concrete fix — bump the cache TTL, enable materialisation, restructure variables, or rewrite the query. Use when the user says "this endpoint is slow", "my endpoint times out", "we're hitting the cost cap on this one", or asks "shoul
Ready to connect★ 40k
- View details
diagnosing-stacktrace-symbolicationSkillDev tools
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). The PostHog symbol-set lookup flow is universal across platforms; build-tool and artifact details live in p
Ready to connect★ 40k
- View details
django-startup-timeSkillDev tools
Keep heavy imports off the django.setup() path that every process (web, celery, temporal, migrate, shell, CI) pays for. Use when touching AppConfig.ready(), wiring signal receivers, editing the lazy API router (posthog/api/rest_router.py or its __init__.py shim), deferring a heavy import, when the s
Ready to connect★ 40k
- View details
extending-personhog-test-harnessSkillDev tools
When and how to add scenarios, chaos events, and invariants to the personhog e2e test harness (rust/personhog-test-harness). Use after fixing a bug or regression in the personhog leader path (leader, router, writer, replica, coordination protocol) so the fix gets a permanent regression scenario; whe
Ready to connect★ 40k
- View details
grouping-noisy-errorsSkillDev tools
Consolidate PostHog error tracking issues that are the same actual error reported under different fingerprints. Use when the user asks "why do I have so many TypeError issues that look the same?", "merge these duplicates", "stop splitting this error into new issues", or wants to clean up fingerprint
Ready to connect★ 40k
- View details
hogliSkillDev tools
PostHog developer CLI and repo tooling reference. Use when the user mentions hogli, asks about repo CLI tools, bin scripts, Makefiles, how to run/build/test/lint, or any dev environment commands.
Ready to connect★ 40k
- View details
implementing-mcp-toolsSkillDev tools
Guide for exposing PostHog product endpoints as MCP tools. Use when creating new or updating API endpoints, adding MCP tool definitions, scaffolding YAML configs, or writing serializers with good descriptions. Covers the full pipeline from Django serializer to generated TypeScript tool handler.
Ready to connect★ 40k
- View details
investigating-ci-failuresSkillDev tools
Investigates a specific CI failure to a verdict: whose fault, which commit, who wrote it, and whether it's fixed. Use for "who broke master", "why did this test fail in CI", "is this failure my PR's fault or everyone's", "is this test flaky or actually broken", "when did this failure start". Works f
Ready to connect★ 40k
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.