CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

build-openshell-mxc-windows

Maintain and validate OpenShell's native Windows MSVC and MXC runtime lane for x64 and ARM64. Use when working on Windows compilation, `windows:*` mise tasks, the MXC supervisor/sandbox pairing, unsupported Windows compute-driver contracts, or Windows build reports. This skill does not implement Docker, Kubernetes, Podman, VM, MSI, or service support on Windows.

Quality

79%

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 ./.agents/skills/build-openshell-mxc-windows/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally actionable and well-sequenced maintenance skill: every workflow step is an exact, copy-pasteable command with explicit error checks and a rigorous reporting checklist. Its weaknesses are token efficiency — hundreds of lines of repetitive policy prose that a contributor-facing reference file could carry — and progressive disclosure, since a 35KB body with alluded-to companion material ships no local reference bundle at all.

Suggestions

Move the stable constraint catalog (Hard Rules, Unsupported Driver Contract, and the many 'Keep/Preserve/Do not' policy paragraphs) into a references/ file (e.g. references/constraints.md), leaving SKILL.md as a lean overview that links to it — this addresses both conciseness and progressive_disclosure.

Trim redundant narration in the GitHub Actions cache-seeding and cache-scoping paragraphs to the operative facts (label-triggered runs, branch-scoped caches, re-run instructions) — the current multi-paragraph explanation repeats the same constraints.

Create the companion reference files the body alludes to (MXC README command contract, WINDOWS-INTEGRATION.md checkpoint) as local references/ entries, or drop the allusions, so the skill is self-consistent with its bundle.

DimensionReasoningScore

Conciseness

The body runs ~580 lines / 35KB of dense prose with repetitive policy statements ("Do not reintroduce", "Keep ... in", "Preserve ..." appear dozens of times), multi-paragraph GitHub Actions cache-scoping narration, and long constraint lists that could each be compressed to a fraction of their length. It is not explaining concepts Claude already knows (nearly everything is repo-specific), so it is above the 1 anchor, but the sheer volume of padded and redundant directive prose clearly marks it as 'noticeably verbose' rather than merely 'could be tightened' (3-4).

2 / 5

Actionability

The guidance is fully executable: exact commands ("mise run --skip-tools windows:check:x64", "git fetch upstream windows", "vswhere -latest -products * -requires ..."), a complete copy-paste PowerShell validation script with per-step error throws, env-var tables with defaults, expected-behavior tables per task, and named log files. This matches the 5 anchor: specific commands cover the common cases end to end.

5 / 5

Workflow Clarity

The workflow is explicitly sequenced with validation checkpoints: run the smallest slice first, detect host architecture before choosing the lane, check $LASTEXITCODE after every command and throw on failure, an ordered 7-step CI contract, a numbered failure-triage pattern (identify error source, prefer existing patterns, re-run relevant tasks), and a final report checklist. This matches the 5 anchor's clear sequence with explicit validation steps and feedback loops for error recovery.

5 / 5

Progressive Disclosure

Section headers, tables, and per-topic organization are good, but the skill is a ~580-line monolith: no references/, scripts/, or assets/ bundle exists even though the body twice alludes to companion material ("This skill and companion reference material", "See the MXC driver README") — those pointers resolve only to external GitHub URLs, not navigable local files. Deep contract detail (unsupported-driver contracts, E2E scenario descriptions, remote test accounting) is inlined where the 4-5 anchors expect it split into clearly signaled one-level-deep reference files; it is above the 2 anchor because structure and navigation within the file are genuinely good.

3 / 5

Total

15

/

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, well-scoped description that explicitly answers both what and when with concrete trigger phrases and a clear out-of-scope boundary. Its main weakness is that the capability verbs are generic — 'maintain and validate' — without enumerating the concrete actions (check, build, test, report) that the skill actually performs.

DimensionReasoningScore

Specificity

The description names the domain precisely ("native Windows MSVC and MXC runtime lane for x64 and ARM64") and gives two actions ("Maintain and validate"), but the actions themselves are generic — it never lists concrete operations like compiling, running tests, or building release binaries. It matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'; a 4 would require several specific actions such as 'runs MSVC checks, builds x64/ARM64 release binaries, reports test counts'.

3 / 5

Completeness

Both questions are explicitly answered: what ("Maintain and validate OpenShell's native Windows MSVC and MXC runtime lane for x64 and ARM64") and when ("Use when working on Windows compilation, windows:* mise tasks, ... or Windows build reports"), plus an explicit exclusion clause. It clearly matches the 5 anchor with concrete trigger phrases; a 4 would mean the 'when' was present but less explicit or enumerative.

5 / 5

Trigger Term Quality

"Windows compilation", "windows:* mise tasks", "MXC supervisor/sandbox pairing", "compute-driver contracts", and "Windows build reports" are terms a contributor to this repo would naturally say, giving good keyword coverage. It falls short of 5 because common variations like "Windows CI", "MSVC build", or "Visual Studio" are absent, while the trigger list leans on project-specific jargon like "MXC supervisor/sandbox pairing".

4 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — a named repository (OpenShell), a named runtime (MXC), and platform-specific triggers (Windows MSVC, x64/ARM64) make accidental triggering by another skill extremely unlikely. The explicit "does not implement Docker, Kubernetes, Podman, VM, MSI, or service support" boundary further reduces overlap risk; no neighboring anchor fits better.

5 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

13

/

16

Passed

Repository

NVIDIA/OpenShell

Path

.agents/skills/build-openshell-mxc-windows/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.