Content
75%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 dense, well-indexed orchestration core: it routes commands to workflows, enumerates every script's intent, and enforces artifact-based validation at each stage, with one-level-deep references that are clearly signaled and verifiable. Its weaknesses are the inlined deployment-specific Project Instructions block, heavy reliance on '--help' and external workflow/schemas files for actual usage detail — several of which are missing from the provided bundle — and prose so compressed that following the rules requires real effort.
Suggestions
Move the 'Project Instructions' block (owner timezone, consumer refresh review, Cargo round cleanup) into a dedicated reference file and link to it, so per-deployment details are not loaded on every skill read.
Ensure every path referenced from the body — workflows/*.md, schemas/*.md, README.md — ships in the skill bundle, or note in the body where sibling-skill paths (../reviewer, ../dev) resolve from, since navigation currently dead-ends for missing targets.
Include one concrete end-to-end example invocation (e.g., a filled 'start' or 'review-pr' call with real arguments) so the common case is executable from the body alone rather than deferring all argument detail to '--help' and workflow files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence throughout — it never explains concepts Claude already knows, and every line carries rule content. Minor trim opportunities exist: the ~35-line inlined 'Project Instructions' block (owner timezone, consumer refresh review, Cargo cleanup, kendex-internal rules like D027/KEN-3338) is deployment/org-specific content read on every load that could live in a reference file, and the version pin 'Requires kendex 1.20.0 or newer' is time-sensitive detail not placed in a deprecated/old-patterns section. This fits 'Efficient; minor instances... that could be trimmed' rather than the fully-earned level-5 'every token earns its place'. | 4 / 5 |
Actionability | Guidance is concretely executable: a 16-command routing table, a ~40-row scripts table with intents, exact script paths ('.agents/skills/orch/scripts/<script>'), and literal commands such as 'git -C [WT_PATH] rev-parse --verify HEAD' and the 'git -C [WT_PATH] diff --no-renames --name-only [BOUND_HEAD] HEAD -- <path>' rebase check. The gap from level 5 is that many invocations defer their actual arguments to '--help' and to workflow files not present in this bundle, so the body alone is not fully copy-paste ready for the common cases. | 4 / 5 |
Workflow Clarity | The cycle is explicitly sequenced ('Get the issue → dev implements → publication, review and fixes in the order from pr-order --help → required CI and review gate → merge') with strong validation checkpoints and feedback loops: artifact-based acceptance ('A round closes on a validated on-disk artifact plus git/tracker state, never on a return message'), bounded fix rounds with re-review narrowing and caps, review-artifact-check as the sole reviewer completion condition, and post-merge box-ticking only on proving artifacts. It stays at level 4 because the detailed per-step sequences are delegated to workflow files absent from this bundle, and the extreme prose density makes the sequencing rules themselves effortful to follow. | 4 / 5 |
Progressive Disclosure | Structure is genuinely good: an overview body acting as an index, command and script routing tables, and one-level-deep references with markdown links and precise section anchors (references/skill-rules.md, references/gates.md, references/oversee-events.md etc., all present in the bundle listing and confirmed to use clear in-file navigation). The organization gaps that keep it below 5: a large portion of referenced targets (workflows/*.md, schemas/*.md, README.md, and cross-skill ../reviewer, ../dev, ../communication paths) do not exist in the provided bundle, and the inlined 'Project Instructions' block is content that would be more appropriately split into a separate reference file. | 4 / 5 |
Total | 16 / 20 Passed |