Monitoring
Logging, metrics, and observability
marginfi
by sendaifun
Complete guide for Marginfi - Solana's decentralized lending protocol for lending, borrowing, leveraged positions(looping) and flash loans. Covers account creation, deposits, borrows, repayments, withdrawals, flash loans, and leveraged positions using the @mrgnlabs/marginfi-client-v2 SDK.
b2c-logs
by SalesforceCommerceCloud
Retrieve or monitor logs from B2C Commerce instances with the b2c cli. Always reference when using the CLI to fetch logs, search log entries, filter by level/time, or tail logs in real-time. Also use when a user reports errors, broken functionality, or issues with controllers, script APIs, custom API backends, jobs, or other SFCC server-side components.
b2c-logging
by SalesforceCommerceCloud
Implement logging in B2C Commerce scripts using dw.system.Logger. Use when adding debug output, error tracking, or custom log files to server-side code. Covers getLogger, log categories, log levels (debug, info, warn, error, fatal), and custom named log files.
plan
by tkersey
Produce essay-heavy, decision-complete plans in proposed_plan block format. Use when asked to run $plan, turn a project brief into an execution-ready architecture plan, or iteratively refine strategy; optionally export to iterative plan-N.md files (max N=5) when explicitly requested outside Plan Mode.
complexity-mitigator
by tkersey
Mitigate incidental code complexity when control flow is tangled, nesting is deep, names are hard to parse, or reasoning requires cross-file hops. Use when a review stalls on readability, you need an analysis-first refactor plan before edits, or you want essential-vs-incidental verdicts, ranked simplification steps, a small structural sketch, and a TRACE assessment (analysis-only; no edits).
analyzing-mlflow-trace
by mlflow
Analyzes a single MLflow trace to answer a user query about it. Use when the user provides a trace ID and asks to debug, investigate, find issues, root-cause errors, understand behavior, or analyze quality. Triggers on "analyze this trace", "what went wrong with this trace", "debug trace", "investigate trace", "why did this trace fail", "root cause this trace".
analyzing-mlflow-session
by mlflow
Analyzes an MLflow session — a sequence of traces from a multi-turn chat conversation or interaction. Use when the user asks to debug a chat conversation, review session or chat history, find where a multi-turn chat went wrong, or analyze patterns across turns. Triggers on "analyze this session", "what happened in this conversation", "debug session", "review chat history", "where did this chat go wrong", "session traces", "analyze chat", "debug this chat".
instrumenting-with-mlflow-tracing
by mlflow
Instruments Python and TypeScript code with MLflow Tracing for observability. Triggers on questions about adding tracing, instrumenting agents/LLM apps, getting started with MLflow tracing, or tracing specific frameworks (LangGraph, LangChain, OpenAI, DSPy, CrewAI, AutoGen). Examples - "How do I add tracing?", "How to instrument my agent?", "How to trace my LangChain app?", "Getting started with MLflow tracing", "Trace my TypeScript app"
git-log-summary
by benmatselby
Provides a summary of the git log for the past period of time. Use when asked to provide a git log summary.
return-calculations
by JoelLewis
"Compute and explain investment return metrics: TWR, MWR/IRR, CAGR, annualization, sub-period linking, arithmetic vs geometric vs log returns."
post-trade-compliance
by JoelLewis
"Post-trade compliance and surveillance: trade surveillance, pattern detection, best execution review, allocation fairness, exception-based monitoring, and regulatory reporting triggers."
autoresearch
by atrislabs
Karpathy-style keep/revert experiment loop for Atris experiment packs. Use when improving prompts, tools, workers, or bounded repo targets.
error-detective
by htlin222
Search logs and codebases for error patterns, stack traces, and anomalies. Use when debugging issues, analyzing logs, or investigating production errors.
debug
by htlin222
Debug errors, test failures, and unexpected behavior with log analysis and correlation. Use when encountering issues, error messages, analyzing logs, or investigating production errors.
promql-validator
by akin-ozer
Comprehensive toolkit for validating, optimizing, and understanding Prometheus Query Language (PromQL) queries. Use this skill when working with PromQL queries to check syntax, detect anti-patterns, identify optimization opportunities, and interactively plan queries with users.
Loki Configuration Generator
by akin-ozer
fluentbit-generator
by akin-ozer
Comprehensive toolkit for generating best practice Fluent Bit configurations. Use this skill when creating new Fluent Bit configs, implementing log collection pipelines (INPUT, FILTER, OUTPUT sections), or building production-ready telemetry configurations.
financial-operations-expert
by shipshitdev
Use this skill when users need help with business finances, tax planning, bookkeeping, profit/loss analysis, cash flow management, or multi-business financial tracking. Activates for "am I profitable," tax questions, accounting setup, or financial health checks.
mpm-monitor
by bobmatnyc
Control monitoring server and dashboard
Root Cause Tracing
by bobmatnyc
Systematically trace bugs backward through call stack to find original trigger
performance-trace-guide
by proflead
Guide collection and analysis of performance traces. Use when a mid-level developer needs to diagnose slowness.
log-summarizer
by proflead
Summarize noisy logs into likely causes and next steps. Use when a junior developer needs help interpreting logs.
cross-service-debugger
by proflead
Coordinate debugging across multiple services. Use when a senior developer needs to trace a distributed issue.
observability-setup
by proflead
Set up metrics, logs, and traces for a service. Use when a mid-level developer needs basic observability coverage.