CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

incident-triage

Structured incident investigation for OpenShift using the Five Whys methodology, investigation guardrails, Prometheus metric analysis, and adversarial due diligence. Orchestrates multi-resource diagnosis across Deployments, ReplicaSets, Pods, Services, and cluster resources to trace from observed symptoms to root cause. Use when: - "investigate this incident" - "triage this alert" - "root cause analysis" - "what caused this outage" - User mentions "five whys", "incident", "triage", "RCA" NOT for single-resource issues with clear patterns (use /debug-pod, /debug-scc, /debug-rbac, or /debug-network instead).

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a highly actionable, well-sequenced investigation workflow with explicit checkpoints, validation, and error handling throughout. Its main weakness is token efficiency: the MCP tool list, prerequisites, and related-skill routing are each duplicated across sections, inflating the file without adding guidance. Bundle references are appropriately one level deep, though one bundled reference file is orphaned.

Suggestions

Deduplicate the MCP server/tool rosters: the identical list appears in both Prerequisites and Dependencies — keep one (Dependencies) and link to it from the other.

Consolidate the related-skills routing, which appears three times (When to Use, Dependencies, and the Step 6 output template), into a single authoritative table.

Either reference or remove the orphaned references/selinux-troubleshooting.md, and consider moving the per-step markdown output templates to a references/ file to slim the main body.

DimensionReasoningScore

Conciseness

The content is mostly efficient and doesn't explain concepts Claude already knows, but the MCP tool roster is duplicated verbatim in Prerequisites and Dependencies, the related-skills routing table appears three times (When to Use, Dependencies, and the Step 6 output template), and the Prerequisites and Dependencies sections substantially repeat each other. This is more than the "minor instances" of the 4 anchor, so it fits the "could be tightened" 3 anchor.

3 / 5

Actionability

Every workflow step names the exact MCP tool with concrete parameters (e.g., "tailLines: 50", labelSelector from ".spec.selector.matchLabels"), gives executable PromQL patterns ("{__name__=~\".*<keyword>.*\"}", "topk(10, ...)", "rate()"), and closes with concrete verification commands ("oc get events -n <namespace> --sort-by='.lastTimestamp' | tail -20"). Remediation commands are placeholders only because they depend on findings, which is inherent to a diagnosis skill.

5 / 5

Workflow Clarity

Six clearly sequenced steps with an explicit "**WAIT for user confirmation before proceeding.**" checkpoint at every phase transition, per-step error handling, a guardrail compliance table, and a feedback loop ("If confidence < 0.7: recommend gathering additional evidence or escalating"). This matches the 5 anchor: explicit validation steps plus error-recovery loops, reinforced by the upfront Human-in-the-Loop requirements.

5 / 5

Progressive Disclosure

References are one level deep and clearly signaled ("[setup](references/prerequisites.md)", "[references/debugging-patterns.md](references/debugging-patterns.md)"), and both referenced paths exist in references/. Minor gaps keep it below 5: selinux-troubleshooting.md is present in the bundle but never referenced from the body, and the long per-step output templates are fully inlined in SKILL.md rather than partially offloaded. It is above the 3 anchor because the references that are used are clearly signaled and well placed, not buried.

4 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person, concrete, and specific about both capabilities and scope, with an explicit "Use when" trigger list and an explicit exclusion clause that separates it from adjacent debug skills. No vague fluff or over-claims were found.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — "Five Whys methodology, investigation guardrails, Prometheus metric analysis, and adversarial due diligence" and "multi-resource diagnosis across Deployments, ReplicaSets, Pods, Services" — with comprehensive coverage of the investigation, metrics, RCA, and due-diligence scope. Fits the 5 anchor rather than 4 because no capability area is conspicuously missing.

5 / 5

Completeness

Explicitly answers both "what" (two-sentence capability description) and "when" (a literal "Use when:" list with concrete trigger phrases), and adds a "NOT for single-resource issues" exclusion. This mirrors the 5 anchor example's structure exactly.

5 / 5

Trigger Term Quality

Includes natural user phrases ("investigate this incident", "triage this alert", "what caused this outage") plus synonyms ("root cause analysis", "RCA", "five whys"). Matches the comprehensive-synonyms anchor at 5; no common variation is missing.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (multi-resource incident RCA) and explicitly disambiguates from sibling skills: "NOT for single-resource issues with clear patterns (use /debug-pod, /debug-scc, /debug-rbac, or /debug-network instead)". Minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

RHEcosystemAppEng/agentic-plugins

Path

rh-developer/skills/incident-triage/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.