ln-71-operations-investigator
From the author
Diagnoses incidents from operational evidence and proposes recovery; does not change live systems.
Install
npx skills add levnikolaevich/claude-code-skills --skill ln-71-operations-investigator -a claude-code
Installs to .claude/skills/ln-71-operations-investigator/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 86
Security100
Provenance73
Maintenance100
Licence100
Adoption45
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- ln-97-observability-engineerlevnikolaevich/claude-code-skillsImplements structured diagnostics, correlation and justified metrics or traces; not incident investigation or a mandatory telemetry platform.DevOps★ 583
- ln-72-product-outcome-evaluatorlevnikolaevich/claude-code-skillsEvaluates observed product outcomes against a prior hypothesis; does not run experiments or change user treatment.Other★ 583
- ln-98-mutation-reliability-engineerlevnikolaevich/claude-code-skillsImplements transactions, idempotency and interrupted-operation recovery; not schema migration or a mandatory background-job platform.Other★ 583
- ln-99-database-lifecycle-engineerlevnikolaevich/claude-code-skillsPrepares and verifies schema migrations, database roles and isolated recovery or test resources; not query tuning or runtime mutation orchestration.Data★ 583
- ln-32-test-strategy-plannerlevnikolaevich/claude-code-skillsPlans risk-based test portfolios and acceptance evidence; does not write or execute tests.Testing★ 583
- incident-managementcbrock84/headcountRuns an operational incident from detection to closed action — declaring it and naming a commander, separating the people restoring service from the people communicating, keeping a timeline as it happens, deciding when it is over, and running a review that produces a small number of changes someone actually completes. Use this to set up an incident process, run one, work out why the same failure keeps recurring, or fix a review practice that generates findings nobody closes.Engineering★ 2.1K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in