CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

release

Guide for performing the DirectX Tool Kit for DirectX 11 release process. Use this skill when asked to help with releasing a new version, publishing packages, or updating ports.

Quality

82%

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

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 content is a well-structured, actionable phased release runbook with concrete scripts and a properly referenced bundle asset. Its main weakness is the absence of explicit validation feedback loops for a high-stakes publishing workflow, which caps workflow clarity.

Suggestions

Add explicit validate->fix->retry feedback loops for the risky publishing steps (e.g., after step 14 NuGet validation: 'If the build fails, fix the package and re-run validation before promoting'), and frame step 4 as a hard gate ('Verify all GitHub Actions and ADO pipelines are green before proceeding to Phase 2').

Provide copy-paste-ready commands for the procedural steps — e.g., the exact git push invocation with --tags for steps 6 and 7, and the local NuGet source setup commands for step 14.

Trim the redundancy between the inline step references and the Key Scripts table — either link the table entries to the steps or drop the inline script descriptions in favor of the table.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (git, PowerShell, ADO, NuGet) with no concept padding, but the Key Scripts table duplicates scripts already named inline and "Be sure to include --tags" repeats, so it is not perfectly tight.

4 / 5

Actionability

Most steps reference concrete executable scripts and commands (e.g. build\preparerelease.ps1, .\vcpkg x-add-version directxtk, promotenuget.ps1 -Version <version>), though a few steps (NuGet validation in step 14, MSCodeHub PR in steps 8/11) are described procedurally without copy-paste-ready commands.

4 / 5

Workflow Clarity

The 8-phase, 24-step sequence is clearly numbered and phased with some checkpoints (CI gate in step 4, archive comparison in step 12, NuGet validation in step 14), but this destructive/batch publishing workflow lacks explicit validate->fix->retry feedback loops, so the feedback-loops cap applies.

3 / 5

Progressive Disclosure

Content is well-organized into Prerequisites, phased Steps, and a Key Scripts summary, and the one bundle asset (assets/vcpkgdxtk.cmd) is real and clearly referenced one level deep in step 19; minor redundancy from the Key Scripts table keeps it just short of excellent.

4 / 5

Total

15

/

20

Passed

Description

87%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 clearly states what the skill does and when to use it, with concrete triggers and a well-defined niche. It is strong overall, with only minor room for improvement in action specificity and synonym coverage.

DimensionReasoningScore

Specificity

Names the domain and lists three concrete actions ("releasing a new version, publishing packages, or updating ports"), but the lead phrase "Guide for performing the... release process" is slightly abstract and not all sub-tasks (tagging, signing, winget) are named, so it stops short of comprehensive.

4 / 5

Completeness

Explicitly answers both what ("Guide for performing the DirectX Tool Kit for DirectX 11 release process") and when ("Use this skill when asked to help with releasing a new version, publishing packages, or updating ports") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ("releasing a new version", "publishing packages", "updating ports"), but lacks synonyms and explicit terms like "NuGet" or "vcpkg", keeping it below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (DirectXTK for DirectX 11 release) with distinct triggers, making conflict with other skills minimal.

5 / 5

Total

18

/

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

microsoft/DirectXTK

Path

.github/skills/release/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.