CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

porting-tools-to-fluent

Guide for porting Babylon.js tools from legacy shared-ui-components to Fluent UI using MakeModularTool. Use when: port to fluent, migrate to fluent, fluent migration, porting tool UI.

Quality

83%

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

78%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 highly actionable, well-sequenced migration guide rich in executable code and real-world gotchas, with explicit validation checkpoints. Its weaknesses are dangling references to nonexistent bundle files, inlined reference-grade material that inflates length, and an internal contradiction about inspector dependencies between the summary and Section 1.

Suggestions

Resolve the dangling references: either add fluent.instructions.md and the design-guidelines file to the bundle (e.g. references/) or inline the essential icon/styling rules they were meant to carry.

Fix the summary's contradiction with Section 1 — step 1 ("add Fluent + inspector") and step 3 ("add inspector path mapping") should drop the inspector references since Section 1 explicitly says none is needed.

Move stable lookup tables (the FontAwesome-to-Fluent icon table, the className-forwarding matrix) into a references/ file linked from the body to cut SKILL.md length while keeping the workflow steps and gotchas inline.

DimensionReasoningScore

Conciseness

The body is dense with repo-specific knowledge (import paths, className-forwarding gotchas, Griffel deduplication behavior) and assumes competence, but the Summary section restates earlier sections and the 20-row icon table plus Section 11 could be tightened or offloaded, matching anchor 4 (minor instances that could be trimmed).

4 / 5

Actionability

Nearly everything is copy-paste ready: a full MakeModularTool bootstrap call, ServiceDefinition factory pattern, makeStyles snippets, exact import paths, a legacy-to-Fluent component mapping table, and a dropdown options pattern; the few placeholders ("/* your service definitions */") are inherent tool-specific slots, matching anchor 5.

5 / 5

Workflow Clarity

A clear 10-step porting order, a phased execution plan that keeps the build green, and a verification checklist (clean build, no legacy imports, both themes) are present, but the summary contradicts the body — step 1 says "add Fluent + inspector" and step 3 "add inspector path mapping" while Section 1 states no inspector dependency or mapping is needed — a coherence gap that keeps it below anchor 5.

4 / 5

Progressive Disclosure

Sections are well organized, but the two linked references (fluent.instructions.md and ../../design-guidelines.md) do not exist in the bundle, and substantial reference-grade material (the icon mapping table, known gotchas, large-editor patterns) is inlined in a ~580-line body, matching anchor 3 (structure present but content that should be separate is inline and references are not backed by real files).

3 / 5

Total

16

/

20

Passed

Description

82%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.

A strong description: explicit what and when, highly distinct niche, and natural trigger phrases. The main gap is that it names only the single action of porting rather than enumerating the concrete capabilities (component mapping, SCSS-to-makeStyles migration, icon replacement, service architecture) the skill actually provides.

Suggestions

Enumerate 2-3 concrete actions in the description, e.g. "Ports Babylon.js tools to Fluent UI: maps legacy components to Fluent primitives, converts SCSS to makeStyles, replaces FontAwesome icons, and rebuilds entry points on MakeModularTool."

Add a few more natural trigger variations such as "Fluent UI migration", "modernize tool UI", or "shared-ui-components" to broaden keyword coverage.

Consider mentioning the reference implementation (viewer-configurator) or tool names (NME, Playground) only if they are phrases users would naturally say when invoking the skill.

DimensionReasoningScore

Specificity

"porting Babylon.js tools from legacy shared-ui-components to Fluent UI using MakeModularTool" names the domain and mechanism precisely but describes only one action (porting); it does not list several specific actions as anchor 4 requires, yet is far more concrete than the generic anchor 2.

3 / 5

Completeness

It explicitly answers both what ("Guide for porting Babylon.js tools ... using MakeModularTool") and when ("Use when: port to fluent, migrate to fluent, fluent migration, porting tool UI") with concrete trigger phrases, matching the anchor 5 pattern.

5 / 5

Trigger Term Quality

"Use when: port to fluent, migrate to fluent, fluent migration, porting tool UI" gives good natural phrasing with variations, but misses synonyms a user would plausibly say such as "Fluent UI", "modernize the UI", or the legacy library name.

4 / 5

Distinctiveness Conflict Risk

"Babylon.js tools", "Fluent UI", and "MakeModularTool" carve out a clear niche with distinct triggers; there is virtually no overlap risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (584 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 2 missing, 1 suspicious

Warning

Total

14

/

16

Passed

Repository

BabylonJS/Babylon.js

Path

.github/skills/porting-tools-to-fluent/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.