lightrun-error-remediation-automation

Guide deterministic runtime investigations in environments using Lightrun MCP tools, with preflight gating, recovery/resume rules, evidence-first diagnosis, PR-first fix proposal delivery, and local source-code fallback only when PR creation is not possible.

1.00x

Quality

72%

Does it follow best practices?

Impact

28%

1.00x

Average score across 1 eval scenario

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/lightrun-error-remediation-automation/SKILL.md

Quality

Content

77%

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 well-sequenced, highly actionable runtime-debugging workflow with strong validation checkpoints and a clear output contract, but it is long and repetitive and keeps most detail inline rather than pushing it to reference files. Consolidating the duplicated Quick Use Guide/Flow content and extracting the state-storage and output-contract detail would improve conciseness and progressive disclosure.

Suggestions

Merge the 'Quick Use Guide' and 'Flow' sections into one authoritative sequenced workflow to remove the substantial overlap and cut length.

Extract the detailed Storage Discovery Protocol (Preconditions state-persistence rules) and the full Output Contract into separate reference files under references/, keeping SKILL.md a concise overview that links to them.

Dedupe the 'Mandatory Runtime Action Result Gate' against 'Investigation Principles' so each rule appears once and cross-references the other.

Dimension	Reasoning	Score
Conciseness	The 338-line body is procedural and avoids explaining concepts Claude already knows, but contains notable redundancy — the 'Quick Use Guide' largely duplicates the 'Flow' section and the 'Mandatory Runtime Action Result Gate' restates 'Investigation Principles' — so it is mostly efficient but could be tightened, matching the score-2 anchor.	2 / 3
Actionability	It gives concrete, executable guidance: explicit blocker codes ('state-storage-unavailable', 'reproduction-required', 'runtime-source-ambiguous'), exact cleanup/cancellation rules, a fully specified output contract, and a real linked reference file, matching the 'fully actionable, specific, copy-ready' anchor for an instruction-only skill.	3 / 3
Workflow Clarity	The 'Flow' is a numbered multi-step process with Tools and Success criteria per step, explicit validation checkpoints (mandatory runtime action result gate, preflight pass/fail), feedback loops (action error mitigation), and a Runtime Quality Checklist, matching the 'clear sequence with explicit validation and checklists' anchor.	3 / 3
Progressive Disclosure	It uses one well-signaled one-level-deep reference (references/mcp-tool-discovery.md, verified to exist) with anchors, but most detail (state-storage protocol, output contract, cleanup rules) remains inline in a monolithic 338-line SKILL.md rather than being split out, matching the 'some structure but content that should be separate is inline' anchor.	2 / 3
	Total	10 / 12 Passed

Description

67%

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

The description is specific and distinctive, clearly carving out a Lightrun runtime-debugging niche, but it lacks an explicit 'when to use' trigger clause and its trigger terms lean technical rather than mirroring natural user phrasing. Adding a 'Use when...' sentence with common user-facing terms would lift the two lower dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when investigating runtime incidents or bugs in services monitored by Lightrun, reproducing hard-to-reproduce errors, or proposing code fixes from runtime evidence.'

Soften jargon like 'deterministic runtime investigations' and 'preflight gating' with natural user phrasing such as 'debug production runtime errors' and 'source checks before capturing evidence'.

Add common keyword variants users might say ('runtime debugging', 'production incident', 'live snapshot', 'trace the failure') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('preflight gating, recovery/resume rules, evidence-first diagnosis, PR-first fix proposal delivery, and local source-code fallback'), matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	It clearly answers 'what does this do' but provides no explicit 'Use when...' trigger guidance, so per the rubric a missing when-clause caps completeness at 2 even though the what is strong.	2 / 3
Trigger Term Quality	It includes relevant domain terms ('Lightrun', 'runtime investigations', 'fix proposal', 'PR') but leans technical ('deterministic', 'preflight gating') and omits common natural variations a user would actually say, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The Lightrun-specific runtime debugging niche with PR-first fix delivery is clearly distinct and unlikely to trigger for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: lightrun-platform/lightrun-ai
Commit: b5e7d41

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.