From sysadmin-skills
Operations task verification gate before claiming work is complete. This skill should be used before closing incidents, finalizing change requests, sending resolution notifications, or when asking "is this resolved?", "can we close this?", "is the change complete?", or verifying SLO compliance after an incident. Evidence before claims — verify operational status first.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sysadmin-skills:done-opsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Core principle:** Evidence before claims, always.
Core principle: Evidence before claims, always.
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
If the service has not been verified as operational in this session, the task cannot be claimed as complete.
This skill is loaded as a gate by /incident and /change-request. It does not need to be invoked directly when using those workflows.
Before claiming any operational task is complete:
| Check | Required Evidence |
|---|---|
| Service restored | Service is accessible and functioning (confirmed by monitoring or manual test) |
| User confirmation | Affected user/team confirms the issue is resolved |
| Monitoring stable | No recurring alerts for the affected component within the observation period |
| Documentation complete | Timeline, actions taken, resolution, and follow-up items recorded |
| Problem record | Created if root cause is unknown or incident is recurring |
| Communication sent | Resolution notification sent to all parties who received the initial alert |
| SLO compliance checked | (Optional) Error budget impact estimated; note if budget is now < 10% |
| Check | Required Evidence |
|---|---|
| Implementation complete | All steps in the implementation plan executed |
| Validation passed | Post-implementation checks confirm expected behavior |
| No regression | Related services unaffected (checked, not assumed) |
| Rollback not triggered | No rollback criteria were met during implementation |
| PIR scheduled | Post-Implementation Review scheduled within required timeframe |
| Users notified | Affected users informed of completion (if applicable) |
| Check | Required Evidence |
|---|---|
| All components operational | Each affected component verified and set to Operational |
| Resolved update posted | Final status update published with summary |
| Duration recorded | Accurate start and end times documented |
| Subscribers notified | Status page notification delivered |
After resolution, observe before final closure:
| Priority | Observation Period |
|---|---|
| P1 | 1-2 hours of stability |
| P2 | 2-4 hours of stability |
| P3 | Confirm at next check-in |
| P4 | Immediate closure acceptable |
npx claudepluginhub bouob/claude-plugins --plugin sysadmin-skillsProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.