CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lightrun-slow-execution-diagnosis

Diagnose performance incidents in running services with Lightrun MCP: slow endpoints, latency or SLO regressions, timeouts, deadline-exceeded errors, hangs, and slowness that is intermittent, sporadic, occasional, happens only sometimes, or appears only under load. Use relevant Runtime History for state/path context before creating live actions. Prefer this over lightrun-live-runtime-debugging, including for mixed slow-and-incorrect cases. Use slow-execution snapshots when a duration boundary separates problematic executions; use focused active-path snapshots or call stacks for known hangs that may not reach an end marker. Select the narrowest code section, derive an evidence-based threshold, and correlate captured state with code and telemetry. Use lightrun-live-runtime-debugging for non-performance diagnosis and lightrun-ask-prod for one-off timing, when available; otherwise report the scope gap. Do not use for pull-request review, code changes, setup, deployment, or post-deployment performance validation.

Quality

94%

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

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

A strong, tightly written operational skill: correct decision architecture with checkpoints, validation gates, a concrete quickstart, and clean one-level reference structure. The only weaknesses are minor repetition that could be trimmed and a missing concrete create example for the non-threshold snapshot path.

Suggestions

Deduplicate repeated gating phrases ('including baseline timing' appears in three sections; preflight applicability is stated twice) to tighten the body without losing meaning.

Add a short concrete snapshot_create example (mirroring the execution_duration_create quickstart) for the non-threshold path in 'Choose the evidence path'/'Capture and correlate', since that path currently gives only directional guidance.

DimensionReasoningScore

Conciseness

The body is dense, imperative, and assumes Claude's competence — it never explains what Lightrun or snapshots are conceptually — matching 'Efficient; minor instances of over-explanation that could be trimmed'. Not 5 because of small redundancies: 'including baseline timing' appears three times, preflight timing is restated ('Run preflight only when creating a live action'), and phrases like 'state the gap, preserve useful findings, and continue' could be tightened.

4 / 5

Actionability

The quickstart gives a fully parameterized, copy-paste-ready execution_duration_create call with a concrete polling sequence and explicit backoff schedule (2s, then 1/2/5s, ~15s cap), plus a concrete runtime/version gate table — 'Mostly executable guidance; concrete code or commands with minor gaps'. Not 5 because the non-threshold path only says 'Create a focused regular snapshot and store its action ID' without a concrete create example, and correlation guidance remains directional.

4 / 5

Workflow Clarity

Clear end-to-end sequence (activation gate → historical evidence → preflight → evidence-path choice → target selection → runtime gates → capture/correlate → single outcome) with an explicit '**Checkpoint:**', validation gates (source-discovery pass/fail, 'make one create attempt. Revalidate targeting or capability failures before repeating'), and error-recovery outcomes (blocked/inconclusive with required contents). Matches the anchor requiring explicit validation steps and feedback loops; live-action creation is also gated by cleanup rules.

5 / 5

Progressive Disclosure

Clear overview with well-signaled, verified one-level-deep references: [Runtime History reads](references/mcp-tool-discovery.md#runtime-history-reads), [source-discovery preflight](references/mcp-tool-discovery.md#source-discovery-preflight), and [Slow-execution snapshot workflow](references/slow-execution-snapshot-workflow.md) all resolve to real files and sections, and the reference files contain no nested references. Detail (threshold derivation, marker placement, discovery rules) is appropriately split out of SKILL.md.

5 / 5

Total

18

/

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.

The description is exemplary: concrete capabilities, exhaustive natural-language trigger synonyms including intermittent-slowness variants, explicit what/when with exclusions, and unambiguous routing versus sibling Lightrun skills. It is long but every clause carries trigger or routing signal rather than padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Use relevant Runtime History for state/path context", "use slow-execution snapshots when a duration boundary separates problematic executions", "Select the narrowest code section, derive an evidence-based threshold, and correlate captured state with code and telemetry" — with comprehensive coverage of the diagnosis workflow. This matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage', not the level below where coverage has minor gaps.

5 / 5

Completeness

Explicitly answers both: what ("Diagnose performance incidents in running services with Lightrun MCP" plus the enumerated mechanisms) and when (trigger conditions, "Prefer this over lightrun-live-runtime-debugging", and "Do not use for pull-request review, code changes, setup, deployment, or post-deployment performance validation"). Matches the anchor requiring concrete trigger phrases for both, not the level below where 'when' is only present.

5 / 5

Trigger Term Quality

Exhaustive natural-term coverage with synonyms: "slow endpoints, latency or SLO regressions, timeouts, deadline-exceeded errors, hangs, and slowness that is intermittent, sporadic, occasional, happens only sometimes, or appears only under load" — exactly the synonym-rich anchor, well above 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

Clear niche (Lightrun performance diagnosis) with explicit routing to sibling skills — "Use lightrun-live-runtime-debugging for non-performance diagnosis and lightrun-ask-prod for one-off timing" — plus explicit exclusions, giving minimal conflict risk per the 'Clear niche with distinct triggers' anchor.

5 / 5

Total

20

/

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-slow-execution-diagnosis/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.