Content
87%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 tight, highly actionable routing document packed with non-obvious operational specifics and no padding. Its one real gap is the absence of validation and error-recovery steps for what is a batch operation across up to 200 routes.
Suggestions
Add a post-run verification step, e.g. check that route_count > 0 and that <output_dir>/ci-result.json exists before summarizing aggregate scores.
Add error-recovery guidance for partial audits — e.g. if the 600s subprocess guard trips, rerun with a lower --max-routes or raise --timeout.
Present the workflow as an explicit ordered sequence (install → run → verify output) instead of spreading it across Prerequisites, Routing, and Output handling sections.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes competence — it never explains what Lighthouse or CWV is, and every section carries non-obvious specifics (e.g. "the only CLI-documented way to set scanner.maxRoutes; unlighthouse-ci has no --max-routes flag"). The only trim candidate is the doubled "untrusted" phrasing in the Security section, which is too minor to drop below anchor 5. | 5 / 5 |
Actionability | The routing table provides three copy-paste-ready command variants with concrete flags (--device desktop, --max-routes 50 --output-dir ./reports), plus the install command and documented defaults (--page-timeout 60s, --timeout 600s). This fully matches the anchor for executable guidance covering the common cases. | 5 / 5 |
Workflow Clarity | The sequence (Prerequisites → Routing → Output handling) is coherent and the wrapper's url_safety pre-flight is mentioned, but this is a batch operation (up to 200 routes) with no post-run validation or error-recovery loop — no step to verify route_count or handle a missing/partial ci-result.json. Per the rubric's batch-operation cap, which overrides the simple-skill exception, workflow clarity cannot exceed 3. | 3 / 5 |
Progressive Disclosure | This is a compact single-file skill with well-organized sections and no bundle files; nothing in it belongs in a separate reference file and there are no nested references to get lost in. Per the rubric's guideline for short skills with no need for external references, well-organized sections alone warrant anchor 5. | 5 / 5 |
Total | 18 / 20 Passed |