<Devsly/>
NotebookLM Watermark Remover
Remove the NotebookLM watermark from PDF slide exports — free, unlimited, and 100% in your browser.
View
NotebookLM Video Watermark Remover
Remove the NotebookLM watermark from every frame of your MP4 and auto-trim the end card — free and unlimited.
View
Gemini Watermark Remover
Remove the Gemini (Veo) sparkle watermark from every frame of your AI-generated MP4 — free and unlimited.
View
MCP https://devsly.io/mcp MCP Tools Best Skills API Docs

Keyboard Shortcuts

Navigation

Quick Search
⌘ / Ctrl + K
Toggle Dark Mode
⌘ / Ctrl + D
Close Dialogs
Esc

Tool Actions

Execute / Process
⌘ / Ctrl + Enter
Clear Input
⌘ / Ctrl + Shift + C
Copy Output
⌘ / Ctrl + Shift + X

Editor

Select All
⌘ / Ctrl + A
Undo
⌘ / Ctrl + Z
Redo
⌘ / Ctrl + Shift + Z

Updated today

by paulip114

sre-practice-skills

SRE Practice Skills for Claude Code

  • New — Created in the last 30 days
  • Active — Updated in the last 14 days
Works with
  • Claude

51 GitHub stars (51)

+51 in 3 days

  • 8 skills (8 skills found in its SKILL.md files)
  • 18 forks (18 forks)
  • Today last update (Last updated today)

Install

Skills CLI

npx skills add paulip114/sre-practice-skills

Asks which skills and agents to install. Just one: npx skills add paulip114/sre-practice-skills --skill sre-capacity-and-system-design — add -g for every project.

Claude Code

git clone https://github.com/paulip114/sre-practice-skillscp -r "sre-practice-skills/sre-capacity-and-system-design" ~/.claude/skills/

Copies the sre-capacity-and-system-design skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.

Plugin

/plugin marketplace add paulip114/sre-practice-skills

Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.

Skills can run code on your machine — read the SKILL.md first.

What it does

In the author's own words, from each skill's SKILL.md.

  • sre-capacity-and-system-design

    Use when designing or reviewing a distributed system for scale and resilience — NALSD capacity math, load balancing, load shedding, retries, deadlines, graceful degradation, cascading failures, simplicity, and distributed consensus for critical state. Based on Google SRE practice.

    sre-capacity-and-system-design/SKILL.md on GitHub (opens in a new tab)
  • sre-data-reliability

    Use when designing, operating or reviewing data pipelines, scheduled/cron jobs, backups and restores, or data integrity protections — pipeline SLOs, idempotency, handling stragglers and hot spots, distributed cron, defense in depth against data loss, and recovery testing. Based on Google SRE practice.

    sre-data-reliability/SKILL.md on GitHub (opens in a new tab)
  • sre-incident-response

    Use during or when preparing for a production incident — declaring it, incident command roles, the live incident document, status updates, mitigation, handoff, drills — and when systematically diagnosing a production problem. Based on Google's IMAG / Incident Command System practice.

    sre-incident-response/SKILL.md on GitHub (opens in a new tab)
  • sre-monitoring-and-alerting

    Use when designing or reviewing monitoring, dashboards and alerts — golden signals, white-box vs black-box, alert hygiene, and turning SLOs into multiwindow multi-burn-rate alerts (with Prometheus templates and a burn-rate calculator). Based on Google SRE practice.

    sre-monitoring-and-alerting/SKILL.md on GitHub (opens in a new tab)
  • sre-on-call-and-toil

    Use when designing on-call rotations and operational workload (page limits, interrupts, onboarding, team overload), measuring and eliminating toil with safe automation, or starting and growing an SRE practice in an organization. Based on Google SRE practice.

    sre-on-call-and-toil/SKILL.md on GitHub (opens in a new tab)
  • sre-postmortem

    Use when writing, reviewing or improving a blameless postmortem — structuring the document, quantifying impact, separating trigger from root causes, writing concrete action items, removing blameful language, or building postmortem culture and follow-up tracking. Based on Google SRE practice.

    sre-postmortem/SKILL.md on GitHub (opens in a new tab)
  • sre-release-and-launch

    Use when designing how code and config reach production (hermetic builds, progressive rollouts, canary analysis, rollback, config validation, reliability testing) or preparing a service or feature for launch (launch checklist, production readiness review, SRE engagement). Based on Google SRE practice.

    sre-release-and-launch/SKILL.md on GitHub (opens in a new tab)
  • sre-slos-and-error-budgets

    Use when defining, reviewing or refining SLIs and SLOs, writing or applying an error budget policy (release freezes, reliability prioritization, escalation), or quantifying incidents and projects in error-budget terms. Based on Google SRE practice.

    sre-slos-and-error-budgets/SKILL.md on GitHub (opens in a new tab)

Review before you install

A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.