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.
The body is an exemplar of token efficiency — a lean, well-organized rule set with explicit applicability guidance and no external references to manage. Its only real weakness is actionability: the rules state what must hold but give no worked examples or concrete application procedure, leaving the agent to interpret how to verify compliance.
Suggestions
Add one short worked example showing a compliant vs. non-compliant sync-behavior change (e.g. a fake toggle vs. a rule-backed control) to make 'UI controls must map to real business rules' concrete.
Add an explicit application step such as 'Review any proposed change against Product Rules 1–5 and Sync Rules before implementing' to serve as a validation checkpoint and lift workflow clarity.
For 'fail loudly rather than dropping data silently', specify what loud failure means in Engram (e.g. surfaced error vs. silent queue drop) so the rule is testable in practice.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is ~30 lines of terse directives ("Local-first remains the default mental model", "fail loudly rather than dropping data silently") with no padding and no explanation of concepts Claude already knows — every token earns its place. | 5 / 5 |
Actionability | The rules are reasonably concrete as design criteria ("must be enforceable server-side", "must be deterministic and testable"), but there are no concrete examples, commands, or mechanisms for applying them — fitting 'some concrete guidance but incomplete' rather than the mostly-executable anchor at 4. | 3 / 5 |
Workflow Clarity | This is a simple, single-purpose skill under 50 lines with an explicit 'When to Use' section, so the simple-skill exception applies and the single action is mostly unambiguous; it falls short of 5 because there is no rule-application or validation checkpoint (e.g. 'verify the proposed change against each rule before implementing'). | 4 / 5 |
Progressive Disclosure | The skill is under 50 lines with no need for external references and no bundle files, and the body is cleanly organized into three well-headed sections (When to Use, Product Rules, Sync Rules), which satisfies the simple-skill criterion for a top score. | 5 / 5 |
Total | 17 / 20 Passed |