CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

panel-log

Deep Log panel knowledge: react-window VariableSizeList virtualization, dynamic measured row heights, autoscroll/tail behavior, multi-format log normalization, and level/text filtering.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

83%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 content is well-structured, concise, and actionable with good code examples and clear progressive disclosure. It describes a viewer component rather than a multi-step destructive workflow, so workflow clarity is adequate but lacks explicit validation checkpoints.

DimensionReasoningScore

Conciseness

The body is efficient with code-first sections and minimal prose; only minor instances of restatement (e.g. 'Performance Notes' reiterates react-window behavior already described) could be trimmed, keeping it just below a 5.

4 / 5

Actionability

Provides mostly executable TypeScript snippets (VariableSizeList JSX, the NormalizedLogMessage interface, a filterMessages signature) with concrete details like 250ms debounce and resetAfterIndex; minor gaps (getItemSize implementation, LogRow rendering) prevent a 5.

4 / 5

Workflow Clarity

The skill documents component responsibilities and behaviors rather than a sequenced multi-step workflow; there are no validation checkpoints. For a read-only viewer this is acceptable, but no explicit sequencing or verification steps caps it at 3.

3 / 5

Progressive Disclosure

A clear overview with well-organized sections and a concrete file tree; all referenced paths (panels/Log/*, packages/suite-base/...) are one level deep and clearly signaled, giving easy navigation within the documented structure.

5 / 5

Total

16

/

20

Passed

Description

81%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 highly specific and comprehensive about capabilities, but lacks an explicit 'Use when...' trigger clause, which caps completeness. Trigger terms are domain-relevant but miss natural user-facing phrasings.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when working on the Log panel, debugging log rendering, or filtering/tailing log messages.'

Include user-natural terms and synonyms like 'log viewer', 'tail logs', 'log levels' rather than only technical jargon.

Mention the message formats by name in the trigger (ROS1/ROS2/Foxglove logs) to improve distinctiveness against generic logging skills.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — react-window VariableSizeList virtualization, dynamic measured row heights, autoscroll/tail behavior, multi-format log normalization, and level/text filtering — with comprehensive coverage of the panel's actions.

5 / 5

Completeness

The 'what' is clearly and thoroughly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Relevant domain terms (log viewer, filtering, virtualization, autoscroll) are present but the description omits natural trigger phrases a user would say (e.g. 'log panel', 'view logs', 'tail logs') and includes no file extensions or common synonyms.

3 / 5

Distinctiveness Conflict Risk

The narrow niche (a specific Log panel with named virtualization and normalization behavior) is mostly distinct from other skills, with only minor overlap risk with general panel/UI skills; no explicit 'when' trigger slightly weakens distinctiveness.

4 / 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

lichtblick-suite/lichtblick

Path

.github/skills/panel-log/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.