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 10 of 575

  • 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

    github.com/posthog/posthog40k stars

    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

    github.com/posthog/posthog40k stars

    View details
  • maintaining-python-testsSkillDev tools

    Maintains existing pytest and Django test suites without weakening correctness. Use when asked to reduce Python test runtime or CI work, investigate slow pytest families, remove stale migration tests, consolidate repeated setup, improve Python test ownership, or measure whether a test optimization w

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • manage-dashboard-widgetsSkillDev tools

    Guides PostHog engineers through dashboard widget platform work — ship a new widget_type (WIDGET_REGISTRY, catalog, run_widgets, WidgetCard) or update a shipped type (config, query, layout, RBAC, tile filter bar, list footer, titleHref, throttles). Use for WidgetSpec, widget_specs/, widget-configs.z

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • managing-dashboardsSkillDev tools

    Guides PostHog engineers through dashboard platform and scene changes. Use when changing Dashboard, DashboardTile, dashboardLogic, dashboard layouts, dashboard sharing or embeds, public dashboards, templates, filters, variables, refresh behavior, tile loading, dashboard lists, or dashboard permissio

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • managing-endpoint-versionsSkillDev tools

    Work safely with endpoint versions — preview a draft in the playground, roll back to an older version, update settings on one version without bumping query history, deactivate a specific version. Use when the user asks "how do I roll back my endpoint", "preview my changes before publishing", "I want

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • merging-prsSkillDev tools

    Merge a PR into `master` through the Trunk merge queue and babysit it until it lands. Enqueue with a `/trunk merge` comment, then watch `trunk merge status` and the PR state until it is MERGED or the queue kicks it out, reporting Trunk's own reason for the terminal transition. Use when asked to merg

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • posthog-desktopSkillDev tools

    Scopes work to the desktop app at products/desktop — a nested standalone pnpm/turbo/Biome workspace imported from the now-archived PostHog/code repo, with posthog/posthog the only source of truth for PRs, CI and publishing, and not part of the root frontend or Django build. Use when the user says /p

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • reviewing-personhog-protocolSkillDev tools

    The full review process for personhog coordination-protocol changes — leases, fencing, handoffs, supervisors, failure budgets, warming, and changelog semantics. Use before pushing or requesting review on any personhog protocol changeset, when asked for an exhaustive or careful review of personhog co

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • reviewing-with-coderabbitSkillDev tools

    Run a CodeRabbit review over the branch from the terminal, with the `coderabbit` CLI, and record the pass in the PR description. Use before `gh pr create`, and whenever a review of a branch is asked for: a local review, a self-review, a CodeRabbit review, or a pre-PR review. Run it once per branch.

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • scene-menu-barSkillDev tools

    Conventions for adding or editing the SceneMenuBar above a scene's <SceneTitleSection>. Use when adding new menu items, moving items between menus, gating behind feature flags, building a new scene's menubar, or wiring rich inputs (tags, combobox) into the bar.

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • setting-feature-flags-in-storybookSkillDev tools

    Use when writing a Storybook story for a component gated on a feature flag — boolean flags or multivariate/experiment-arm variants. Covers the `featureFlags` story parameter and why imperatively setting flags renders the flag-off branch in visual-regression snapshots while passing in jest.

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • stacking-prsSkillDev tools

    Create and manage GitHub native Stacked PRs in this repo with the `gh stack` CLI. Use when asked to stack PRs, split a large change into a stack, add a layer to a stack, restack or rebase a stack, adopt existing branches or PRs into a stack, check out someone else's stack, or land a stack. Covers cr

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • survey-sdk-auditSkillDev tools

    Audit PostHog survey SDK features and version requirements

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    View details
  • testing-mcp-tools-locallySkillDev tools

    Set up the local dev environment, seed data, and API keys to test the staff-only managed migrations MCP tools (managed-migrations-support-list, managed-migrations-support-get) end to end. Use when testing batch import support tooling, debugging MCP tool responses or discovery (tools not appearing),

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    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

    github.com/posthog/posthog40k stars

    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

    github.com/posthog/posthog40k stars

    View details
  • working-with-chartsSkillDev tools

    Guides consumers of @posthog/quill-charts through chart selection, data, themes, sizing, and composition. Use when adding or changing a chart built with the package, including its axes, tooltips, legend, overlays, or interactions. Links to package examples and API docs. Does not cover product integr

    Ready to connect★ 40k

    github.com/posthog/posthog40k stars

    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

    github.com/posthog/posthog40k stars

    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

    github.com/posthog/posthog40k stars

    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

    github.com/github/awesome-copilot39k stars

    View details
  • apple-appstore-reviewerSkillDev tools

    Lets your agent review your app code for Apple App Store rejection risks and optimization tips.

    Ready to connect★ 39k

    github.com/github/awesome-copilot39k stars

    View details
  • arch-linux-triageSkillDev tools

    Lets your agent troubleshoot Arch Linux problems with pacman, systemd, and rolling-release updates.

    Ready to connect★ 39k

    github.com/github/awesome-copilot39k stars

    View details
  • arize-annotationSkillDev tools

    Lets your agent set up label schemas and human review queues, and apply human annotations to tracing data in Arize.

    Ready to connect★ 39k

    github.com/github/awesome-copilot39k stars

    View details
  • bench-readSkillDev tools

    Lets your agent read shared workspace artifacts like findings, verdicts, and work products left by other desks.

    Ready to connect★ 39k

    github.com/github/awesome-copilot39k stars

    View details
  • bug-reproduction-briefSkillDev tools

    Turns vague or intermittent bug reports into a minimal, evidence-backed reproduction before fixing.

    Ready to connect★ 39k

    github.com/github/awesome-copilot39k stars

    View details
  • build-evidence-mapSkillDev tools

    Lets your agent build an auditable map of supporting and contradicting evidence for a contested decision.

    Ready to connect★ 39k

    github.com/github/awesome-copilot39k stars

    View details
  • centos-linux-triageSkillDev tools

    Lets your agent triage and resolve CentOS issues using SELinux and firewalld tooling.

    Ready to connect★ 39k

    github.com/github/awesome-copilot39k stars

    View details
  • conventional-branchSkillDev tools

    Lets your agent create and check Git branch names that follow the Conventional Branch naming rules.

    Ready to connect★ 39k

    github.com/github/awesome-copilot39k stars

    View details
  • copilot-pr-autopilotSkillDev tools

    Lets your agent automatically triage and resolve Copilot review comments on your pull requests.

    Ready to connect★ 39k

    github.com/github/awesome-copilot39k stars

    View details

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.

See how to connect your AI