Agent Skills

by wind-information-co-ltd

筛选估值具备安全边际、股息水平有吸引力且分红可持续的收益型股票，并输出优先级、风险点与跟踪重点。适用于股息投资、价值筛选、现金流导向型选股等场景。

vcp_breakout_scan_skill

by wind-information-co-ltd

筛选波动逐级收缩、抛压减弱、结构趋于成熟的突破预备股，并输出关键位置、确认信号与风险边界。适用于波动收敛策略、Minervini 风格交易、主升前预备股跟踪等场景。

volume_spike_reasoning_skill

by wind-information-co-ltd

对股票盘中或日内放量异动进行归因，判断是消息驱动、资金行为、情绪扩散还是技术性放量。适用于盘中放量时快速判断、缩小排查范围、识别真假异动等场景。

watchlist_news_impact_digest_skill

by wind-information-co-ltd

汇总自选股在指定时间窗口内的重要新闻、公告与舆情变化，并判断偏利多、利空或中性影响。适用于下班后复盘、盘前补新闻、批量整理自选股信息等场景。

wind-alice

by wind-information-co-ltd

调用万得 Alice Agent（A2A 协议，SSE 流式）执行指定 Skill 并获取分析结果的 CLI 工具。当用户要求"用 Alice 跑某个 Skill"、"出一份某公司的调研问题清单"、"做一页纸投资备忘"、"核验一段金融信息"等需要点名 Alice 子 Skill 的场景使用。

agent-auth-mcp

★ 51

by better-auth

Use the Agent Auth MCP tools to discover providers, connect agents, manage capabilities, and execute operations through the MCP protocol. Use when working inside an MCP-enabled environment (Cursor, Claude Code, etc.) and need to authenticate agents, execute capabilities, or interact with Agent Auth providers.

🔥🔥🔥✓ VerifiedAccount requiredNeeds API keys

agent-auth-cli

★ 51

by better-auth

Use the Agent Auth CLI (auth-agent) to discover providers, connect agents, manage capabilities, and execute operations. Use when the user wants to interact with an Agent Auth provider from the terminal, authenticate an agent, execute capabilities, or manage agent connections.

agent-auth-connectors

★ 51

by better-auth

Reliable workflow for using Agent Auth connector capabilities (Gmail and any other provider exposed through the agent-auth tools) — discovering capabilities, connecting an agent per provider, scoping grants with constraints, executing calls, and decoding failure codes. Use whenever a request involves reading or acting on a user's connected account through agent-auth — reading/searching email, listing threads, fetching messages, deploying, or any "check my [provider]" task that routes through age

integration-react-vite

by posthog

PostHog integration for React applications built with Vite (no router)

integration-ruby

by posthog

PostHog integration for any Ruby application using the Ruby SDK

integration-ruby-on-rails

by posthog

PostHog integration for Ruby on Rails applications

integration-swift

by posthog

PostHog integration for Swift iOS and macOS applications

auditing-experiments-flags

by posthog

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.

authoring-log-alerts

by posthog

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.

exploring-llm-clusters

by posthog

Investigate AI observability clusters — understand usage patterns in AI/LLM traffic, compare cluster behavior, compute cost/latency metrics, and drill into individual traces within clusters.

exploring-llm-costs

by posthog

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.

exploring-llm-traces

by posthog

ABSOLUTE MUST to debug and inspect LLM/AI agent traces using PostHog's MCP tools. Use when the user pastes a trace or session URL (e.g. /ai-observability/traces/<id> or /ai-observability/sessions/<id>), asks to debug a trace, figure out what went wrong, check if an agent used a tool correctly, verify context/files were surfaced, inspect subagent behavior, investigate LLM decisions, or analyze token usage and costs. Also use when raw SQL/HogQL against `events.properties.$ai_input` / `$ai_output_c

investigate-metric

by posthog

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.

querying-posthog-data

by posthog

Required reading before writing any HogQL/SQL or calling execute-sql against PostHog. Use whenever the user wants to search, find, or do complex aggregations PostHog entities (insights, dashboards, cohorts, feature flags, experiments, surveys, hog flows, data warehouse, persons, etc.) and query analytics data (trends, funnels, retention, lifecycle, paths, stickiness, web analytics, error tracking, logs, sessions, LLM traces). Covers HogQL syntax differences from ClickHouse SQL, system table sche

error-tracking-nextjs

by posthog

PostHog error tracking for Next.js

error-tracking-node

by posthog

PostHog error tracking for Node.js

error-tracking-nuxt

by posthog

PostHog error tracking for Nuxt

integration-tanstack-start

by posthog

PostHog integration for TanStack Start full-stack applications

diagnosing-missing-recordings

by posthog

Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling, triggers, ad blockers, and quota/billing scenarios.

exploring-autocapture-events

🔥🔥🔥✓ VerifiedFreeAdvanced setup

by posthog

Guides exploration of $autocapture events captured by posthog-js to understand user interactions, find CSS selectors (especially data-attr attributes), evaluate selector uniqueness, query matching clicks ad-hoc, and create actions. Use when the user asks about autocapture data, wants to find what users are clicking, needs to build actions from click events, asks about elements_chain, wants to build a trend or funnel filtered by clicks or other autocapture interactions, asks which properties auto

setting-up-a-data-warehouse-source

🔥🔥🔥✓ VerifiedFreeAdvanced setup

by posthog

Guide the user through connecting a new data warehouse source — Postgres, MySQL, Stripe, Hubspot, MongoDB, Salesforce, BigQuery, Snowflake, and so on. Use when the user wants to "connect Stripe", "import data from Postgres", "add a new data source", "sync my warehouse tables", or wants to pick sync methods for each table. Walks through source-type discovery, credential validation, table discovery, per-table sync_type selection, and the final create call. Also covers picking a good prefix and wha

logs-python

by posthog

PostHog logs for Python

integration-vue-3

by posthog

PostHog integration for Vue 3 applications

finding-experiments

by posthog

Resolves a PostHog experiment reference from natural language to a concrete experiment ID by browsing `experiment-list` (not feature-flag tools), with disambiguation when multiple experiments match. Use when the user names or quotes an experiment ("split test demo", "the File engagement boost experiment", "onboarding retention test", "landing page hero experiment", "pricing experiment"), describes it loosely ("the signup experiment", "my pricing test", "the one with the new checkout"), uses a re

signals-scout-csp-violations