Content
73%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 an unusually disciplined, actionable workflow: concrete tsci commands, exact JSX props, explicit validation gates, and fix-and-rerun feedback loops for every risky stage. Its one serious defect is that the progressive-disclosure architecture is broken in practice — CLI.md, SYNTAX.md, WORKFLOW.md, CHECKLIST.md, templates/, and all of the elements/*.md links point to files that do not exist in the bundle, and the bulky element index is inlined instead.
Suggestions
Ship the referenced bundle files (CLI.md, SYNTAX.md, WORKFLOW.md, CHECKLIST.md, templates/, and the elements/*.md directory) or remove the dangling references — currently only scripts/ exists, so every navigation pointer except scripts/ is a dead end.
Move the 80-line Builtin Elements index out of SKILL.md into a single reference file (e.g. ELEMENTS.md) to reduce token cost and keep SKILL.md a lean overview.
Close the actionability gaps by adding a complete minimal default-exported circuit example and the explicit CLI install command, and deduplicate the netlist-check-first guidance repeated between workflow steps 5 and 6.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense, imperative, and teaches only proprietary knowledge (CLI flags, check semantics, schematic-layout rules) with no padding about concepts Claude already knows. Not 5: the check-ordering guidance "Run `tsci check netlist` before..." is duplicated between steps 5 and 6, and the ~80-line Builtin Elements index is inlined content that could be trimmed or moved; not 3 since nearly every token carries tscircuit-specific information Claude cannot infer. | 4 / 5 |
Actionability | Concrete, copy-paste-ready commands and props throughout: "tsci check shorts [file]", "tsci build --pcb-png [file]", "supplierPartNumbers={{jlcpcb:[\"C165948\"]}}", "<connector standard=\"usb_c\" />", "pcbX, pcbY, pcbRotation, layer". Not 5: there is no complete minimal default-exported circuit example and "Install CLI" is given without the actual install command; not 3 since guidance is fully executable, not pseudocode or high-level hints. | 4 / 5 |
Workflow Clarity | The six-step "Default workflow" is clearly sequenced with explicit validation gates and feedback loops: "Do not finalize unless both `tsci check schematic-placement` and `tsci check placement` pass with no actionable placement violations; if violations exist, fix layout and rerun until clean", and short-failure recovery ("Inspect `checks/check-shorts/bitmap.png`... fix the implicated copper, then rerun the check"). Not 4: validation checkpoints and error-recovery loops are explicit at every risky stage (netlist, placement, routing, shorts). | 5 / 5 |
Progressive Disclosure | The body clearly signals a one-level-deep reference layer ("CLI primer: `CLI.md`", "Syntax primer: `SYNTAX.md`", "Workflow patterns: `WORKFLOW.md`", "Pre-export checklist: `CHECKLIST.md`", "Ready-to-copy templates: `templates/`", plus 80+ `./elements/*.md` links), but the actual bundle contains only `scripts/` — every one of those reference files is missing, so navigation dead-ends, and the 80-line element index is inlined content that clearly belongs in a separate file. Not 3: the problem is not unclear signaling but a largely absent reference layer; not 1 because SKILL.md itself is well-sectioned and references are one level deep with no nesting. | 2 / 5 |
Total | 15 / 20 Passed |