Skill ops sre
This skill should be used when the user mentions keywords related to ops-sre.From its SKILL.md
npx -y skills add saitarrun/sdlc-ai-workflow --skill skill-ops-sreAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
0.6 KB, 110 tokens by cl100k_base, as published. Nobody here has run it
Skill: ops-sre
This skill provides methodology guidance for ops-sre work.
Key Principles
Apply best practices from the reference books when working on ops-sre tasks.
Process
- Read relevant input documents
- Apply methodology principles
- Document decisions and trade-offs
- Follow the patterns established in the codebase
Testing Your Work
Ensure quality by:
- Checking against the principles above
- Getting feedback from team members
- Verifying against acceptance criteria
- Following the SDLC process
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most ship operate skills give in 110 tokens
Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07
- Document a rollback plan before deploymentin 41 of 779, across 22 files
- Update the changelogin 21 of 779, across 19 files
- Run the test suitein 20 of 779
- Create an annotated git tagin 20 of 779
- Clean up feature flags after full rolloutin 18 of 779, across 10 files
- Verify deployment health after launchin 18 of 779, across 10 files
- Test both feature flag statesin 17 of 779, across 9 files
- Verify the working tree is cleanin 17 of 779
- Make database migrations backward-compatiblein 16 of 779, across 8 files
- Set up error monitoring before launchin 15 of 779, across 7 files
- Monitor metrics at each rollout stagein 14 of 779, across 5 files
- Create a GitHub releasein 14 of 779
Said here and by no other author read
- Apply best practices from reference books
- Read relevant input documents
- Apply methodology principles
- Follow established codebase patterns
- Check work against stated principles
- Get feedback from team members
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.