Content
11%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 a skeleton with almost no instructional substance: a truncated persona paragraph, bare keyword lists, pattern names without techniques, and anti-pattern headings without content. It provides no executable guidance, no workflow, and no meaningful organization, leaving a reader with nothing actionable to apply.
Suggestions
Replace the persona narrative with concrete techniques, e.g. specific trimming heuristics (drop oldest tool outputs first, retain system prompt and last N turns), token-counting commands, and when-to-summarize vs. when-to-retrieve decision rules.
Fill in the three empty Anti-Pattern sections with what each looks like and what to do instead (e.g. Naive Truncation → preserve system prompt and task statement; truncate middle turns first).
Fix the truncated sentence ("Your cor...") and replace the circular "When to Use" filler with genuine applicability conditions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short in line count but padded: the opening paragraph repeats the frontmatter persona verbatim and is truncated mid-sentence ("Your cor"), Capabilities is a bare keyword list, the three Anti-Pattern headings ("### ❌ Naive Truncation", "### ❌ Ignoring Token Costs", "### ❌ One-Size-Fits-All") have zero content, and "When to Use" is circular filler ("This skill is applicable to execute the workflow or actions described in the overview"). This matches anchor 2 (several padded sections); it is not 3 because almost no token here earns its place, and not 1 because there is no wall of over-explanation. | 2 / 5 |
Actionability | No code, commands, or concrete executable guidance anywhere. Pattern entries like "Place important content at start and end" and "Summarize by importance, not just recency" are high-level hints, and the anti-patterns are empty headings with no explanation of what to do instead. This matches anchor 1 (entirely vague; only describes rather than instructs); anchor 2 would require at least minimal concrete steps. | 1 / 5 |
Workflow Clarity | There is no sequence of steps, no decision guidance (e.g. when to summarize vs. when to trim), and no validation checkpoints. Even under the simple-skill exception, workflow clarity requires an unambiguous single action, and no actionable instruction exists at all. Anchor 1 (steps missing or incoherent) fits. | 1 / 5 |
Progressive Disclosure | No bundle files exist (references/, scripts/, assets/ are absent), so the score rests on body organization alone. The under-50-lines guideline allows a 5 only for well-organized sections, but the sections here are hollow stubs — empty anti-pattern headings, a truncated sentence, and a circular When-to-Use line — which is minimal, poorly organized structure matching anchor 2 rather than the 'some structure' of anchor 3. | 2 / 5 |
Total | 6 / 20 Passed |