CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

panel-state-transitions

Deep StateTransitions panel knowledge: TimeBasedChart segments, message-path extraction, preloaded-range subscription with 250ms batch flush, block+currentFrame merge, and messagesToDataset.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/panel-state-transitions/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 body is a well-structured, mostly concise map of the StateTransitions panel with a clear data-flow sequence and concrete file locations, weakened mainly by a pseudocode code stub instead of executable guidance and some repetition around the batch-flush detail.

Suggestions

Replace the messagesToDataset pseudocode stub with a concrete, executable snippet (or explicitly justify the pseudocode and point to the real implementation file).

De-duplicate the 250ms batch-flush explanation so it appears once, removing the repetition across Data Flow, the dedicated section, and Performance Notes.

Consolidate the Structure diagram and Key Files listing to avoid repeating the same file set in two sections.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no basic-concept padding), but the "250ms batch flush" detail is restated across the Data Flow, its own section, and Performance Notes — a minor trim opportunity that keeps it below the lean anchor at 5.

4 / 5

Actionability

It gives concrete file paths (Key Files) and a clear data flow, but the only code block is a pseudocode stub ("// iterate all messages, extract value at path") rather than executable code, matching the pseudocode anchor at 3.

3 / 5

Workflow Clarity

The Data Flow section is a clearly ordered six-step sequence of how messages move through the panel; no validation checkpoints are present, but they are not really applicable to a descriptive data-flow rather than a destructive operational procedure, so it sits above 3.

4 / 5

Progressive Disclosure

Content is organized into clear, well-signaled sections with a clearly marked one-level cross-skill reference ("load `message-path` skill"); the minor gap is that the file listing is duplicated between the Structure diagram and the Key Files section, and the body slightly exceeds the under-50-line simple-skill threshold.

4 / 5

Total

15

/

20

Passed

Description

58%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 specific and distinctively tied to a named panel, listing several concrete internal components, but it lacks any "Use when..." trigger guidance and leans heavily on implementation jargon over natural user keywords.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should load this skill (e.g. working on or debugging the StateTransitions panel).

Lead with natural trigger phrasing users would actually say (e.g. 'state transitions', 'timeline of discrete state changes') before the internal component list.

Frame the listed items as actions/capabilities rather than only 'knowledge of' nouns to lift specificity toward the comprehensive-action anchor.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete components — "TimeBasedChart segments, message-path extraction, preloaded-range subscription with 250ms batch flush, block+currentFrame merge, and messagesToDataset" — but frames them as knowledge nouns rather than actions, so it falls short of the comprehensive-action anchor at 5.

4 / 5

Completeness

The "what" is reasonably clear (deep knowledge of the panel's internals), but there is no "Use when..." clause or any trigger guidance, so per the rubric cap completeness cannot exceed 3.

3 / 5

Trigger Term Quality

Relevant domain keywords like "StateTransitions panel" and "message-path" are present, but most terms ("preloaded-range subscription", "block+currentFrame merge", "messagesToDataset") are internal implementation jargon rather than natural user phrasing, and common synonyms/variations are missing.

3 / 5

Distinctiveness Conflict Risk

It is clearly tied to the specific StateTransitions panel niche, with only minor overlap risk from the shared "TimeBasedChart" component also used by other panels; not a 5 because no explicit trigger phrasing disambiguates it.

4 / 5

Total

14

/

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-state-transitions/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.