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.
90
88%
Does it follow best practices?
Impact
Pending
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 what the skill does (validates environment readiness by checking specific tools) and when to use it (first thing in a new session for optimization work). The enumeration of specific checks provides good specificity and distinctiveness. The main weakness is that trigger terms lean technical rather than matching natural user language.
| 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 Rust toolchain, ci/ scripts, build, benchmarking tools, profilers, memory tools, git state, and SMP CLI) and when ('Run this FIRST when starting a new Claude session to verify the environment is ready for optimization work'). | 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 specific tools enumerated. Unlikely to conflict with other skills due to the narrow, well-defined scope and explicit trigger condition (starting a new session). | 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 strong, well-crafted skill that efficiently communicates a preflight validation workflow. It excels at conciseness and actionability with its script-first approach and comprehensive fix table. The explicit safety constraint (ask before executing fixes) is a good practice. The only minor weakness is that bundle files weren't provided to verify the referenced scripts exist.
| 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 table format is an efficient way to present fix mappings. The skill assumes Claude's competence throughout. | 3 / 3 |
Actionability | Provides a concrete executable command to run the preflight script, a clear behavioral directive (stop on failure, ask before fixing), and a comprehensive table mapping each failure to a specific, copy-paste-ready fix command. Fully actionable. | 3 / 3 |
Workflow Clarity | The workflow is clear and well-sequenced: run script → stop on failure → show fixes → ask user → proceed only after confirmation. The explicit 'STOP on any failure' and 'Do NOT automatically execute fixes' directives serve as validation checkpoints and safety gates for potentially destructive operations. | 3 / 3 |
Progressive Disclosure | The content is well-organized with the script reference and fix table, but the bundle files note says none were provided, so we can't verify the referenced script paths (preflight, install_smp) actually exist. The skill itself is compact enough to not need external references, but the script-based approach implies a bundle that isn't documented here. | 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
01ef8d7
- 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.