监控
日志、指标与可观测性
Failure Postmortem
Sounder25
Structured logging and analysis of execution failures to prevent recurrence.
libby-book-monitor
alexpolonsky
Track book availability on Libby/OverDrive libraries. Search library catalogues, manage a watchlist, and get notified when books are added. Use for "libby", "check libby", "libby watchlist", "is book on libby", "book available", "overdrive", "library catalogue", "ספרייה", "ספרים".
blogwatcher
magnusthovsland
"Monitor blogs and RSS/Atom feeds via blogwatcher-cli tool."
springboot-patterns
x-cmd
Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.
update-focus
mseok
"Update current-focus.md with a structured session summary. Preserves the document's rich structure: weekly focus, session history rotation, open loops, mental state. Use at end of work sessions or when a session-end reminder appears."
langsmith-observability
L-yifan
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
dspy
L-yifan
Build complex AI systems with declarative programming, optimize prompts automatically, create modular RAG systems and agents with DSPy - Stanford NLP's framework for systematic LM programming
Bankr x402 SDK - Client Patterns
BankrBot
This skill should be used when the user asks to "implement Bankr SDK client", "write bankr-client.ts", "create SDK client setup", "common files for SDK project", "package.json for Bankr SDK", "tsconfig for Bankr", "SDK TypeScript patterns", "execute SDK transactions", or needs the reusable client code and common project files for Bankr SDK integrations.
log-analyzer
AIDotNet
解析和分析日志文件，支持模式匹配、过滤、统计和错误检测。
site-reliability-engineer
nahisaho
Production monitoring, observability, SLO/SLI management, and incident response. Trigger terms: monitoring, observability, SRE, site reliability, alerting, incident response, SLO, SLI, error budget, Prometheus, Grafana, Datadog, New Relic, ELK stack, logs, metrics, traces, on-call, production monitoring, health checks, uptime, availability, dashboards, post-mortem, incident management, runbook. Completes SDD Stage 8 (Monitoring) with comprehensive production observability: - SLI/SLO definitions and tracking - Monitoring stack setup (Prometheus, Grafana, ELK, Datadog, etc.) - Alert rules and notification channels - Incident response runbooks - Observability dashboards (logs, metrics, traces) - Post-mortem templates and analysis - Health check endpoints - Error budget tracking Use when: user needs production monitoring, observability platform, alerting, SLOs, incident response, or post-deployment health tracking.
flare
spatie
Manage Flare error tracking and performance monitoring using the flare CLI. Use when the user wants to list, triage, resolve, snooze, or debug errors; manage projects; create projects and retrieve API keys; check error counts; investigate slow routes, queries, jobs, or commands; view aggregated performance data and traces; or interact with flareapp.io from the command line.
stakeholder-map
alunadev
"Builds a Power × Interest stakeholder map and generates a communication plan per quadrant. Use when managing a complex launch, aligning cross-functional teams, or preparing stakeholder engagement strategy. Triggers on: stakeholder management, stakeholder map, stakeholder alignment, communication plan, power interest grid, cross-functional alignment, executive alignment, managing up."
incident-response
data219
Use when an alert, outage, error spike, latency surge, or telemetry anomaly needs fast multi-tool incident triage and safe mitigation decisions.
enterprise-java
ProjAnvil
企业级 Java 开发技能，涵盖 Spring 生态系统、微服务、设计模式、性能优化和 Java 最佳实践。使用此技能构建企业级 Java 应用、使用 Spring Boot、实现微服务，或需要 Java 架构和性能调优指导时使用。
product-strategy
alunadev
Expert product strategy advisor for Senior PMs. Use when defining a product vision, setting OKRs, building a roadmap, prioritizing between competing bets, entering a new product area, or when stakeholders disagree on direction. Produces a structured strategy document grounded in user outcomes, not feature lists.
lesson-learned
cachemoney
"Analyze recent code changes via git history and extract software engineering lessons. Use when the user asks 'what is the lesson here?', 'what can I learn from this?', 'engineering takeaway', 'what did I just learn?', 'reflect on this code', or wants to extract principles from recent work."
competitor-analysis
alunadev
"Analyzes competitors with structured intel across positioning, features, pricing, and differentiation opportunities. Use before entering a new market, updating product strategy, or preparing a competitive brief. Triggers on: competitive analysis, competitor research, market landscape, differentiation, competitive positioning, competitor mapping, market entry, who are my competitors."
junglebus
b-open-io
This skill should be used when the user asks about "JungleBus", "transaction streaming", "BSV subscriptions", "real-time blockchain data", "GorillaPool API", or needs to subscribe to blockchain events.
mathematician
dangeles
Use when designing algorithms, analyzing complexity, selecting numerical methods, or verifying mathematical correctness for software implementations.
observable-gepa-migration
raveeshbhalla
Migrate DSPy GEPA usage in DSPy from the original to gepa-observable. This makes it possible for teams to clearly review each iteration and the lineage to understand how their prompt is evolving. The repository offers a web dashboard for monitoring, but requires a custom GEPA fork that provides custom observers and LM call logging. Use when developers want to add observability to GEPA optimization.
Root Cause Tracing
obra
Systematically trace bugs backward through call stack to find original trigger
product-price-monitor
magnusthovsland
"Watch product, flight, or listing prices; alert on target."
git-history-analyzer
ratacat
"Use this agent when you need to understand the historical context and evolution of code changes, trace the origins of specific code patterns, identify key contributors and their expertise areas, or analyze patterns in commit history. This agent excels at archaeological analysis of git repositories to provide insights about code evolution and development patterns. <example>Context: The user wants to understand the history and evolution of recently modified files.\nuser: \"I've just refactored the authentication module. Can you analyze the historical context?\"\nassistant: \"I'll use the git-history-analyzer agent to examine the evolution of the authentication module files.\"\n<commentary>Since the user wants historical context about code changes, use the git-history-analyzer agent to trace file evolution, identify contributors, and extract patterns from the git history.</commentary></example> <example>Context: The user needs to understand why certain code patterns exist.\nuser: \"Why does this payment processing..."
ceo-advisor
ovachiever
Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Includes strategy analyzer, financial scenario modeling, board governance frameworks, and investor relations playbooks. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy.