Content
78%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 strong, highly actionable body with excellent progressive disclosure and copy-paste-ready commands. The main cost is redundancy: the operating-prompt rules are restated across the Operating Prompt, Hard Rules, and Anti-Patterns sections, which could be merged to tighten token use.
Suggestions
Merge the 'Hard Rules' and 'Anti-Patterns To Reject' sections into the 'Operating Prompt' section — items 3, 4, 5, and 7 of Hard Rules and several anti-patterns restate rules already listed verbatim above, costing tokens without adding new behavior.
Cut the two-paragraph positioning text ('It is the Andreessen-lens counterpart to a founder-operating-system plugin...') — it describes what the skill is not rather than instructing Claude what to do.
Add one line of guidance for incomplete runs, e.g., what to do when the user cannot supply script inputs (score inputs as 'unknown' and downgrade the verdict confidence) — this closes the workflow's main validation gap.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient — the routing table, forcing questions, and script commands all earn their tokens — but the same rules are stated three times: the Operating Prompt section ('Lead with the strongest counterargument', 'No disclaimers'), Hard Rules items 3–5 and 7 ('Counterargument first', 'Confidence levels mandatory', 'No sycophancy, no disclaimers'), and the Anti-Patterns list ('Validating the premise...', 'Citing an Andreessen quote without a confidence level...'). The plugin-comparison paragraph ('It is the Andreessen-lens counterpart to a founder-operating-system plugin') is decorative. This matches the level-3 anchor 'mostly efficient but includes some unnecessary explanation or could be tightened'; it is not level 2 because there is no explanation of concepts Claude already knows and no padding filler. | 3 / 5 |
Actionability | Fully executable guidance throughout: a routing table mapping user intents to scripts, six forcing questions each with a recommended answer, exact copy-paste commands with realistic arguments ('python scripts/market_first_evaluator.py --size 8 --growth 7 --timing 9 --pull 8 --team 6 --product 5'), a fixed verdict vocabulary (BUILD-POUR-FUEL / MARKET-FIRST-DERISK / KILL-OR-REPICK-MARKET), and a worked delivery format. This matches the level-5 anchor: copy-paste ready commands covering the common cases. | 5 / 5 |
Workflow Clarity | A clear four-step sequence — detect and route, forcing-question interrogation one at a time ('Do not batch them — make the user commit to each'), deterministic tool scoring ('the verdict isn't vibes'), then verdict delivery with confidence levels. This is not a destructive/batch skill so the validation cap does not apply, and the script-score gate functions as a checkpoint. It falls short of level 5 only because there is no explicit handling for edge states — e.g., what to do when inputs to a scoring script are unknown, or when the user refuses to answer a forcing question — leaving minor validation gaps per the level-4 anchor. | 4 / 5 |
Progressive Disclosure | The body is a clean overview with well-signaled, one-level-deep references: a References section listing each of the 4 reference files with a one-line content description, an Assets section with 5 named templates/examples, and a Tooling table for the 3 scripts. Core workflow content (routing, forcing questions, commands) stays inline while deep material (canon sources, worksheets, worked examples) is pushed out, matching the level-5 anchor. Note: no bundle files were present in the reviewed directory to verify the referenced paths exist, so this score reflects the body's structure as written. | 5 / 5 |
Total | 17 / 20 Passed |