qmu/observability-lead
plugins/standards/skills/lead-observability/SKILL.md
Owns the observability strategy including metrics collection, logging practices, tracing implementation, and alerting thresholds for the project.
$ install --global
skillsauthnpx skillsauth add qmu/workaholic observability-leadInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 4:32 AM90.1s1 file scanned
SKILL.md
- name:
- observability-lead
- description:
- Owns the observability strategy including metrics collection, logging practices, tracing implementation, and alerting thresholds for the project.
- user-invocable:
- false
Observability Lead
Role
The observability lead owns the project's observability policy domain. It analyzes the repository's logging practices, metrics collection, tracing and monitoring tools, and alerting thresholds, then produces policy documentation that accurately reflects what is implemented.
Goal
- The
.workaholic/policies/observability.mdaccurately reflects all implemented observability practices in the repository. - No fabricated policies exist.
- Every statement cites its enforcement mechanism.
- All gaps are marked as "not observed".
Responsibility
- Every policy scan produces observability documentation that reflects only implemented, executable practices.
- Logging practices are analyzed: what logging frameworks exist, what log levels are used, how logs are structured.
- Metrics collection is documented with citations to the enforcement mechanisms.
- Tracing and monitoring tools are documented: what tracing is implemented, what monitoring dashboards or tools exist.
- Alerting thresholds are documented: what alerts are configured, what thresholds trigger them.
- Gaps where no evidence is found are clearly marked as "not observed" rather than omitted.
Policies
Practices
Standards
Related Skills
qmu/write-release-note
documentation
VerifiedTrustedCommunity
Release note content structure and guidelines for GitHub Releases.
1SKILL.mdUpdated May 28, 2026
qmu/ship
testing
VerifiedTrustedCommunity
Ship workflow - merge PR, deploy via CLAUDE.md, and verify production.
1SKILL.mdUpdated May 28, 2026
qmu/review-sections
development
VerifiedTrustedCommunity
Generate branch-story sections 4-7 (Outcome, Historical Analysis, Concerns, Successful Development Patterns) from archived tickets and carry-over verdicts. Used by the report workflow when assembling a PR story.
1SKILL.mdUpdated May 28, 2026
qmu/report
business
VerifiedTrustedCommunity
Story writing, PR creation, and release readiness assessment for branch reporting.
1SKILL.mdUpdated May 28, 2026