Content
40%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 well-sectioned but content-thin: it provides no executable code or commands, no defined workflow, and a placeholder When-to-Use, relying on terse one-liners and comment-style solutions. Several sections are empty or truncated, which undercuts the otherwise clean structure.
Suggestions
Add concrete, executable examples for the key patterns — a DataLoader batching snippet, a query depth/complexity limit config, and a field-level authorization resolver — instead of one-line descriptions and comment-style solutions.
Define an actual review workflow with validation checkpoints (e.g., check N+1 → check depth/complexity limits → check authorization in resolvers → check nullability design) and replace the generic "When to Use" placeholder with real trigger guidance.
Remove the duplicated persona intro and the truncated "You've l" sentence, and flesh out the empty Anti-Patterns entries with concrete guidance so every section earns its tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short overall, but the persona intro is duplicated verbatim from the frontmatter and the "hard-won lessons" anecdote is atmospheric fluff that assumes Claude does not already know these GraphQL pitfalls, so it could be tightened. | 3 / 5 |
Actionability | There is no executable code or commands anywhere; the Sharp Edges "solutions" are comment-style hints ("# USE DATALOADER", "# LIMIT QUERY DEPTH AND COMPLEXITY") and the Patterns are one-liners ("Batch and cache database queries"), giving only high-level hints rather than steps to execute. | 2 / 5 |
Workflow Clarity | No multi-step process or sequence is defined — the body is a collection of lists and a table — and the "When to Use" section is a meaningless placeholder ("This skill is applicable to execute the workflow or actions described in the overview"), leaving rough structure but no actual workflow or checkpoints. | 2 / 5 |
Progressive Disclosure | Sections are clearly headed (## Capabilities, ## Patterns, ## Anti-Patterns, ## Sharp Edges) and no external references are needed for this thin, self-contained content; minor gaps (empty Anti-Patterns entries, the placeholder When-to-Use, and a truncated sentence) keep it just below a 5. | 4 / 5 |
Total | 11 / 20 Passed |