lading-preflight
Environment validation checklist. Run this FIRST when starting a new Claude session to verify the environment is ready for optimization work. Checks Rust toolchain, ci/ scripts, build, benchmarking tools, profilers, memory tools, git state, and SMP CLI.
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly communicates both what the skill does and when to use it. It enumerates specific checks (Rust toolchain, profilers, memory tools, etc.) and provides an explicit trigger condition ('Run this FIRST when starting a new Claude session'). The main weakness is that trigger terms are somewhat technical and may not match how users naturally phrase requests for environment validation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: checks Rust toolchain, ci/ scripts, build, benchmarking tools, profilers, memory tools, git state, and SMP CLI. These are concrete, enumerated items. | 3 / 3 |
Completeness | Clearly answers both what ('Environment validation checklist' that checks specific tools) and when ('Run this FIRST when starting a new Claude session to verify the environment is ready for optimization work'). The 'when' trigger is explicit and actionable. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'Rust toolchain', 'benchmarking tools', 'profilers', 'memory tools', 'git state', and 'SMP CLI', but these are somewhat technical. Missing more natural user-facing terms like 'setup', 'environment check', 'verify setup', 'ready to go'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche: environment validation specifically for Rust optimization work with named tools (SMP CLI, profilers, benchmarking). Unlikely to conflict with other skills due to the specific combination of domain (Rust optimization) and purpose (pre-session validation). | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, lean skill that efficiently communicates a preflight validation workflow. It excels at conciseness and actionability — providing exact commands for every failure scenario without over-explaining. The explicit safety guardrail of asking before executing fixes demonstrates good workflow design. The only minor weakness is the inability to verify referenced script paths since no bundle files were provided.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every token earns its place. No unnecessary explanations of what Rust is, what preflight checks are, or how toolchains work. The content is a lean command, a stop instruction, and a reference table — nothing more. | 3 / 3 |
Actionability | Provides a concrete executable command to run, a clear table mapping every possible failure to a specific fix command or action, and explicit behavioral instructions (stop on failure, ask before fixing). Fully actionable and copy-paste ready. | 3 / 3 |
Workflow Clarity | The workflow is clear and well-sequenced: run the preflight script → stop on failure → show suggested fixes → ask user before proceeding. The explicit 'STOP on any failure' and 'Do NOT automatically execute fixes' instructions serve as validation checkpoints and safety guardrails for a potentially destructive operation (environment modification). | 3 / 3 |
Progressive Disclosure | The content references external scripts (preflight, install_smp) which is good progressive disclosure, but no bundle files were provided to verify these exist. The skill is compact enough that inline content is appropriate, but the reference to scripts without verifiable paths slightly weakens confidence. The table of fixes is appropriately inline rather than in a separate file. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- DataDog/lading
- Commit
e98e305
- 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.