extensions-internals

Deep extension system implementation knowledge: IExtensionLoader interface contracts, IndexedDB storage schema, version-compare cache strategy, contribution point registration, extension sandbox, and the .foxe packaging format.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/extensions-internals/SKILL.md

Quality

Content

63%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 a well-structured, actionable technical reference with concrete interfaces, schemas, and a copy-paste panel example. Its main weaknesses are noticeable internal duplication (interface shown twice, type warnings thrice) and the absence of any progressive file split despite the document's length.

Suggestions

De-duplicate the ExtensionContext interface (shown in both 'Contribution Registration' and 'Extension Sandbox') and consolidate the repeated type-value warnings into one callout.

Move the detailed .foxe format and contribution-registration reference into separate one-level-deep reference files linked from the overview to improve progressive disclosure.

Add explicit validation/checkpoint notes to the install and registration flows so the sequences are prescriptive rather than purely descriptive.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense, relevant technical detail, but repeats itself: the ExtensionContext interface appears twice and the valid type-value warning ('browser/server/filesystem, not remote/indexeddb') is restated three times, so it could be tightened.	3 / 5
Actionability	Provides copy-paste-ready concrete material — the Panel Registration activate() example, package.json required fields, storage schema, and typed interface contracts — with only minor gaps for less-common flows.	4 / 5
Workflow Clarity	Install, Load, and Registration flows are laid out as clearly numbered sequences; no destructive/batch operation cap applies, though the flows describe internal behavior rather than prescriptive Claude-executed steps with validation checkpoints.	4 / 5
Progressive Disclosure	No bundle files exist and the entire reference is inlined in one long SKILL.md; sections are well-headed and navigable, but detail blocks (full .foxe format, contribution registration, catalog provider) that could live in separate one-level references are inlined.	3 / 5
	Total	14 / 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 distinct, listing six concrete internal topics, but lacks any 'Use when...' trigger guidance and leans on technical jargon over natural user phrasings. Completeness is capped at 3 by the missing trigger clause.

Suggestions

Add an explicit 'Use when ...' clause naming natural trigger phrases (e.g., implementing or debugging Foxe extensions, packaging .foxe files, registering contribution points).

Soften jargon with user-facing synonyms so the description surfaces terms a user would actually say.

Lead with verb-led actions (e.g., 'Implements and debugs extension loading...') instead of the 'knowledge:' noun-phrase framing.

Dimension	Reasoning	Score
Specificity	Enumerates six concrete sub-areas ('IExtensionLoader interface contracts, IndexedDB storage schema, version-compare cache strategy, contribution point registration, extension sandbox, and the .foxe packaging format') with comprehensive coverage, though framed as knowledge topics rather than verb-led actions.	4 / 5
Completeness	Provides a clear 'what' (deep extension-system internals) but has no 'Use when...' or equivalent trigger clause, so per guidelines completeness caps at 3.	3 / 5
Trigger Term Quality	Contains relevant terms ('extension', '.foxe packaging format') but is dominated by internal jargon (IExtensionLoader, contribution point registration) that users would rarely say naturally, missing common synonyms.	3 / 5
Distinctiveness Conflict Risk	The highly specific internal terms (IExtensionLoader, .foxe, IndexedDB storage schema) carve out a clear niche with low overlap risk, though 'extension system' alone is moderately broad.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

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/extensions-internals/SKILL.md
Commit: 0900ce3

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.