Agent Skills

memory-leak-audit

✓★ 187,144

by microsoft

Audit code for memory leaks and disposable issues. Use when reviewing event listeners, DOM handlers, lifecycle callbacks, or fixing leak reports. Covers addDisposableListener, Event.once, MutableDisposable, DisposableStore, and onWillDispose patterns.

🧰 Not standalone — use together with microsoft/vscode

heap-snapshot-analysis

✓★ 187,144

by microsoft

Analyze V8 heap snapshots to investigate memory leaks and retention issues. Use when given .heapsnapshot files, asked to compare before/after snapshots, asked to find what retains objects, or investigating why objects survive GC. Provides snapshot parsing, comparison, retainer-path helpers, and scratchpad scripts.

🧰 Not standalone — use together with microsoft/vscode

memory

✓★ 105,779

by google-gemini

Expertise in maintaining persistent bot memory, synchronizing with previous sessions via the Task Ledger, and preserving decision logs.

🧰 Not standalone — use together with google-gemini/gemini-cli

alloc-profile

✓★ 48,467

by clickhouse

Analyze a jemalloc (or other) allocation profile in collapsed stack format. Use when the user wants to analyze memory allocations, find top allocators, or understand memory usage patterns from a .collapsed profile file.

🧰 Not standalone — use together with clickhouse/clickhouse

optimizing-clickhouse-and-hogql-queries

★ 35,336

by posthog

Workflow for optimizing ClickHouse and HogQL queries. Use when a HogQL query, query runner, insight, or report is too slow; when a hand-written ClickHouse query (via `sync_execute` or in a migration) is too slow; when ClickHouse times out or hits memory limits; when investigating a slow `system.query_log` row; or when reviewing a proposed HogQL printer change for performance. Covers extracting the ClickHouse SQL, common smells (`FROM ... FINAL`, `JSONExtract` over properties, missing skip indexe

🧰 Not standalone — use together with posthog/posthog

exploring-scouts

★ 35,336

by posthog

How to explore and make sense of PostHog Signals scouts — the scheduled agents that scan a project and write reports into the Signals inbox. Use when a user wants to understand what scouts they have, how each one is behaving, and whether the fleet is actually working. Covers surveying the fleet and its schedules, reading recent scout runs and drilling into a single run's reasoning, inspecting the durable scratchpad memory the fleet has built up, tracing a run to the reports it wrote or edited, a

🧰 Not standalone — use together with posthog/posthog

kudos-storage

★ 35,336

by posthog

The data model — the `kudos` table columns, the `kudos_id` dedupe/idempotency scheme, and the per-recipient `people/<handle>.md` profile memory. Load before any table-append or memory-write.

🧰 Not standalone — use together with posthog/posthog

runbook-memory

★ 35,336

by posthog

🧰 Not standalone — use together with posthog/posthog

signals-scout-mcp-tool-calls

★ 35,336

by posthog

Signals scout for PostHog MCP tool calls. Watches $mcp_tool_call telemetry for tools that need improvement — high, broad-reach failure rates, retry/hammering that betrays a confusing schema, slow or context-bloating responses — and files each validated tool-quality finding as a report in the inbox; otherwise writes durable memory and closes out empty. Adapts to which fields the project actually captures.

🧰 Not standalone — use together with posthog/posthog

auditing-the-fleet

★ 35,336

by posthog

The fleet-wide audit — sweep every agent, mine recent sessions for failures/anomalies, classify root causes, and branch a DRAFT proposal per fix (never freeze/promote); write a report to memory. Load when asked to audit all agents or what's underperforming.

🧰 Not standalone — use together with posthog/posthog

mastra-smoke-test

★ 25,837

by mastra-ai

Smoke test Mastra projects locally or deploy to staging/production. Tests Studio UI, agents, tools, workflows, traces, memory, and more. Supports both local development and cloud deployments.

🧰 Not standalone — use together with mastra-ai/mastra

investigation-notes

✓★ 8,372

by cloudflare

Structured scratch tracking document for investigation state during bug hunts - prevents re-reading code, losing context, and rabbit holes; maintains external memory so you don't re-derive conclusions

🧰 Not standalone — use together with cloudflare/workerd

hosting-plans-helper

★ 470

by automattic

Answer WordPress.com plan, pricing, upgrade, and feature-tier questions (plan names, what each tier unlocks — plugins, themes, custom code, SSH, hosting — and current prices) from authoritative live data. Load before answering ANY plan, pricing, or feature-gating question; never answer these from memory.

🧰 Not standalone — use together with automattic/studio

learn-history

★ 239

by openshift

Analyze all past sessions for this project and extract knowledge worth persisting to AGENTS.md, .claude/agents/, or memory. Deep analysis of full session history.

🧰 Not standalone — use together with openshift/oc

learn-session

★ 239

by openshift

Review the current session and extract knowledge worth persisting to AGENTS.md, .claude/agents/, or memory. Use at the end of a session to capture what was learned.

🧰 Not standalone — use together with openshift/oc