CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

layouts-internals

Deep layout system implementation knowledge: ILayoutStorage contracts, IndexedDB schema, sync operation computation, mutex-locked LayoutManager, conflict resolution, WriteThroughLayoutCache, NamespacedLayoutStorage, and CurrentLayoutProvider reducers.

Quality

69%

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/layouts-internals/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 lean, technically precise reference for the layout system internals, with concrete code and accurate file paths. Its main weakness is the absence of an operational workflow with validation checkpoints, and all content being inlined rather than progressively disclosed into reference files.

Suggestions

If any multi-step operation (sync, migration, baseline reset) is meant to be performed, add an explicit numbered procedure with a validation/checkpoint step rather than only documenting the architecture.

Consider moving the longer API/type references (e.g. computeLayoutSyncOperations' full SyncOperation union) into a reference file under references/ and linking to it from SKILL.md to improve progressive disclosure.

Expand the abbreviated code comments (SAVE_PANEL_CONFIGS merge logic, SPLIT_PANEL) into complete executable snippets so guidance is copy-paste ready.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence, using real TypeScript signatures and file paths with no padding about what IndexedDB or a mutex is; a few prose sentences (e.g. on the Layout type) could be trimmed slightly.

4 / 5

Actionability

Provides concrete, accurate code (interface and type definitions, class signatures) plus exact source file paths a reviewer can navigate to; minor gaps are the panel-tree pseudocode and the unexpanded SAVE_PANEL_CONFIGS comment.

4 / 5

Workflow Clarity

This is reference/architecture documentation rather than a sequenced operational workflow, so there are no explicit validation checkpoints or feedback loops; the 'Common Issues' list gives mitigations but no ordered procedure.

3 / 5

Progressive Disclosure

Content is well-organized into clear ## and ### sections with helpful warning callouts, but everything is inlined in SKILL.md with no bundle files or one-level-deep references to split the substantial reference material into.

4 / 5

Total

15

/

20

Passed

Description

55%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 clearly scoped to this codebase's layout internals, but it is jargon-heavy and omits any 'Use when...' trigger guidance. Adding a natural-language trigger clause and a few user-facing synonyms would lift completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause naming natural triggers, e.g. 'Use when working on layout storage, sync, or panel-layout reducers in the suite-base package.'

Include user-facing synonyms alongside class names, such as 'layout sync', 'panel layout', or 'IndexedDB layouts', so the description matches what users actually say.

Lead with a concrete action verb (third person) instead of the passive 'Deep ... implementation knowledge' framing.

DimensionReasoningScore

Specificity

Lists several specific concrete subsystems ("ILayoutStorage contracts", "IndexedDB schema", "mutex-locked LayoutManager", "WriteThroughLayoutCache", "CurrentLayoutProvider reducers"), but the framing verb is the passive/generic "Deep ... implementation knowledge" rather than concrete actions.

4 / 5

Completeness

Clearly states the "what" (a comprehensive list of internal subsystems) but has no "Use when..." clause or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Triggers are internal class names and jargon ("ILayoutStorage", "WriteThroughLayoutCache", "mutex-locked LayoutManager") rather than natural phrases a user would say; no synonyms or common variations like "layout sync" or "panel layout" are included.

2 / 5

Distinctiveness Conflict Risk

The highly specific internal component names pin it to a clear niche with distinct triggers and minimal risk of firing for the wrong skill.

5 / 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/layouts-internals/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.