SKILL RADAR · GITHUB
Useful agent skills, ranked by real adoption.
Browse verified skills from public repositories. Compare what each skill does, package contents, install activity, and source evidence before adding it to your agent.
- CATALOG SCOPE
- VERIFIED
- skills
- 5,771
- repositories
- 824
- last synced
- Sep 8, 2026
cyrusagentscyrus-setup-github
Configure GitHub for Cyrus — gh CLI login and git config for PRs, with optional webhook setup to enable @mention responses in PR comments, automated rebases and merges, and auto-fixing based on CI failures (coming soon).
- installs
- 1
- GitHub stars
- 797
- Updated
- Sep 5
cyrusagentscyrus-setup-gitlab
Configure GitLab authentication for Cyrus — glab CLI login and git config for creating merge requests.
- installs
- 1
- GitHub stars
- 797
- Updated
- Sep 5
cyrusagentscyrus-setup-prerequisites
Check and install prerequisites for Cyrus — Node.js, jq, gh CLI, and the cyrus-ai npm package.
- installs
- 1
- GitHub stars
- 797
- Updated
- Sep 5
cyrusagentscyrus-setup-slack
Configure Slack integration for Cyrus — create a Slack app from manifest, then guide the user to save credentials.
- installs
- 1
- GitHub stars
- 797
- Updated
- Sep 5
cyrusagentsSearch the web for information. Use when you need to look something up, find current information, or research a topic.
- installs
- 1
- GitHub stars
- 797
- Updated
- Sep 5
cyrusagentsrelease
Prepare, verify, publish, and finish a coordinated Cyrus CLI release. Use when a user asks to release Cyrus, publish cyrus-ai, run a CLI release, or perform the /release workflow.
- installs
- 1
- GitHub stars
- 797
- Updated
- Sep 5
mattpocockdocument-ai-hero-api
Generate or update documentation for the AI Hero API by reading the source code at ~/repos/ai/course-builder. Use when user wants to document, update docs for, or understand the AI Hero API endpoints.
- installs
- 1
- GitHub stars
- 717
- Updated
- Sep 4
mattpocockimprove-codebase-architecture-project
Survey the codebase, pick ONE high-leverage deepening opportunity (filtering out anything already proposed), and publish it as a PRD-shaped GitHub issue via /to-prd-project. Designed to run unattended in the daily architecture-review workflow.
- installs
- 1
- GitHub stars
- 717
- Updated
- Sep 4
mattpocockinstall-effect-package
Install @effect/ packages safely. Use whenever adding a new Effect ecosystem dependency.
- installs
- 1
- GitHub stars
- 717
- Updated
- Sep 4
mattpocockoptimize-loader
"Optimize slow React Router loaders by eliminating redundant DB queries, creating slim query variants, and parallelizing independent fetches. Use proactively when writing or reviewing loader code that calls domain operations services (e.g. CourseOperationsService, VideoOperationsService), or when triaging a slow page load."
- installs
- 1
- GitHub stars
- 717
- Updated
- Sep 4
chainbase-labsagentkey
- PROACTIVELY use whenever the user needs data outside your training set or requires a live network call — web search, URL scraping, news, social media (any platform), market prices (crypto/stocks/FX), on-chain data, e-commerce product data, business/company data, weather, travel (flights/hotels). The provider catalog is dynamic and grows over time; if unsure whether a provider exists, call findtools first to discover it. Not needed for conceptual, code, or local-file work.
- installs
- 1
- GitHub stars
- 640
- Updated
- Aug 24
posthogassessing-heatmaps
Assesses what a page's heatmap is telling you and recommends concrete changes. Pulls click / rageclick / scroll-depth data for a URL, names the hot elements by cross-referencing autocapture events on the same page, and can create a saved heatmap the user opens in PostHog, then summarizes the behavior and proposes improvements.\nTRIGGER when: user asks what a heatmap shows, why people aren't clicking something, where users rage-click, how far they scroll, what to change on a page based on heatmap/click data, or to 'analyze/assess/review the heatmap' for a URL.\nDO NOT TRIGGER when: the user only wants to create a saved heatmap screenshot with no analysis (use heatmaps-saved-create directly), or is asking about session replay in general (use investigating-replay).
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogauditing-endpoints
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 the Endpoints product. Produces a prioritised report grouped by issue type, with recommended actions but does not modify anything without explicit confirmation.
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogauditing-experiments-flags
Audit PostHog experiments and feature flags for configuration issues, staleness, and best-practice violations. Read when the user asks to audit, health-check, or review experiments or feature flags, check flag hygiene, or verify experiment setup.
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogauthoring-data-quality-checks
Adds and runs data quality checks (dbt-test style assertions) on a project's warehouse tables and saved-query views: not-null, uniqueness, accepted values, referential integrity, row-count bounds, freshness, and custom HogQL. Use when asked to test a model, validate a view, check for nulls or duplicates, add data quality checks, find out why a number looks wrong, or judge whether a warehouse table is trustworthy before using it in an analysis. To describe what data means (metrics, certifications, joins), see setting-up-data-catalog instead. Trigger terms: data quality, data test, dbt test, not null check, uniqueness check, freshness check, referential integrity, row count check, validate model, is this table trustworthy.
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogauthoring-log-alerts
Author useful, low-noise log alerts on services in a PostHog project. Use when the user asks to set up alerts for their logs, suggest alerts they should add, or evaluate whether a service is worth monitoring. Covers service triage, baseline characterisation, threshold drafting, back-testing via simulate, and shipping with a notification destination.
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogbuilding-html-canvases
Author a PostHog canvas with semantic HTML, CSS, and direct browser APIs — documents, articles, generative graphics, 2D canvas and WebGL experiences, and focused experiments where React components add no useful structure. Use after building-canvases has routed a canvas request to a plain-HTML/browser-API implementation. Covers the thin component wrapper the current runtime requires, styling and theming without Quill, drawing surfaces, and animation/cleanup patterns.
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogbuilding-react-quill-canvases
Author the React + Quill implementation of a PostHog canvas: the single-component contract, the allowed imports, Quill (PostHog's design system) component and composition rules, theme-aware design tokens, loading skeletons, and the in-canvas date picker. Use after building-canvases has routed a canvas request to a React implementation — dashboards, data boards, forms, tools, or any canvas that should look native to PostHog.
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogchecking-deploy-timing
Determine when a PostHog code change reached a given environment by reading the hidden GIT deploy annotations in the project and correlating them with the merge commit on GitHub. Use when PostHog staff ask "when was X deployed", "is my change live in the US/EU yet", "has my PR shipped", "did the fix roll out to prod-us", or otherwise want to know whether/when a commit, PR, or feature went out to a region. Do not answer deploy-timing questions from event/data volume alone — that only shows when data changed, not when code shipped.
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogchoosing-trend-or-slope-view
Clarify how to visualize change over a time range before building a trend. Use whenever the user asks how much something changed, grew, dropped, improved, or regressed between two points or periods — "how much did X change from A to B", "before vs after", "start vs end", "week over week", "compare this month to last", "change over time" — or mentions a "slope chart" / "slopegraph". Two readings of "change" need different charts: the whole trend (a line, every interval) versus just the two endpoints (a slope, start vs end). Ask which they want, then render it. Not for choosing a saved insight ChartDisplayType in the insight editor.
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogcleaning-up-stale-feature-flags
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.
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogcomposing-grid-canvases
Compose PostHog grid canvases — widget grids (including the user's home canvas) built from reusable component canvases. Use when a task asks to add, fill, move, resize, or remove a widget on a grid or home canvas, to compose a whole canvas of widgets from one ask, to build a reusable widget/component, or when a placement id or grid canvas id is the target. Covers the component store search → configure → fork → build ladder, the component placement contract (size, configSchema), the placement lifecycle (pending/generating/live/failed), the guarded layout patch loop, and reading the canvas's comment threads.
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogconfiguring-experiment-rollout
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 rollout percentage, variant split, or traffic distribution; gives a ratio like 60/40, 70/30, or 80/20; asks "who sees the test variant?"; wants to increase, decrease, or change the rollout or split on a draft or running experiment; weighs equal vs uneven splits; or proposes a mid-experiment split change (often an anti-pattern that needs reset or end-and-restart).
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogconsuming-endpoints-from-client-code
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 codename vs insight breakdown property), handling rate-limit and materialised-endpoint error responses. Use when the user says "how do I call my endpoint", "generate a client for this", or "what auth header do I use".
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4