Content
93%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.
An exemplary routing-focused skill body: lean, fully actionable, with a clear workflow and well-signaled one-level-deep references into an existing bundle. The only gap is the absence of explicit validation/feedback steps in the workflow, which is acceptable for this non-destructive integration/debugging context.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~38-line body contains no padding or explanations of concepts Claude already knows; every line is routing, a non-obvious trick ("append `.md` to any page URL on https://tiptap.dev/docs"), or safety guidance, so every token earns its place. | 5 / 5 |
Actionability | Guidance is fully concrete: exact URL patterns ("https://tiptap.dev/docs/llms.txt"), the exact source path ("node_modules/@tiptap/*"), and a copy-paste-ready `git clone --depth 1 --filter=blob:none` command; the instruction-only guidance is specific and executable throughout. | 5 / 5 |
Workflow Clarity | The 3-step workflow (identify framework/versions/feature, read docs and installed source, load only relevant references) is a clear sequence with a routing table, and step 2's "Match the implementation to the installed version" acts as a checkpoint. It lacks explicit validation/feedback loops, so it falls short of the 5 anchor; no destructive or batch operations apply the 3-cap. | 4 / 5 |
Progressive Disclosure | The task-to-reference table routes to all four real, one-level-deep reference files (references/setup.md, collaboration.md, ai.md, document-features.md), with an explicit "Load a reference only if its topic applies" rule and a docs-index fallback for unlisted topics; the references themselves point to external docs rather than nesting further files. | 5 / 5 |
Total | 19 / 20 Passed |