CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

windows-ml

Windows ML (WinML, Microsoft.Windows.AI.MachineLearning) guidance in three evidence tiers - Microsoft Learn canon, ONNX Runtime/GenAI source and NuGet facts, and dated Trackdub observations. Use whenever work touches Windows ML or WinML, ExecutionProviderCatalog, EnsureReadyAsync/TryRegister, GetEpDevices, execution provider selection or registration, onnxruntime.dll conflicts, Microsoft.ML.OnnxRuntimeGenAI.WinML, DirectML availability, EP-context compilation, or a Windows ML / ONNX Runtime upgrade, even when the user only says "DirectML is broken" or "why doesn't the NPU show up".

Quality

80%

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 ./.claude/skills/windows-ml/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 maximally lean discovery stub that delegates all substance to an external SKILL.md via a repo-relative path escaping the skill bundle. Brevity is excellent, but actionability, workflow clarity, and progressive disclosure all suffer because the actual guidance is entirely absent from this file and the referenced target is not part of the bundle and does not resolve from this location.

Suggestions

Inline the essential evidence-tier rules (or at least a quick-start summary of EP selection, registration, and conflict-resolution steps) in this body so the skill remains actionable when the external path does not resolve.

Make the reference resolve within the skill's own bundle - e.g., bundle the canonical SKILL.md as a references/ file next to this stub - instead of the fragile repo-relative '../../../.agents/skills/windows-ml/' path.

Add a fallback instruction for when the linked file is missing (e.g., where the canonical copy lives or what to do instead) so the single workflow step cannot dead-end.

DimensionReasoningScore

Conciseness

Three sentences with zero padding: 'The skill lives in ... Read that SKILL.md now and follow its evidence-tier rules. This file only exists so Claude Code can discover the skill.' No over-explanation of known concepts; every token earns its place.

5 / 5

Actionability

The only guidance is the directive 'Read that SKILL.md now and follow its evidence-tier rules' - concrete as a link, but the specific steps to execute (evidence-tier rules, EP selection, conflict resolution) are entirely absent from this body, delegated to '../../../.agents/skills/windows-ml/SKILL.md', a path outside the skill bundle that does not resolve from this file's location. Not 1 because the link and directive are specific and unambiguous; not 3 because no domain guidance exists in the body at all.

2 / 5

Workflow Clarity

The single delegation step ('Read that SKILL.md now and follow its evidence-tier rules') is clear and unambiguous, but this is not a simple skill - the description promises multi-step evidence-tier evaluation, EP registration, and upgrade workflows, none of which are sequenced or checkpointed in this file; all sequencing is implicit in an external file. The simple-skill exception does not apply, and validation checkpoints for the real work are missing.

3 / 5

Progressive Disclosure

The body is a single, clearly-signaled, one-level-deep reference, which is structurally sound. However, it points outside the skill's own bundle ('../../../.agents/skills/windows-ml/SKILL.md') with no references/, scripts/, or assets/ directories alongside, and the target does not resolve from this file's location - navigation to the actual content cannot be verified. Not 2 (nothing is inlined and the reference is prominent, not buried); not 4 (the gap is more than minor - all skill content lives outside the bundle).

3 / 5

Total

13

/

20

Passed

Description

95%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: an explicit 'what' paired with an unusually thorough 'Use whenever...' trigger clause covering API names, package identifiers, and colloquial user phrasings, in a niche with minimal conflict risk. The only weakness is the verb-less 'guidance in three evidence tiers' framing that enumerates topics rather than actions.

DimensionReasoningScore

Specificity

Enumerates many concrete topics - 'execution provider selection or registration', 'onnxruntime.dll conflicts', 'DirectML availability', 'EP-context compilation', 'a Windows ML / ONNX Runtime upgrade' - but frames them under the verb-less 'guidance in three evidence tiers' rather than stating actions. Above the 3 anchor (far more than 1-2 items, comprehensive topic coverage); below 5 because capabilities are listed as topics, not explicit actions.

4 / 5

Completeness

Explicitly answers both: what - 'Windows ML (WinML, Microsoft.Windows.AI.MachineLearning) guidance in three evidence tiers - Microsoft Learn canon, ONNX Runtime/GenAI source and NuGet facts, and dated Trackdub observations' - and when - 'Use whenever work touches Windows ML or WinML, ... or a Windows ML / ONNX Runtime upgrade', with concrete trigger phrases throughout.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage: synonyms ('Windows ML', 'WinML'), API names ('ExecutionProviderCatalog', 'EnsureReadyAsync/TryRegister', 'GetEpDevices'), file and package identifiers ('onnxruntime.dll', 'Microsoft.ML.OnnxRuntimeGenAI.WinML'), and colloquial user phrasings explicitly captured - 'even when the user only says "DirectML is broken" or "why doesn't the NPU show up"'.

5 / 5

Distinctiveness Conflict Risk

A clear niche (Windows ML / WinML on Windows with ONNX Runtime) with distinct API-level triggers like 'EnsureReadyAsync/TryRegister', 'GetEpDevices', and 'Microsoft.ML.OnnxRuntimeGenAI.WinML'; minimal overlap with any other skill domain.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

MesilimLLC/Trackdub

Path

.claude/skills/windows-ml/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.