CtrlK
BlogDocsLog inGet started
Tessl Logo

directxtk-tutorial

Walk through the DirectX Tool Kit for DirectX 11 Getting Started tutorial step by step. Use this skill when asked to follow the tutorial, set up a new DirectX 11 project, or learn how to use DirectX Tool Kit from scratch.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/directxtk-tutorial/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, well-structured overview that points cleanly to per-step references, but its value is undermined because the referenced `reference/` files are absent and the body itself carries no concrete executable guidance or validation checkpoints. The asset listing matches the real `assets/` folder, but the step references are broken.

Suggestions

Create the missing `reference/` directory with `step0.md`–`step7.md` and `tutorial-steps.md` (or correct the link paths) so the signaled references actually resolve.

Add at least one concrete, executable snippet or command to SKILL.md (e.g., the project-setup command or a minimal Direct3D code sample) so the body is actionable without relying solely on the missing reference files.

Insert a per-step validation checkpoint (e.g., 'confirm the project builds before proceeding to the next step') to give the workflow an explicit feedback loop.

DimensionReasoningScore

Conciseness

The body is lean (~30 lines), assumes Claude's competence, avoids explaining what DirectX or the toolkit is, and lets every token earn its place as a navigational overview.

3 / 3

Actionability

It gives a clear interaction directive ('ask the user if they would like to see the Technical Notes section ... or skip it') and sequencing guidance, but all concrete technical steps are delegated to reference files that do not exist, leaving the body's actionable substance incomplete.

2 / 3

Workflow Clarity

Steps are clearly sequenced in an ordered table with a per-step user checkpoint, but there are no validation/verification checkpoints, and the actual step content lives in missing reference files so the workflow's concrete substance cannot be confirmed.

2 / 3

Progressive Disclosure

The body is well-organized with a clean step table and clearly signaled one-level-deep references, but the referenced `reference/step0.md`–`step7.md` and `reference/tutorial-steps.md` files do not exist (only `assets/` is present), so the navigation does not resolve in practice.

2 / 3

Total

9

/

12

Passed

Description

75%Weight 40%Scale 1-3

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 with an explicit 'Use when' trigger clause and a clear, distinctive niche. Its main weakness is that the listed actions are facets of a single tutorial-following capability rather than several distinct concrete operations, and trigger-term coverage could include more natural variations.

DimensionReasoningScore

Specificity

It names the domain ('DirectX Tool Kit for DirectX 11') and several actions ('walk through the tutorial step by step', 'set up a new DirectX 11 project', 'learn how to use DirectX Tool Kit from scratch'), but these are variations of one tutorial-following capability rather than the multiple distinct concrete actions the top anchor calls for.

2 / 3

Completeness

It states what the skill does ('Walk through the ... tutorial step by step') and gives an explicit 'Use this skill when ...' clause naming three trigger situations, satisfying both the what and the when.

3 / 3

Trigger Term Quality

Triggers like 'follow the tutorial', 'set up a new DirectX 11 project', and 'learn how to use DirectX Tool Kit from scratch' are natural, but coverage lacks common variations a user might say (e.g., 'DirectXTK', 'sprites', 'shaders', 'DirectX 11 graphics').

2 / 3

Distinctiveness Conflict Risk

The niche is highly specific (DirectX Tool Kit for DirectX 11 Getting Started tutorial) with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 9 missing

Warning

Total

15

/

16

Passed

Repository
microsoft/DirectXTK
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.