CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lightrun-live-runtime-debugging

Diagnose bugs and incidents using suitable captured Runtime History before focused live capture with Lightrun MCP. Use when static analysis or logs cannot explain the failure mechanism, when a hypothesis must be tested against runtime values or control flow, or when resuming Lightrun async actions. For latency, timeout, deadline, SLO, or hang diagnosis, use lightrun-slow-execution-diagnosis when available; if unavailable, continue here with best-effort evidence. Do not use for one-off production measurements (use lightrun-ask-prod when available; otherwise report the measurement-scope gap), pull-request review, code changes, setup, or deployment.

Quality

92%

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

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

An exceptionally well-crafted instruction-only skill body: fully actionable decision gates, explicit validation checkpoints and error-recovery feedback loops, and clean progressive disclosure into two real, well-signaled reference files. The only improvement space is token efficiency — the Quick Use Guide recap and a few near-duplicate lines across sections could be tightened without losing clarity.

DimensionReasoningScore

Conciseness

The body is dense and imperative, assumes competence (no concept explanations, no padding), e.g. "Treat exposed tool schemas and descriptions as authoritative" and "After each result, reassess information gain." It is not a 5 because the Quick Use Guide largely recapitulates earlier sections and some lines repeat nearly verbatim ("Inspect exposed tools and check inherited async action IDs before creating replacements" appears in both Runtime Preflight and the guide), tokens that could be trimmed.

4 / 5

Actionability

For an instruction-only skill the guidance is fully executable: concrete decision gates ("after two consecutive no-hit/timeouts from correctly targeted synchronous captures"), a specific error-mitigation matrix (verify custom timeout/window, increase collection window, retarget "at least one of source, location, signal definition, or leading hypothesis"), exact handoff fields, and a concrete troubleshooting URL. Every common case (no hits, timeout, targeting mismatch, pending async, preflight failure) has a prescribed, specific response, leaving nothing to guess.

5 / 5

Workflow Clarity

The Quick Use Guide gives a clear 9-step sequence with explicit validation checkpoints ("If the diagnosis evidence gate is met, proceed to cleanup and synthesis"; "Diagnose only when evidence connects the trigger, runtime state, executed path, failure point, and impact"), feedback loops for error recovery (Action Error Mitigation's retarget-before-retry rules), and checklists for the outcome branches and action cleanup. This matches the anchor-5 'explicit validation steps; feedback loops; checklists' pattern.

5 / 5

Progressive Disclosure

SKILL.md is a lean workflow overview with detail appropriately split into two real, one-level-deep reference files, each well-signaled at the exact point of need: "Read [MCP tool discovery](references/mcp-tool-discovery.md) before runtime calls" and "read [Async runtime actions](references/async-actions.md) before creating, polling, retrieving, or cancelling actions". Both files exist in the bundle, contain the promised content, and do not nest further references (async-actions.md back-links to SKILL.md only), matching the anchor-5 'clear overview with well-signaled one-level-deep references'.

5 / 5

Total

19

/

20

Passed

Description

87%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 that clearly states what the skill does, when to use it with concrete trigger conditions, and how it differs from sibling skills via explicit routing and negative scope. The only weaknesses are minor: the headline action 'diagnose bugs and incidents' is generic and a few natural trigger synonyms (debug, error, stack trace) are absent.

DimensionReasoningScore

Specificity

Names several concrete actions — "Diagnose bugs and incidents using suitable captured Runtime History before focused live capture with Lightrun MCP" and "resuming Lightrun async actions" — matching the 'several specific actions; minor gaps' anchor. It is not a 5 because "diagnose bugs and incidents" is itself generic and the description does not comprehensively enumerate the underlying operations (querying stored hits, placing probes, polling actions).

4 / 5

Completeness

Explicitly answers both questions: what ("Diagnose bugs and incidents using suitable captured Runtime History before focused live capture with Lightrun MCP") and when ("Use when static analysis or logs cannot explain the failure mechanism, when a hypothesis must be tested against runtime values or control flow, or when resuming Lightrun async actions"), plus explicit negative triggers ("Do not use for one-off production measurements..."). This matches the anchor-5 example structure of concrete 'what' plus concrete 'Use when' trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage: "bugs", "incidents", "static analysis or logs", "failure mechanism", "hypothesis", "latency, timeout, deadline, SLO, or hang", "pull-request review", "code changes", "setup, or deployment" — phrases users would naturally say. A few common synonyms are missing (e.g., "debug", "error", "stack trace", "production issue"), so it falls short of the comprehensive-synonyms anchor at 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Lightrun MCP runtime debugging with a history-first workflow) with explicit disambiguation: routes latency/hang cases to "lightrun-slow-execution-diagnosis", measurements to "lightrun-ask-prod", and excludes "pull-request review, code changes, setup, or deployment". Minimal conflict risk, matching the anchor-5 'clear niche with distinct triggers'.

5 / 5

Total

18

/

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-live-runtime-debugging/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.