sc-observability
sc-observability contains 7 collected skills from randlee, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Use when the user says things like "bring sc-observability into an existing Rust project" or "adopt sc-observability in a codebase that already has logging". Adopts sc-observability incrementally with a logging-first path and focused migration references for log, tracing, or custom JSONL setups.
Use when the user says things like "set up sc-observability in a new Rust project" or "add structured logging to a new Rust app". Bootstraps a new project with sc-observability from crates.io using the shared light-logging house style, ~/.<app> log roots, and a rendered starter template.
Use when the user says things like "review this project for sc-observability best practices" or "check whether our logging setup matches the sc-observability standard". Reviews a Rust project's observability setup against the shared house style and recommends missing baseline items and easy improvements.
Orchestrate phased work where cobs is the sole developer and quality-mgr enforces the QA gate for sc-observability.
Orchestrate multi-sprint phase execution as team-lead (ARCH-ATM). Manages sprint waves, scrum-master lifecycle, PR merges, cobs reviews, and integration branch strategy. This skill is for the TEAM-LEAD only, not for scrum-masters.
Reusable QA orchestration skill for GitHub PRs. Use for multi-pass QA, CI monitoring with `atm gh monitor`, one-shot PR reporting with `atm gh pr report`, and template-driven findings/final quality reports.
Session initialization for the team-lead identity. Confirms identity and detects whether a full team restore is needed. Only run when ATM_IDENTITY=team-lead.