CtrlK
BlogDocsLog inGet started
Tessl Logo

langfuse-incident-runbook

Troubleshoot and respond to Langfuse-related incidents and outages. Use when experiencing Langfuse outages, debugging production issues, or responding to LLM observability incidents. Trigger with phrases like "langfuse incident", "langfuse outage", "langfuse down", "langfuse production issue", "langfuse troubleshoot".

68

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A well-structured, highly actionable incident runbook with time-boxed steps, decision-table checklists, and a verification checkpoint. Its main weaknesses are duplicated content between the body and the orphaned references/implementation.md file, and the absence of any link to that reference from the body.

Suggestions

Link references/implementation.md from the body (e.g., a '## Advanced troubleshooting' section pointing to it) so the bundle file is discoverable rather than orphaned.

De-duplicate the Step 1 triage script and the 'Error Handling' table against implementation.md to avoid maintaining the same guidance in two places.

Make the verify→fix→retry loop explicit in Step 5 (e.g., 'if trace count is 0 or ERROR, return to Step 4 and re-apply the matching procedure').

DimensionReasoningScore

Conciseness

Mostly lean tables and executable code with no concept padding, but the 'Error Handling' table duplicates Step 2's symptom/cause/action rows and references/implementation.md repeats the Step 1 diagnosis script, so not every token earns its place.

2 / 3

Actionability

Provides copy-paste-ready bash (curl health/auth checks, docker restart), concrete TypeScript config (exportIntervalMillis, maxExportBatchSize, flushAt), and specific decision tables throughout rather than abstract direction.

3 / 3

Workflow Clarity

Time-boxed numbered steps (2-min triage → determine type → fallback → resolution → verify → review) with decision-table checklists (severity, symptom→action) and an explicit Step 5 verification checkpoint.

3 / 3

Progressive Disclosure

The body is well-sectioned, but references/implementation.md is never linked from the SKILL.md body, and its diagnosis/resolution code overlaps inline body content rather than being cleanly split and signaled as a one-level-deep reference.

2 / 3

Total

10

/

12

Passed

Description

90%

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 that answers both 'what' and 'when' with explicit, natural trigger phrases and a tight Langfuse-specific niche. The only soft spot is action specificity, where the verbs are generic operations language rather than distinct concrete operations.

DimensionReasoningScore

Specificity

Names the domain and several actions ('Troubleshoot and respond to Langfuse-related incidents and outages', 'debugging production issues', 'responding to LLM observability incidents'), but the verbs are generic ops language rather than crisply distinct concrete operations like the score-3 anchor ('extract text... fill forms... merge documents').

2 / 3

Completeness

Clearly states what it does ('Troubleshoot and respond to Langfuse-related incidents and outages') and when to use it ('Use when experiencing Langfuse outages, debugging production issues...'), plus an explicit 'Trigger with phrases like...' clause.

3 / 3

Trigger Term Quality

Lists natural phrases a user would actually say — 'langfuse incident', 'langfuse outage', 'langfuse down', 'langfuse production issue' — giving good coverage of common variations rather than technical jargon.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to Langfuse with every trigger prefixed by 'langfuse', giving it a clear niche that is unlikely to fire for or conflict with other skills.

3 / 3

Total

11

/

12

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.