Loading...
Loading...
Found 311 Skills
Production server monitoring stack covering Prometheus, Node Exporter, Grafana, Alertmanager, Loki, and Promtail on bare-metal or VM Linux hosts. USE WHEN: - Setting up monitoring for a new production server or VPS - Configuring Prometheus scrape targets for application or system metrics - Creating Grafana dashboards and datasource provisioning - Writing Alertmanager routing rules with email/Slack notifications - Implementing the PLG stack (Promtail + Loki + Grafana) for log aggregation - Performing live system diagnostics with htop, iotop, nethogs, ss, vmstat, iostat - Setting up uptime monitoring with UptimeRobot or healthchecks.io DO NOT USE FOR: - Kubernetes-native observability (use the kubernetes skill instead) - Application-level APM (distributed tracing with Jaeger/Tempo — use observability skill) - Cloud-managed monitoring (CloudWatch, GCP Monitoring, Azure Monitor) - Windows Server monitoring
Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.
Reference for all GrepAI MCP tools. Use this skill to understand available MCP tools and their parameters.
Build microservices - Spring Cloud, service mesh, event-driven, resilience patterns
Analyze implementation details, trace data flow, and explain technical workings with precise file:line references. Use when you need to understand HOW code works.
Investigate suspected bugs with git archaeology and root cause analysis. Triggers: "bug", "broken", "doesn't work", "failing", "investigate bug".
Guide developers through capturing diagnostic artifacts to diagnose production .NET performance issues. Use when the user needs help choosing diagnostic tools, collecting performance data, or understanding tool trade-offs across different environments (Windows/Linux, .NET Framework/modern .NET, container/non-container).
Reverse Paper Reading Method: Given a paper, recursively identify the previous papers it critiques and improves on (max 5 layers), then find the latest research progress published after it, and tell the evolution history of the relevant problem forward from the source. Centered on problems, explain the problems identified by each paper and their solution innovations in a Feynman-style manner. Use when user shares a paper and wants to understand its intellectual lineage, citation chain, problem evolution, or says 'reverse reading', 'paper traceability', 'paper context', 'paper river', 'paper connects', 'trace back', 'the ins and outs of this paper', 'paper evolution'. Also trigger when user wants to understand how a research problem evolved across multiple papers.
Build worlds through cascading consequences from speculative changes. Use when introducing new technologies, species, or alternate histories and need to trace realistic societal transformations across multiple domains.
Supported programming languages in GrepAI. Use this skill to understand which languages can be indexed and traced.
Setup Sentry in Ruby apps. Use when asked to add Sentry to Ruby, install sentry-ruby gem, or configure error monitoring for Ruby applications or Rails.
Trace bugs through call chains using knowledge graph