Content
81%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 actionable, well-structured reference: exact link forms, a decision table keyed by render host, hard rules, and a validation-bearing pass checklist. Its main weakness is redundancy — the same rules are restated in the decision table, forms, hard rules, and pass — which inflates token cost without adding guidance.
Suggestions
State each rule once in its canonical section and have "The pass" reference it tersely (e.g. 'No SHA pins — see Absolute GitHub URL') instead of restating the rule; the main-only, npm-absolute, and cross-host-fragment rules currently appear two to three times each.
Move the Grida URLs table and the engine-repo decision prose into a references/ file (e.g. references/hosts.md) and keep SKILL.md to the decision table, hard rules, and the pass, cutting roughly a third of the body.
Trim rhetorical asides ("This is correctness, not hygiene", "far more often than you'd expect") and compress the repeated rationale in the relative-vs-absolute rules to one sentence each.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body avoids explaining concepts Claude already knows and is dense with repo-specific rules, but the same rules recur across the decision table, "The forms", "Hard rules", and "The pass" (main-only pins appear three times; npm-absolute and cross-host-fragment rules twice each), plus asides like "This is correctness, not hygiene" that could be trimmed. It fits the 'mostly efficient but could be tightened' anchor rather than the 'minor instances' anchor above. | 3 / 5 |
Actionability | Guidance is fully executable for an instruction-only skill: exact URL templates ("https://grida.co/docs/<path>", ".../blob/main/<path>"), a worked transformation ("docs/wg/platform/billing/ai-credits.md → https://grida.co/docs/wg/platform/billing/ai-credits"), and verifiable commands ("git ls-files", "git check-ignore"). Specific examples cover the common cases. | 5 / 5 |
Workflow Clarity | "The pass" is a clear 7-step numbered checklist with explicit validation checkpoints (verify the target is published, not draft/unlisted or generated; pre-commit gate that no local-only/untracked target exists). The skill is non-destructive, so the missing-validation cap does not apply, and the sequence (three questions → decision table → forms → hard rules → pass) is coherent. | 5 / 5 |
Progressive Disclosure | No bundle files exist and the single ~140-line file is well-sectioned with tables, hard rules, and a summary checklist — good structure with no nested references. It falls short of a 5 because it exceeds a lean single-file size and reference material like the Grida URL table and the engine-cluster decision prose could live in a separate one-level-deep reference file. | 4 / 5 |
Total | 17 / 20 Passed |