1. Habit
  2. Skills
  3. Groundcover CLI skill
paymog · 9K installs

Groundcover CLI skill
Runs by itself, every weekday morning.

Production issues triaged with evidence.

Install the Groundcover CLI skill and make it a habit: follow https://gethabit.dev/skills/paymog/groundcover-cli.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

9K installs1 starsMIT licenceSource on GitHub ↗

Groundcover CLI

by paymog · 9K installs

The skill

Groundcover cli lets an agent drive the groundcover command to query logs, traces, metrics and k8s events and to manage dashboards, monitors, silences and pipelines on Groundcover.

Only when you ask.

The habit

Production issues triaged with evidence.

↻ Runs by itselfevery weekday morning

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

every weekday morning. Runs in Claude Code routine or cron.

  • ↻ every weekday morning
  • 0 8 * * 1-5

02

It checks its work

all queries answered. If a check fails, it tries again.

  • ✓groundcover auth status resolves a gcsa_ key
  • ✓logs search, traces search and metrics query return without an error
  • ✓the triage note lists each checked service

03

It remembers

daily triage log. The next run reads it first: yesterday's error counts and open issues.

loops/groundcover-prod-triage-loop/log.md

One run, step by step.
Then it stops.

Stop ruleStops after five services per run and one retry per query.

  1. 01

    Check auth

    Confirm groundcover auth status shows a valid gcsa_ service-account key.

  2. 02

    Set the window

    Compute start and end times in UTC with date -u, last hour by default.

  3. 03

    Logs first

    Run groundcover logs search with a GCQL filter on service_name and error level.

  4. 04

    Traces if slow

    Run groundcover traces search on duration_ms and pivot trace IDs back to logs.

  5. 05

    Metrics shape

    Use groundcover metrics query with PromQL range queries for error rate and p99.

  6. 06

    Is it running

    Check groundcover k8s workloads for restarts and k8s events-search for Warning events.

  7. 07

    Write the note

    Summarize findings per service and add them to the log.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Groundcover CLI skill helps.

Use it when

  • ✓ You debug a production error
  • ✓ You check latency or crashlooping pods
  • ✓ You edit Groundcover dashboards or monitors

Skip it when

  • – You do not use Groundcover
  • – You only have an ingestion key

Questions

Groundcover CLI skill, answered.

Which key does it need?

A gcsa_ service-account key. A gcik_ ingestion key will not authenticate the API.

Why does logs search time out?

Busy workloads flood logs. Add a narrow term, shorten the window or raise --timeout.

Does it silence alerts?

Not in this loop. Silencing is a separate step with groundcover silences create.

How do I install the Groundcover CLI skill?

Copy the prompt at the top into your agent. It installs the skill from paymog/groundcover-cli and sets up the habit. Or run npx skills add paymog/groundcover-cli --skill groundcover-cli.

Is the Groundcover CLI skill free?

Yes. It is published under MIT. Habit is free too.

Groundcover CLI. Now as a habit.

Install the Groundcover CLI skill and make it a habit: follow https://gethabit.dev/skills/paymog/groundcover-cli.md

  • Free
  • No account
  • Undo in one line

All paymog skills →More ops skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by paymog, published under MIT. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.