agentleFS
Sign inStart free
abdullahkhawerabdullahkhawer/devops-skills/skills/betterstack-cli/SKILL.md

betterstack-cli

Skill8 starsChanged 6 months agoApache-2.0View on GitHub

Perform Better Stack (Logs, Uptime, Incidents) operations using the Better Stack HTTP API via curl. Use for querying logs, monitors, and incidents.

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the instance and rules below when constructing all Better Stack API commands.

    line 8
  2. Distinctive:

    Update the table below with your Better Stack credential file paths:

    line 12
  3. Distinctive:

    If the target environment is unclear, ask the user before running any command.

    line 19
  4. Distinctive:

    NEVER target a Better Stack team/environment not listed in the configuration table above.

    line 69
  5. Distinctive:

    NEVER print, display, log, or store the contents of any token file.

    line 70
  6. Very specific:

    Always read the token inline with $(cat <TOKEN_FILE>) — never hardcode a token value in a command.

    line 71
  7. Very specific:

    Always pass -s (silent) to curl and pipe through jq for readable output.

    line 72
  8. Distinctive:

    NEVER run DELETE endpoints, pause a monitor, or resolve/acknowledge an incident without explicit user instruction.

    line 73
  9. Very specific:

    All list endpoints are paginated (pagination.next field) — follow it until absent to fetch all pages.

    line 74
  10. Distinctive:

    If a monitor ID or incident ID is unfamiliar, look it up with a read-only call first.

    line 75

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Better Stack CLI Skill

Use the instance and rules below when constructing all Better Stack API commands.

Configuration

Update the table below with your Better Stack credential file paths:

EnvironmentToken FileTeam
Production~/.betterstack/prod.token<your-prod-team>
Staging~/.betterstack/staging.token<your-staging-team>

If the target environment is unclear, ask the user before running any command.

Prerequisites (one-time setup by user)

Generate a Better Stack API token (Settings → API tokens) for each environment and save it to the corresponding token file. Never print or display token values. Do not perform these steps yourself.

mkdir -p ~/.betterstack && echo "<your-api-token>" > <TOKEN_FILE> && chmod 600 <TOKEN_FILE>

Command Format

curl -s -H "Authorization: Bearer $(cat <TOKEN_FILE>)" \
  "https://<your-betterstack-api-host>/api/v<version>/<endpoint>" | jq .

Logs querying and Uptime/Incidents management use different API hosts — confirm the correct one for the operation with the user if unsure (telemetry API vs Uptime API).

Available API Endpoints

Read-only (safe, no confirmation needed)

EndpointMethodDescription
/api/v2/monitorsGETList uptime monitors
/api/v2/monitors/<id>GETGet a specific monitor
/api/v2/incidentsGETList incidents
/api/v1/heartbeatsGETList heartbeat checks
/api/v1/query (telemetry API)GET/POSTQuery log data

Mutating operations (confirm with user before running)

EndpointMethodDescription
/api/v2/monitorsPOSTCreate a monitor
/api/v2/monitors/<id>PATCHUpdate a monitor
/api/v2/incidents/<id>/acknowledgePOSTAcknowledge an incident
/api/v2/incidents/<id>/resolvePOSTResolve an incident

Never run — requires explicit human approval

EndpointMethodReason
/api/v2/monitors/<id>DELETEIrreversible monitor deletion
/api/v2/heartbeats/<id>DELETEIrreversible heartbeat deletion
/api/v2/monitors/<id>/pausePOSTStops monitoring silently, risking missed real outages

Rules

  • NEVER target a Better Stack team/environment not listed in the configuration table above. If a request references an unfamiliar team, stop and ask the user to confirm.
  • NEVER print, display, log, or store the contents of any token file.
  • Always read the token inline with $(cat <TOKEN_FILE>) — never hardcode a token value in a command.
  • Always pass -s (silent) to curl and pipe through jq for readable output.
  • NEVER run DELETE endpoints, pause a monitor, or resolve/acknowledge an incident without explicit user instruction.
  • All list endpoints are paginated (pagination.next field) — follow it until absent to fetch all pages.
  • If a monitor ID or incident ID is unfamiliar, look it up with a read-only call first.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free