CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lightrun-error-remediation-automation

Guide deterministic runtime investigations in environments using Lightrun MCP tools, using suitable Runtime History before new live actions, 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.

Quality

68%

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

Fix and improve this skill with Tessl

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

Quality

Content

58%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 skill body delivers an exceptionally well-gated investigation workflow with explicit sequencing, validation checkpoints, error recovery, and a clean one-level reference file — but it pays for this with heavy redundancy, telling the same story three ways across the Quick Use Guide, Flow, and checklist, and it never grounds the abstract 'choose tools by description' guidance in a concrete example. Condensing the duplicated sections would reclaim a large token budget at no loss of clarity.

Suggestions

Collapse the 'Quick Use Guide' and 'Flow' sections into one workflow — they duplicate the same numbered steps (including sub-steps 3.1-3.9) almost verbatim — and cut checklist items that merely restate rules already enforced by the gates.

Add one or two concrete example Lightrun MCP tool invocations with expected input arguments and a sample result payload (e.g., a snapshot status check and a Runtime History query) so the abstract 'choose from currently available tools' guidance has an executable anchor.

Move the detailed storage-discovery protocol and state-persistence rules into a reference file (like mcp-tool-discovery.md) and keep only the decision rules inline, so SKILL.md works as the overview the progressive-disclosure structure expects.

DimensionReasoningScore

Conciseness

The body states the same workflow and rules three times: the 'Quick Use Guide' steps 1-11 duplicate the 'Flow' steps 1-10 nearly verbatim (including identical sub-steps 3.1-3.9), 'Investigation Principles' restates the result-gate and PR-gating rules, and the 30-item 'Runtime Quality Checklist' repeats them again. This matches the anchor for noticeably verbose with several padded sections; it is above anchor 1 only because the individual passages avoid explaining concepts Claude already knows.

2 / 5

Actionability

There is concrete guidance in places — exact blocker codes ('state-storage-unavailable', 'runtime-source-ambiguous', 'reproduction-required'), the exact skillName argument, a storage priority list, and a detailed output contract — but the actual tool usage is left abstract ('choose from currently available Lightrun MCP runtime tools based on their descriptions and fit to...') with no example invocations or expected output shapes anywhere. This sits between anchor 3's incomplete concrete guidance and anchor 4's mostly executable guidance; the pervasive tool-selection abstraction and missing examples keep it at 3.

3 / 5

Workflow Clarity

The multi-step process is explicitly sequenced with per-step success criteria, hard validation gates (MCP preflight, the 'Mandatory Runtime Action Result Gate', resume criteria), explicit error-recovery feedback loops (Action Error Mitigation, Missing-MCP recovery, blocker/reproduction-required handoffs), and a checklist for the complex process. This matches the top anchor exactly; it is well above anchor 4, which allows minor validation gaps.

5 / 5

Progressive Disclosure

The bundle structure is good: detailed discovery/preflight material lives in references/mcp-tool-discovery.md, every in-body link and anchor (Source discovery, Missing-MCP recovery, Runtime History reads, Source selection guidance) resolves to a real heading in that file, and references are one level deep and clearly signaled. It is not a 5 because the 356-line body itself is a monolithic detailed specification with the duplicated workflow sections rather than a lean overview, i.e. some content that belongs in reference files is inlined.

4 / 5

Total

14

/

20

Passed

Description

62%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.

The description communicates a specific, well-differentiated Lightrun runtime-debugging workflow with concrete capability claims, but it reads as an internal process specification rather than a user-facing trigger. Its main weaknesses are the absence of any 'Use when...' trigger guidance and jargon-heavy phrasing that misses the natural terms users would say when they need this skill.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user reports a runtime error, production incident, or bug in a service monitored by Lightrun, or asks to investigate, reproduce, or fix runtime behavior with Lightrun MCP tools.'

Include natural synonyms users would actually say — 'debug', 'investigate an incident', 'production error', 'runtime error', 'Lightrun snapshot/metric/log' — alongside the existing technical terms.

Trim internal-process jargon like 'deterministic', 'preflight gating', and 'recovery/resume rules' in favor of plain capability statements, since these add tokens without adding user-recognizable triggers.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — 'using suitable Runtime History before new live actions', 'preflight gating', 'recovery/resume rules', 'evidence-first diagnosis', 'PR-first fix proposal delivery, and local source-code fallback' — which matches the anchor for several specific actions with minor gaps. It is not a 5 because these are workflow-process abstractions rather than fully concrete, comprehensive capabilities, and it falls clearly above anchor 3 (only 1-2 concrete actions).

4 / 5

Completeness

The 'what' is clearly stated (a guided runtime investigation workflow ending in a fix proposal), but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is above anchor 2 because the 'what' is specific and comprehensive, not vague.

3 / 5

Trigger Term Quality

It includes some relevant keywords ('runtime investigations', 'Lightrun MCP tools', 'fix proposal', 'PR') but is dominated by technical jargon ('deterministic', 'preflight gating', 'recovery/resume rules') and misses the natural phrases a user would say, such as 'debug', 'incident', 'production error', 'snapshot', or 'log'. This matches the anchor for some relevant keywords missing common variations, and is below anchor 4's good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

'Guide deterministic runtime investigations in environments using Lightrun MCP tools' carves out a clear niche tied to a specific vendor toolchain, with distinct triggers (Runtime History, Lightrun actions, PR-first fix delivery) and minimal overlap risk with generic debugging skills. This matches the anchor for a clear niche with distinct triggers.

5 / 5

Total

15

/

20

Passed

Validation

100%

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

Path

skills/lightrun-error-remediation-automation/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.