Operate Better Stack telemetry and uptime monitoring via MCP playbooks.
npx skills add https://github.com/johinsDev/loyalty-app --skill better-stack
Please help me install this Agent Skill. Skill: better-stack Source: https://github.com/johinsDev/loyalty-app/tree/main/.claude/skills/better-stack Command: npx skills add https://github.com/johinsDev/loyalty-app --skill better-stack
This Skill helps you operate Better Stack for the loyalty-app monorepo so you can reliably debug incidents, monitor uptime, and build log-based alerts without getting lost in tools, tokens, or namespaces.
Use the Better Stack MCP to list existing telemetry sources and uptime monitors first, then tell the AI exactly what you want to create (e.g., a new log-based chart alert or an availability monitor) and which environment/service it should apply to.
High-intent search queries and answers about installing and using this skill.
To set up Better Stack uptime monitors and telemetry sources using MCP, you must first register the MCP server with separate bearer tokens for uptime and telemetry. You can then list existing monitors and log sources before creating new ones.
Yes, you can create log-based chart alerts for error rates in a monorepo. The Skill provides MCP-driven workflows to build dashboards and configure alerts for specific error-rate or latency signals following repo naming and retention conventions.
The best way to manage incident response and heartbeats in Better Stack is through MCP-driven workflows that allow you to validate availability, manage heartbeats, and acknowledge or resolve incidents directly from your operational playbook.
Yes, you need separate bearer tokens for Better Stack telemetry and uptime monitoring. Correct MCP server registration requires distinct tokens to properly authenticate and manage telemetry logs versus uptime monitors.
This Skill helps troubleshoot auth and log ingest issues by providing MCP-driven operational playbooks that let you inspect ingest schemas, verify telemetry sources, and debug incidents without getting lost in tool namespaces.
Yes, there are specific naming, region, and retention conventions for creating Better Stack alerts. The Skill enforces these repo-specific safety conventions to ensure proper alerting and incident workflows across your services.
DevMHOneAuthenticate NextRoute API sessions with Bearer tokens and session cookies.
wyre-technologyManage BetterStack uptime monitors, incidents, heartbeats, and status pages.
PremModhaOfficialConfigures a Grafana observability stack routing telemetry from microservices to Prometheus, Jaeger, Loki, and Grafana.
MacPhobosManage DigitalOcean resources for monitoring, uptime checks, and project organization.
