Skip to content
TrustedSkillsbeta
Back to all skills

Slo Implementation

Checked
wshobson·vlatest·devops·MIT

This skill provides a deliberately slow, iterative implementation process to encourage thoughtful design and reduce rapid-fire development.

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 wshobson/agents --skill slo-implementation -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

wshobson

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 passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    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 wshobson/agents at 46891e7e60.

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

Commit
46891e7e60
Manifest
plugins/observability-monitoring/skills/slo-implementation/SKILL.md
Scanned
2 files, 313 lines
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

What it does

The slo-implementation skill enables AI agents to understand, define, and implement Service Level Objectives (SLOs) within software development or operations workflows. It provides guidance on setting measurable targets for service reliability, performance, and availability, ensuring alignment with business goals.

When to use it

  • When defining reliability metrics for a new cloud-based application
  • During the planning phase of an IT service improvement initiative
  • When creating documentation for SLOs in DevOps or site reliability engineering (SRE) practices

Key capabilities

  • Provides templates and frameworks for setting SLOs
  • Helps translate business requirements into technical performance targets
  • Offers guidance on monitoring and reporting against defined SLOs

Example prompts

  • "Define an SLO for a web application with 99.9% uptime."
  • "Create a service level objective for response time under normal load conditions."
  • "Explain how to monitor and report on SLO compliance in an SRE environment."

Tips & gotchas

  • Ensure alignment between SLOs and business priorities before implementation.
  • Use this skill in conjunction with monitoring tools to track progress effectively.