CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lightrun-ask-prod

Answer questions about production system behavior — captured variable values, execution durations, hit counts, and value distributions — using suitable existing Runtime History first, then live instrumentation with Lightrun MCP tools when needed. Use when the question requires runtime evidence rather than static code analysis (e.g. "show recent requests to this endpoint", "show the runtime distribution for this operation", "what values appear for this expression in production?", "which branch runs for customer X?"). Do not use for incident diagnosis, pull-request review, code changes, setup, or deployment. Route latency, timeout, deadline, SLO, or hang diagnosis to lightrun-slow-execution-diagnosis when available; route other diagnosis, or fallback when that skill is unavailable, to lightrun-live-runtime-debugging when available. If neither diagnosis skill is available, report the scope gap.

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 well-structured, schema-driven workflow skill: clear sequenced flow with validation checkpoints and feedback loops, correct progressive disclosure into a single real reference file, and concrete guidance throughout. Minor room to tighten verbose passages and to extend worked examples beyond the duration case.

Suggestions

Add one more brief schema-driven worked example (e.g. a snapshot/expression value query from Runtime History) so the most common question types get the same concrete call/result pattern as the duration example.

Tighten the owned-action lifecycle rules in step 6 and the reporting bullets in step 7 into shorter imperative lines to reduce token cost without losing semantics.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive with no re-explanations of concepts Claude already knows, but a few passages could be tightened — e.g. the owned-action rules in step 6 ('Treat only actions created or explicitly inherited for this request as owned; cancel only owned actions that are stale, duplicate, superseded, mistargeted, or unnecessary') and step 7's long bullet list — placing it between the lean (5) and minor-trim (4) anchors.

4 / 5

Actionability

Concrete guidance throughout — the capability-selection table, preflight gating rules, and a worked schema-driven example with an illustrative call and representative result — and the illustrative-identifier caveat is explicitly justified. However, only the duration case gets a worked example; snapshot/expression, execution-count, and distribution flows lack concrete call/result patterns, so it falls short of the 'examples cover the common cases' anchor.

4 / 5

Workflow Clarity

Seven clearly sequenced steps with explicit validation checkpoints — history suitability evaluation (step 3), preflight pass/fail with blocker reporting (steps 4-5), duplicate checks and status/result-availability semantics (step 6) — plus a feedback loop ('After repeated no-data or low-information results, revalidate or change the source, code location, signal, or window') and an error-handling table.

5 / 5

Progressive Disclosure

Shared discovery rules are appropriately split into references/mcp-tool-discovery.md with well-signaled one-level-deep links whose anchors ('#runtime-history-reads', '#source-discovery-preflight') exist in that file; the body retains only the skill-specific flow, matching the clear-overview anchor.

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.

An exemplary description: concrete capability list, explicit use and do-not-use triggers with verbatim example questions, and explicit routing to sibling skills. Third-person, dense, and unambiguous about scope.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'captured variable values, execution durations, hit counts, and value distributions' — plus both mechanisms ('suitable existing Runtime History first, then live instrumentation with Lightrun MCP tools'), comprehensively covering the skill's measurement domain.

5 / 5

Completeness

Explicitly answers both what ('Answer questions about production system behavior... using... Runtime History first, then live instrumentation') and when ('Use when the question requires runtime evidence rather than static code analysis'), with quoted trigger phrases and explicit 'Do not use for' exclusions.

5 / 5

Trigger Term Quality

Includes verbatim user phrasings ('show recent requests to this endpoint', 'what values appear for this expression in production?', 'which branch runs for customer X?') covering the main question types with natural synonyms, matching the comprehensive-coverage anchor rather than the 'a few natural terms missing' anchor.

5 / 5

Distinctiveness Conflict Risk

Explicitly excludes incident diagnosis, pull-request review, code changes, setup, and deployment, and routes latency/timeout/SLO/hang diagnosis to named sibling skills ('lightrun-slow-execution-diagnosis', 'lightrun-live-runtime-debugging') with a fallback rule — a clear niche with minimal conflict risk.

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-ask-prod/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.