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
17,235 results · page 9 of 575
- 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
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★ 72
- View details
nature-citationSkillDev tools
Lets your agent add Nature-style citations to a manuscript by finding suitable papers and exporting references.
Ready to connect★ 41k
- View details
nature-polishingSkillDev tools
Lets your agent rewrite academic writing into concise, polished English while keeping facts and citations intact.
Ready to connect★ 41k
- View details
nature-ref-verifierSkillDev tools
Lets your agent cross-check academic references field by field and flag errors like DOI or page mismatches.
Ready to connect★ 41k
- View details
nature-responseSkillDev tools
Lets your agent draft and revise Nature-style reviewer response letters, rebuttals, and cover letters.
Ready to connect★ 41k
- View details
nature-reviewerSkillDev tools
Lets your agent critique a research manuscript like a journal peer reviewer, assessing novelty, significance, and technical soundness.
Ready to connect★ 41k
- View details
researchwriteSkillDev tools
Lets your agent draft, revise, and audit research proposals and evidence-grounded scientific writing.
Ready to connect★ 41k
- 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
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
checking-member-accessSkillDev tools
Explains what a member or a role can do in a PostHog project, using the access control MCP tools. Use when the user asks what someone can see or edit, who can edit dashboards or feature flags, why a member can or cannot open a dashboard, notebook or table, what a role grants, which properties are hi
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-local-replaySkillDev tools
Debugs why session recordings aren't appearing in the local dev environment. Use when a developer reports that local replay ingestion isn't working, recordings aren't showing up despite /s calls, or the replay pipeline seems broken after hogli start. Covers the full local pipeline: SDK capture, Cadd
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
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.
54,764 of the 55,196 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.