AGENT SKILLS · ミッション装備
実際に使われている Agent Skills
公開リポジトリの検証済み Skills を比較し、機能、内容、導入状況、出典を確認してから追加できます。
- 掲載範囲
- 検証済み
- Skills
- 23,248
- リポジトリ
- 3589
- 最終同期
- 2026/11/04
posthogexploring-llm-costs
Investigate LLM spend in PostHog — total cost over time, cost by model, provider, user, trace, or custom dimension, token and cache-hit economics, and cost regressions. Use when the user asks "how much are we spending on LLMs?", "which model / user / feature is most expensive?", "why did cost spike?", wants to build a cost dashboard or alert, or pastes a trace URL and asks about its cost.
- 1時間の導入数
- 1
- GitHub Stars
- 81
- 更新日
- 9月10日
posthogexploring-scouts
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
- 1時間の導入数
- 1
- GitHub Stars
- 81
- 更新日
- 9月10日
posthogfeature-usage-feed
Set up an LLM-judge evaluation that extracts canonical use cases for a PostHog feature at scale and streams the results to a Slack channel as a live feed. Use when someone wants to understand how users are actually using a specific AI/LLM-powered feature in production — what they're investigating, what questions they're trying to answer, and what patterns surface — without manually reading hundreds of traces. Assumes the feature emits $aigeneration and $aievaluation events with $sessionid linkag
- 1時間の導入数
- 1
- GitHub Stars
- 81
- 更新日
- 9月10日
posthogformatting-insight-axes
Pick the right y-axis unit when creating or updating an insight via posthog:insight-create or posthog:insight-update — both TrendsQuery (trendsFilter.aggregationAxisFormat) and SQL insights (DataVisualizationNode, chartSettings.yAxis[].settings.formatting). Use when the agent is about to add a formula purely to convert units (e.g. dividing seconds by 60 to display minutes), when a mathproperty or SQL column is a duration, currency, ratio, or large count, or whenever the user mentions "format the
- 1時間の導入数
- 1
- GitHub Stars
- 81
- 更新日
- 9月10日
posthoginstrument-feature-flags
- Add PostHog feature flags to gate new functionality. Use after implementing features or reviewing PRs to ensure safe rollouts with feature flag controls. Also handles initial PostHog SDK setup if not yet installed.
- 1時間の導入数
- 1
- GitHub Stars
- 81
- 更新日
- 9月10日
posthoginstrument-metrics
- Add PostHog metric capture to track counters, gauges, and histograms. Use after implementing features or reviewing PRs to ensure key operations are measured, or when asked to add metrics, counters, or track a value over time. Also handles mirroring existing Prometheus/StatsD/OpenTelemetry metrics into PostHog and initial OTLP exporter setup.
- 1時間の導入数
- 1
- GitHub Stars
- 81
- 更新日
- 9月10日
posthoginvestigate-metric
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries. Use when the user reports an anomaly, asks "why did X change?", or needs root-cause analysis for a trend, funnel, retention, stickiness, or lifecycle metric.
- 1時間の導入数
- 1
- GitHub Stars
- 81
- 更新日
- 9月10日
posthoginvestigating-metric-anomalies
Investigates server/infrastructure metric anomalies in PostHog Metrics — from "this metric is rising/dropping/spiking" or a fired alert to a probable cause with evidence. Use when asked why a metric looks wrong (ingestion lag rising, error rate spiking, latency degrading, queue depth growing, throughput dropping), when an alert fires on an OTel/Prometheus metric, or for any incident triage that starts from a metric symptom. Composes characterize-metric-anomaly, query-metrics, and metric-names-li
- 1時間の導入数
- 1
- GitHub Stars
- 81
- 更新日
- 9月10日
posthogresolving-ingestion-warnings
Diagnoses and resolves PostHog ingestion warnings — problems recorded while ingesting events (dropped events, rejected person merges, oversized payloads, invalid data). Use when a user asks why events are missing, dropped, or undercounted, why identify/alias calls don't work or accounts stay duplicated, why person or group properties aren't updating or profiles look inflated, why recordings have gaps, heatmaps are empty, LLM token counts are missing, why cookieless events vanish, or whenever the
- 1時間の導入数
- 1
- GitHub Stars
- 81
- 更新日
- 9月10日
posthogsetting-up-data-catalog
Populates and maintains a project's data catalog (semantic layer): canonical metrics, trust marks (certifications) on warehouse tables/views, and reviewed table relationships. Use when asked to set up / seed / bootstrap the data catalog or semantic layer, to catalog a project's metrics, to certify or deprecate data sources, to propose or review table joins, or to work through the proposal review queue. To use an existing catalog to answer a business-number question, see querying-posthog-data ins
- 1時間の導入数
- 1
- GitHub Stars
- 81
- 更新日
- 9月10日
posthogsetting-up-support-slack-locally
Connect a real Slack workspace to local PostHog Conversations (the SupportHog Slack app) so Slack messages become support tickets and replies post back. Use when the user wants to test the conversations Slack integration locally, hits "Support Slack OAuth client ID is not configured", gets a white screen or "Network error" on the OAuth callback, or asks how to set SUPPORTSLACKAPPCLIENTID / a tunnel for supporthog Slack events. Covers the Slack app + scopes, the SUPPORTSLACK dynamic settings, and
- 1時間の導入数
- 1
- GitHub Stars
- 81
- 更新日
- 9月10日
posthogsignals
How to query the documentembeddings table for raw signal data using HogQL. Use when you need to perform semantic search over signals, fetch every signal that contributed to a specific report, or list signal types. For browsing the curated report layer (the Inbox) — listing reports, filtering by status/source, drilling into a single report by ID — use the inbox-exploration skill first; drop into this skill afterwards if the user wants the underlying observations.
- 1時間の導入数
- 1
- GitHub Stars
- 81
- 更新日
- 9月10日
posthogsignals-scout-error-tracking
Signals scout for PostHog error tracking. Watches $exception bursts, stuck loops, multi- fingerprint clusters, and status regressions.
- 1時間の導入数
- 1
- GitHub Stars
- 81
- 更新日
- 9月10日
posthogsignals-scout-health-checks
Signals scout over PostHog's own health checks. Bundles the project's active health issues by kind, weights them by blast radius, and surfaces the ones worth acting on.
- 1時間の導入数
- 1
- GitHub Stars
- 81
- 更新日
- 9月10日
posthogsignals-scout-mcp-tool-calls
Signals scout for PostHog MCP tool calls. Watches $mcptoolcall telemetry for tools that need improvement — broad-reach failure rates, retry hammering, slow or context-bloating responses — grouped by owning product category, each with a fix suggestion.
- 1時間の導入数
- 1
- GitHub Stars
- 81
- 更新日
- 9月10日
posthogsignals-scout-replay-vision
Signals scout for PostHog Replay Vision scanners. Watches that enabled scanners keep observing (throughput and quota cliffs) and that aggregate score shifts and recurring themes get surfaced.
- 1時間の導入数
- 1
- GitHub Stars
- 81
- 更新日
- 9月10日
posthogsignals-scout-skills-store
Skill-hygiene scout for the team's PostHog skills store. Watches recently-changed and most- used skills for authoring violations — vague descriptions, bloated bodies, dead file links, kitchen-sink scope, committed secrets.
- 1時間の導入数
- 1
- GitHub Stars
- 81
- 更新日
- 9月10日
posthogwriting-streamlit-apps
Write Streamlit app source code that runs well in a PostHog sandbox — the posthogapps.query() bridge for reading PostHog data, the packages baked into the sandbox image, caching and session state across Streamlit reruns, layout and chart patterns, and the app.py entry point with any helper modules and data files bundled beside it. Use when authoring or debugging the Python source of a PostHog Streamlit app, when a query inside an app fails, or when asked to "write a streamlit app that shows Post
- 1時間の導入数
- 1
- GitHub Stars
- 81
- 更新日
- 9月10日
coleam00hooks-create
Author a working Claude Code hook from a plain-English description of what it should guarantee or do. You describe the behavior ("never let the agent edit my migrations", "don't stop until the tests pass", "log every command"); this skill picks the right lifecycle event, writes the hook script, and wires it into .claude/settings.json. Use when you want a deterministic guarantee or automation in your AI Layer and don't want to write the hook by hand. The meta-tool for the hooks primitive.
- 1時間の導入数
- 1
- GitHub Stars
- 495
- 更新日
- 9月9日
coleam00piv-review-pr
Full pull-request review — fetch the PR, run the project's validation, review the diff with fresh eyes (dispatching the code-reviewer agent), categorize issues by severity, post the review to GitHub (approve / request-changes / comment), and save a report. The agentic gate that runs on an open PR before a human approves. Use after piv-create-pr.
- 1時間の導入数
- 1
- GitHub Stars
- 495
- 更新日
- 9月9日
coleam00piv-run-full-loop
Autonomously develops a complete feature from priming through planning, execution, and commit by chaining the four core PIV-loop skills. Use when you want a full hands-off feature build from a single description.
- 1時間の導入数
- 1
- GitHub Stars
- 495
- 更新日
- 9月9日
coleam00piv-slice-epic
Slice an epic (with its architecture decisions) into PIV-sized tickets with a dependency graph, then create them in your tracker (Jira via the Atlassian MCP, or GitHub/Linear/local). Accepts the epic and its architecture as one doc or as an epic plus a separate linked architecture page. Turns a large strategic doc into the discrete units of work that the PIV loop consumes.
- 1時間の導入数
- 1
- GitHub Stars
- 495
- 更新日
- 9月9日
coleam00plan-create-stories
Decomposes a PRD into well-formed, engineer-ready tickets — Jira issues or GitHub issues. Use after a PRD exists, to turn its phases and user stories into a structured backlog. Works for a new codebase (MVP scope) or an existing one (epic scope).
- 1時間の導入数
- 1
- GitHub Stars
- 495
- 更新日
- 9月9日
lupynowmath-modeling-solver
数学建模竞赛解题全流程指导。覆盖国赛(CUMCM)和美赛(MCM/ICM)全部题型(A-F)，提供12种问题本质分析、95+场景模型决策矩阵、5本算法Cookbook、11本完整例题Playbook、22个Python+7个MATLAB可运行代码模板。与math-modeling-paper形成"解题→写作"配对。当用户提及建模思路、选什么模型、怎么建模、赛题求解、粘贴赛题文本、美赛/国赛题目分析、CVaR/NSGA-II/Monte Carlo/时间序列/ANOVA/灰色关联、网络流/图论/生态建模、模型命名/Memo/Letter/Our Work流程图时，使用此skill。
- 1時間の導入数
- 1
- GitHub Stars
- 362
- 更新日
- 7月31日