Content
31%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 operational core (blocking gates, workflow detection table, gh CLI rules, validation checklist) is genuinely good, but it is buried under a triple-stated owner directive that consumes most of the file, and every detailed workflow lives in referenced files that are not included in the bundle. The skill also carries non-operational content (MRR pressure, Codex competition taunts) and an unresolved contradiction between mandatory delegation and mandatory first-hand verification.
Suggestions
Collapse the triple-stated directive (owner monologue + 12 decoded principles + 12 MUST rules) into one concise rules section, and move any verbatim directive text you must preserve into a single reference file — the current ~250-line preamble restates the same ~40 lines of policy three times.
Include the eight referenced files (validation.md, tdd.md, triage-issue.md, review-pr.md, release.md, marketing.md, agent-teams.md, communication.md) in the bundle, or inline minimal essentials for each workflow — currently every workflow link in the detection table is dead.
Remove non-operational framing (MRR/sales pressure, the Codex-competition taunt) and resolve the contradiction between 'you are FORBIDDEN from reading source code' and the file:line citation requirements by stating explicitly that subagents perform the reads and the EM verifies their citations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Roughly 250 of ~440 lines are an "OWNER OPERATING DIRECTIVE" preamble that states the same rules three times — a verbatim owner monologue, then 12 "Decoded operating principles", then 12 "MUST rules" covering identical ground (e.g. principle #5 and MUST-8 both restate the TDD law verbatim in spirit). This matches the "severely verbose; heavily padded" anchor; the lean operational sections at the end are not enough to lift it to 2, since the padding is duplication rather than trimmable over-explanation. | 1 / 5 |
Actionability | There is real executable guidance (gh commands like "gh pr merge --squash", validation commands like "npx vitest run tests/adapters/" and "npm run typecheck", the clone recovery command "git clone --depth 1 <url> refs/platforms/<name>"), but key workflow steps remain abstract ("Ping-pong — Route Architect reviews ↔ Staff Engineer fixes", "wear your PO hat", "Build agent roster... context-driven") and the concrete per-workflow instructions are delegated to files not present in the bundle. This lands between the pseudocode-level and mostly-executable anchors. | 3 / 5 |
Workflow Clarity | The top-level EM flow (Analyze → Recruit → Dispatch → Ping-pong → Ship) is sequenced and blocking gates with a validation checklist exist, but the actual triage/review/release/marketing workflows have no in-file sequence — they are only a pointer table to triage-issue.md, review-pr.md, release.md, and marketing.md, none of which ship in this bundle. Checkpoints are also undercut by an internal contradiction: the delegation gate forbids the main agent from "reading source code" while MUST-6/claim-verification demand first-hand file:line evidence. | 3 / 5 |
Progressive Disclosure | All eight referenced files (validation.md, tdd.md, triage-issue.md, review-pr.md, release.md, marketing.md, agent-teams.md, communication.md) are missing from the bundle — the bundle contains no reference files at all, so every deep link is dead. Simultaneously, large content that clearly belongs in separate files is inlined: the 250-line directive, the 17-adapter enumeration, and the refs/platforms upstream-repository table. This matches the anchor for inlined content that belongs in separate files plus broken navigation; it is not 3 because the missing files make the otherwise well-signaled reference structure non-functional. | 2 / 5 |
Total | 9 / 20 Passed |