Content
68%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A lean, well-organized body with a solid executable example and useful do/don't guidance. Main gaps: the example has a compile-blocking missing import, the instructions read as principles rather than a sequenced workflow with an integrated validation step, and only one of several promised patterns is shown.
Suggestions
Fix the Example 1 code so it compiles as written: add `import * as cdk from "aws-cdk-lib";` (or use `RemovalPolicy.RETAIN` via an existing import) so `cdk.RemovalPolicy.RETAIN` resolves.
Turn the Instructions into a sequenced workflow with an integrated validation checkpoint, e.g. make 'Run `cdk diff` and review changes before deploying' an explicit numbered step with guidance on what to do when unexpected destructive changes appear (e.g. adjust RemovalPolicy).
Either add compact examples for the other promised patterns (ECS service, static site) or move pattern details into a references/ file and point to it from SKILL.md to keep the main file lean.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is tight and assumes Claude's competence — no padding explaining what CDK is, and sections are scannable. A few generic bullets ('Enable monitoring by default', 'Apply the principle of least privilege') could be tightened into specifics, keeping it below anchor 5. | 4 / 5 |
Actionability | Provides one near-complete executable TypeScript example and a concrete command ('Use `cdk diff` before every deploy'), but the example won't compile as written (`cdk.RemovalPolicy.RETAIN` uses an unimported `cdk` namespace) and patterns promised in the use-when section (ECS, static sites) have no example, matching anchor 4 rather than 5. | 4 / 5 |
Workflow Clarity | The six numbered instructions are design principles rather than a sequenced process, and the one validation checkpoint (`cdk diff` before deploy) is tucked into Best Practices instead of being an explicit step with error-recovery guidance, matching anchor 3 rather than 4. | 3 / 5 |
Progressive Disclosure | No bundle files exist (references/, scripts/, assets/ are absent), and the single-file body is well-sectioned with clear headers at ~72 lines — good structure. It sits just above the under-50-line simple-skill threshold and the promised pattern catalog (ECS, static sites) would soon belong in separate reference files, matching anchor 4 rather than 5. | 4 / 5 |
Total | 15 / 20 Passed |