Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
erichowens avatar

Site Reliability Engineer

  • 131 installs
  • 178 repo stars
  • Updated July 14, 2026
  • erichowens/some_claude_skills

Define SLOs, alerting, incident response, capacity planning, and runbooks so production SaaS and API services stay reliable, observable, and recoverable under real traffic and failure modes.

About

Embodies site reliability engineering practices for running production services: observability stacks, on-call readiness, deployment safety, infrastructure tuning, and blameless postmortems aimed at reducing downtime and toil for API-first and CLI-backed SaaS platforms.

  • SLO and error-budget design
  • Alert noise reduction
  • Incident response playbooks
  • Capacity and scaling reviews
  • Postmortem-driven hardening

Site Reliability Engineer by the numbers

  • 131 all-time installs (skills.sh)
  • Ranked #492 of 1,435 DevOps & CI/CD skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/erichowens/some_claude_skills --skill site-reliability-engineer

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs131
repo stars178
Last updatedJuly 14, 2026
Repositoryerichowens/some_claude_skills

What it does

Define SLOs, alerting, incident response, capacity planning, and runbooks so production SaaS and API services stay reliable, observable, and recoverable under real traffic and failure modes.

Files

SKILL.mdMarkdownGitHub ↗

Site Reliability Engineer

Expert in Docusaurus build health, MDX validation, and deployment safety for the Claude Skills showcase website. Prevents common build failures through pre-commit validation and automated health checks.

When to Use

Use for:

  • Pre-commit validation of markdown/MDX files
  • Catching Liquid template syntax errors
  • Validating SkillHeader component props
  • Checking for missing hero images/ZIP files
  • Pre-build link validation
  • Post-build health reports
  • Diagnosing Docusaurus build failures

Do NOT use for:

  • General DevOps (use deployment-engineer)
  • Kubernetes/cloud infrastructure (use kubernetes-architect)
  • Runtime monitoring/alerting (use observability-engineer)
  • Database migrations (use database-migrations agents)
  • Security scanning (use security-auditor)

Core Problem Domain

The 5 Recurring Anti-Patterns

#ProblemSymptomFix
1Liquid syntax in examplesLiquid templates break MDXWrap in backtick expression
2Unescaped angle brackets<70 parsed as HTMLUse <70
3Wrong SkillHeader propsSSG build failureUse fileName not skillId
4Missing critical filesSkill invisible on siteAdd to skills.ts
5Cache corruptionPhantom errorsClear .docusaurus, build

Quick Start

Install Hooks (One-Time)

npm run install-hooks

Manual Validation

npm run validate:liquid    # Liquid syntax
npm run validate:brackets  # Angle brackets
npm run validate:props     # SkillHeader props
npm run validate:all       # All checks

Clear Cache (When Stuck)

rm -rf .docusaurus build node_modules/.cache
npm run build

Pre-Commit Validation

The pre-commit hook automatically: 1. Liquid syntax - Scans for double-brace templates outside code blocks 2. Angle brackets - Finds <digit patterns 3. SkillHeader props - Validates component usage 4. Required files - Checks hero images, ZIPs exist

Speed: Under 5 seconds for typical commits

Expert vs Novice Approach

NoviceExpert
Runs full build to checkPre-commit catches 90% in 5 seconds
Manual cache clearingAuto-detect cache issues
Ignores warningsZero-tolerance for broken links
Simple regex validationContext-aware (skips code blocks)

Anti-Patterns

Anti-Pattern: Full Build for Validation

What it looks like: npm run build to check for errors Why wrong: Minutes vs seconds, slow feedback Instead: npm run validate:all (under 30 seconds)

Anti-Pattern: Ignoring Build Warnings

What it looks like: "Build succeeded, ship it!" (ignoring warnings) Why wrong: Broken links = poor UX, tech debt Instead: Post-build validation fails on warnings

Anti-Pattern: Naive Regex Validation

What it looks like: /\{\{.*?\}\}/ (matches in code blocks too) Why wrong: False positives in code examples Instead: Track code block state, skip protected regions

Scripts (in scripts/ folder)

ScriptPurpose
validate-liquid.jsDetect unescaped Liquid syntax
validate-brackets.jsDetect unescaped angle brackets
validate-skill-props.jsValidate SkillHeader component

Troubleshooting Quick Reference

IssueDiagnosisFix
Hook not runningls -la .git/hooks/pre-commitchmod +x or reinstall
False positivesPattern in code blockCheck ``` markers
Slow validationtime npm run validate:allOptimize glob patterns

Success Metrics

After installing hooks:

  • Build failure rate: 15% → under 2%
  • Time to diagnose errors: 10 min → under 1 min
  • Validation speed: Under 30 seconds

Reference Files

  • references/validation-logic.md - Context-aware detection patterns
  • references/ci-cd-integration.md - GitHub Actions, health reports
  • scripts/ - Working validation scripts

---

Prevents: Liquid errors | Angle bracket failures | Prop mismatches | Missing assets | Broken links

Use with: skill-documentarian (sync) | docusaurus-expert (advanced config)

Related skills

DevOps & CI/CDmonitoringdeployinfra

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.