Content
72%Weight 40%Scale 1-3Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is well-organized and token-efficient with good progressive disclosure to a real reference file, but its deeper investigative steps ('reconstruct the smallest runtime graph', 'reproduce the smallest asset-to-runtime boundary') are abstract and lack executable examples or explicit validation feedback loops.
Suggestions
Add one concrete worked example or runnable snippet (e.g., a sample source-map→original-symbol lookup or a chunk-loader trace) so the 'Reconstruct' and 'Reproduce' steps have executable specifics rather than abstractions.
Promote step 5 into an explicit validation checkpoint with a re-check loop — e.g., 'Verify: confirm the recovered symbol is actually invoked by the currently served bundle; if not, return to step 2' — instead of leaving verification implicit.
For each Workflow phase, name the specific artifact or tool action that produces the output (e.g., 'parse the source map with source-map-explorer to map chunk ids to original modules') to lift actionability from described to instructed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~45-line body is lean and efficient, never explaining concepts Claude already knows (no 'what a source map is'), and every line carries instruction; it does not reach the verbose score-2 anchor of unnecessary explanation. | 3 / 3 |
Actionability | It names concrete artifacts to record ('entry HTML, script tags, preload hints, manifest files, asset map, chunk registry, and source map URLs') but several core steps stay abstract ('Reconstruct the smallest runtime graph that explains which asset executes now', 'Reproduce the smallest asset-to-runtime boundary') with no executable examples or commands. It is more specific than the score-1 'describe rather than instruct' anchor but lacks the copy-paste-ready specificity of score 3. | 2 / 3 |
Workflow Clarity | A clear numbered sequence exists (Quick Start steps 1–5 plus a 3-phase Workflow), but validation checkpoints are implicit rather than explicit — step 5's 'proves the decisive behavior' is a proof step yet there is no structured validate-then-retry feedback loop. This fits 'sequence present but checkpoints missing or implicit' better than the explicit-checkpoint score-3 anchor. | 2 / 3 |
Progressive Disclosure | A concise overview body points via a clearly signaled one-level-deep reference ('Load `references/bundle-sourcemap-recovery.md` for the artifact checklist, deobfuscation checklist, and evidence packaging') to a real, non-nested file (verified present), with content appropriately split between overview and reference. | 3 / 3 |
Total | 10 / 12 Passed |