Content
90%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 token-efficient, highly actionable reference for a cross-repo bridge: concrete search anchors, message payloads, and verification commands with no conceptual padding. Workflow and disclosure are strong, with only minor gaps in interleaved validation checkpoints and optional splitting of message-contract details.
Suggestions
Interleave validation into the Change Checklist (e.g., append a 'verify with yarn agent:check --profile commit and chart npm run build' step) so the workflow reads as validate-then-proceed rather than checklist + separate verification block.
Consider extracting the per-message contract payloads (Market Kline, Marks, Hyperliquid Price Scale, Perps Symbol Sync, Perps Lines) into a references/ file linked from a short Message Contracts overview, keeping SKILL.md leaner.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and assumes Claude's competence — it never explains what TradingView/WebView/iframe are, and every line is load-bearing (search anchors, payload shapes, params, checklist) with no padded conceptual prose. | 5 / 5 |
Actionability | It gives concrete executable guidance: `rg` search anchors with exact symbol names, complete TypeScript message payloads, named handlers, URL params, and verification commands (`yarn agent:check --profile commit`, `npm run build`, `npm run lint`). | 5 / 5 |
Workflow Clarity | The 9-step Change Checklist plus a Verification section with a pre-commit checkpoint (`yarn agent:check --profile commit`) form a clear sequence with validation, but the checklist steps and verification are presented as separate blocks rather than interleaved validate-then-proceed feedback loops. | 4 / 5 |
Progressive Disclosure | Content is well-organized into clear sections (Mental Model, Search Anchors, URL Parameters, Message Contracts, Change Checklist, Verification) with no nesting, and no bundle files exist to reference; the only minor gap is that the detailed per-message contracts could optionally live in reference files rather than inline. | 4 / 5 |
Total | 18 / 20 Passed |