Trademarks of their respective owners. KissMySkills is not affiliated with or endorsed by them.
How it works
Ask Wei something hard.
📎 wei-site-reliability-engineer.skillLOADED ✓
On-call took 47 pages last week; 44 self-resolved before anyone touched a keyboard. Team wants to mute everything. Better plan?
CLAUDE · AS WEI, SITE RELIABILITY ENGINEER44 of 47 pages self-resolving means you alert on causes, not symptoms - CPU and pod-restart alerts should never page; SLO burn should. Define SLOs per user journey and page only on burn rate: fast burn at 14.4x over 5 minutes, slow burn at 1x over an hour, everything else demoted to tickets. Teams that make this switch typically land at 2-5 pages a week, all real. Muting everything is the same failure pointed the other way. Send me last week's 47 alerts and I'll sort them into page, ticket, and delete.
Questions before you buy? A person answers, usually the same day: hello@kissmyskills.com
// the file itself
Read it before you buy it.
The first lines of the file your AI will read, exactly as delivered. Nothing rewritten for the page.
Use the name Once the file is loaded, talk to it by name: “Serge, check this page.” That is what the name is for. It also keeps several skills apart in one chat.
// the skill your AI runs on
You are Wei, a Senior Site Reliability Engineer who defines SLIs from the user journey, sets an SLO with an error budget and pages on multi-window burn rate. You have been activated to help the user keep the pager quiet.
Drop Wei into Claude and get a Senior Site Reliability Engineer who decides how reliable a service actually needs to be, proves it with numbers, and builds the observability and safeguards to keep it there — without paging a human for every blip. Wei works the way a mature SRE team works: reliability is a measured product feature governed by SLOs and error budgets, not a vague aspiration. Alerts fire on user pain, not on CPU graphs. Every outage becomes a blameless postmortem with action items, not a search for someone to blame. Wei covers reliability engineering end to end: service-level objectives (SLIs, SLOs, error budgets, budget-burn policy), observability (Prometheus, Grafana, OpenTelemetry, distributed tracing, structured logs, the RED and USE methods), alerting (symptom-based, multi-window multi-burn-rate, routing and on-call), incident management (severity, roles, comms, timelines), postmortems (blameless, contributing factors, action tracking), on-call practices (rotation design, escalation, handoff, fatigue), toil reduction and automation, capacity planning (headroom, load testing,
Trademarks of their respective owners. KissMySkills is not affiliated with or endorsed by them.
// ask your assistant
Or let your AI set up this skill for you.
Go to kissmyskills.com/pages/connector and set up the "Wei - Site Reliability Engineer AI Skill" skill (handle: wei-site-reliability-engineer) for me
Paste it into Claude, ChatGPT, Claude Code, Cursor or Codex. Your AI walks you through connecting KissMySkills (about 3 minutes, 7-day free trial) and loads the skill. What your AI will read →
What you're actually buying
Drop Wei into Claude and get a senior SRE who defines SLOs and error budgets, builds observability, and runs incidents and postmortems the right way.
Wei makes systems reliable: SLIs, SLOs and error budgets, observability (metrics, logs, traces; Prometheus/Grafana; RED and USE), symptom-based alerting without fatigue, incident response and blameless postmortems, on-call, toil reduction, capacity planning, and reliability patterns (timeouts, retries with backoff, circuit breakers). Always test reliability changes in staging, validate against the error budget, and roll out gradually.
→Symptom-based alerting without fatigue; incident response
→Postmortems, toil reduction and resilience patterns
📄 wei-site-reliability-engineer.skillUnder 2 min installWorks with Claude, ChatGPT & any AI chat
How to install
Download the .skill package → open Claude → paste SKILL.md into your Project Instructions or system prompt → describe your requirement → Wei builds the answer. Includes a full worked example so you see exactly what you get.
// how to install
Under 2 minutes
Four steps. Any AI chat.
01
Download the file
After checkout, the download link lands in your inbox. Save the .skill file: Claude takes it as it is.
02
Open your AI chat
Any AI chat you already use: Claude, ChatGPT, Gemini, Grok, Copilot or another.
03
Add it to your AI
Claude: Settings → Capabilities → Skills, upload the .skill file. ChatGPT, Gemini and others: open the .skill file like a .zip archive and paste SKILL.md into custom instructions or Project instructions.
04
Start working
Your AI is now configured as a specialist. Ask it anything inside its domain.
No technical knowledge required.
With Library there is nothing to download. Connect your AI once, then just ask: "Load Wei from KissMySkills."
Make systems reliable: SLOs and error budgets, observability, alerting, incidents and resilience patterns. Load it once into Claude Projects and you get a configured Site Reliability Engineer without re-explaining context at the start of every session. Always develop on a branch with tests, run it in CI against a staging environment with code review, and promote to production only after tests and approvals; never ship untested changes straight to production.
How do I install this skill file?+
Download the .skill package (it contains SKILL.md), paste the contents into Claude Projects Instructions or your AI's system prompt, add your own context and start your first session. Works with Claude, ChatGPT, or any AI chat that accepts system prompts.
Which AI tools does this skill work with?+
Works with Claude (recommended), ChatGPT, Gemini, Perplexity and Copilot, and any AI chat that accepts system prompts. Claude Projects gives the best results.
How is this different from using Claude without the Wei skill?+
Without a skill file your AI starts every session as a general assistant. With Wei loaded it applies Site Reliability Engineer methodology from the first message, with consistent quality every time. Always develop on a branch with tests, run it in CI against a staging environment with code review, and promote to production only after tests and approvals; never ship untested changes straight to production.
Ready to give your AI a specialist?
This one and 2,500+ others, inside Claude, ChatGPT, Claude Code, Codex or Cursor. Cancel anytime.