Content
42%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.
The body is a well-conceived router with genuinely concrete routing tables and explicit fail-closed rules, but as a SKILL.md it is severely overweight: dense versioned contract lists and boundary prose that belong in reference files are inlined, and every operational pointer targets vendored files absent from this bundle. The routing core is the strong core; most of the rest adds tokens without adding executable guidance at the router level.
Suggestions
Move the ARS v3.22.x caller-contract and contract-honesty boundary lists into a dedicated reference file (e.g., ars/shared/references/) and keep only a one-line pointer plus the few rules that affect routing decisions.
Compress the Codex Runtime Mapping table to the rows that change routing behavior; the environment-variable transport details (ARS_CROSS_MODEL_TRANSPORT, cache settings, API keys) belong in codex/model-runtime-policy.md.
Trim the duplicated sr-screener boundary statements (they appear in the routing core, the router table, and a dedicated section) into one authoritative statement plus cross-references, and ship the referenced ars/ and codex/ files with the bundle so the one-level-deep pointers resolve.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~575-line body inlines enormous policy sections that should live in separate reference files: the multi-hundred-word Codex Runtime Mapping table rows (e.g., the `ARS_CROSS_MODEL_TRANSPORT=codex` row), the 'ARS v3.22.0 Contract-Honesty Boundaries' list, and the sr-screener boundary paragraphs. It does not explain concepts Claude already knows, so it avoids the score-1 'padded with basics' anchor, but a router this token-heavy loaded on every activation is noticeably verbose with several sections that could be trimmed or moved. | 2 / 5 |
Actionability | There is genuinely concrete guidance — the alias table ('read `ars/commands/ars-plan.md`, route to `ars/academic-paper/WORKFLOW.md` in `plan` mode'), the intent-to-WORKFLOW routing table, and canonical agent filename lists — but the executable detail of each mode is deferred to vendored files not present in this bundle, and large portions (Contract-Honesty Boundaries, Bibliographic Network Routing) are abstract policy rather than executable steps. This lands between 'mostly executable with minor gaps' (4) and 'minimal concrete guidance' (2). | 3 / 5 |
Workflow Clarity | The routing core gives a real sequence (Step 0 escape hatch, then classify as explicit intent / cross-phase materials / ambiguous) with some explicit checkpoints ('If a workflow or required supporting file cannot be loaded, report the loading failure and stop that workflow'), but the many overlapping exception carve-outs ('only when', 'unless', 'never') and stage validation deferred to absent WORKFLOW.md files leave the overall procedure with implicit checkpoints and gaps, fitting the score-3 anchor. | 3 / 5 |
Progressive Disclosure | Section structure and one-level-deep references are present and mostly clearly signaled, but the body inlines large contract and boundary content that clearly belongs in separate files, and none of the referenced bundle files (ars/, codex/) exist in the package as provided, so the pointers cannot be verified. This fits 'some structure but could be better organized; content that should be separate is inline' better than the score-4 'most content appropriately placed'. | 3 / 5 |
Total | 11 / 20 Passed |