Skip to content
TrustedSkillsbeta
Back to all skills

Observability Monitoring Slo Implement

Listed
sickn33·vlatest·devops·MIT

Automates SLO implementation & monitoring across infrastructure, providing proactive alerts based on observability data.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add sickn33/agentic-awesome-skills --skill observability-monitoring-slo-implement -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

sickn33

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • Declares what it does: failed

    No SKILL.md was found in the skill's directory.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned sickn33/antigravity-awesome-skills at 5a4cdd9df8.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
5a4cdd9df8
Manifest
skills/observability-monitoring-slo-implement/SKILL.md
Scanned
0 files
Copies in repo
3 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The observability-monitoring-slo-implement skill enables AI agents to define, track, and automate alerts for Service Level Objectives (SLOs) within DevOps environments. It bridges the gap between raw metrics and actionable reliability standards by configuring monitoring thresholds directly through natural language instructions.

When to use it

  • Establishing new SLOs for critical microservices or APIs without manual dashboard configuration.
  • Automating alerting rules when error rates exceed acceptable limits defined in business requirements.
  • Adjusting existing reliability targets based on changing user traffic patterns or seasonal demand.
  • Integrating SLO tracking into CI/CD pipelines to enforce quality gates before deployment.

Key capabilities

  • Define custom SLOs using specific metrics and target percentages (e.g., 99.9% availability).
  • Configure automated alerting channels for when SLO burn rates exceed defined thresholds.
  • Generate visual reports on current SLO compliance status across multiple services.
  • Update or remove existing SLO configurations dynamically via agent commands.

Example prompts

"Create an SLO for the payment gateway service requiring 99.95% success rate over a rolling 30-day window." "Set up alerts to notify the on-call team if the API latency exceeds 200ms for more than 1% of requests." "Review current SLOs for the user authentication module and adjust the error budget threshold to 0.5%."

Tips & gotchas

Ensure your monitoring stack already collects the necessary metrics (e.g., request counts, errors) before attempting to define an SLO; the skill cannot generate raw data collection pipelines. Be specific about time windows (hourly, daily, monthly) and error definitions when setting targets to avoid ambiguous alerting behavior.