Content
61%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.
A well-structured, highly actionable MCP tool reference with concrete tool sequences, parameters, and pitfalls for every workflow. Its weaknesses are notable redundancy across sections (pitfalls repeated, a duplicative summary table) and the absence of validation/confirmation steps before the documented destructive delete operations.
Suggestions
Add an explicit verification step before destructive operations, e.g., 'Before DELETE_FOLDER/DELETE_SPACE: list contents (WRIKE_GET_FOLDERS / WRIKE_GET_SPACE), confirm scope with the user, and prefer the recycle-bin path (MODIFY_FOLDER) unless permanent deletion is explicitly requested.'
De-duplicate the deletion and date-format pitfalls that currently appear in both the per-workflow 'Pitfalls' blocks and the 'Known Pitfalls' section, and drop the Quick Reference rows that fully restate workflow parameters.
Include one or two example tool-call payloads (e.g., a WRIKE_CREATE_TASK body with folderId, title, responsibles) to make the guidance copy-paste ready.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a dense, Wrike-specific reference with no filler explaining concepts Claude already knows, but it has real redundancy: deletion warnings appear in both the folder-workflow pitfalls and the 'Known Pitfalls' section, the date format is stated three times, and the Quick Reference table restates the workflow sections. This fits anchor 3 ('mostly efficient but could be tightened') rather than 4, whose over-explanation would be only minor, and not 2 since nothing is generic padding. | 3 / 5 |
Actionability | Concrete, executable guidance throughout: exact tool slugs ('WRIKE_CREATE_TASK'), parameter names ('folderId', 'responsibles'), enum values ("'Active', 'Completed', 'Deferred', 'Cancelled'"), and formats ('YYYY-MM-DD'). It falls short of anchor 5 only because there are no example tool-call payloads showing an actual invocation, and it is clearly above anchor 3's pseudocode level. | 4 / 5 |
Workflow Clarity | Sequences are well-labeled ([Prerequisite]/[Required]/[Optional]) and setup includes a checkpoint ('Confirm connection status shows ACTIVE'), but the skill involves destructive operations (DELETE_FOLDER 'removes ALL contents permanently', DELETE_SPACE 'is irreversible') with no verification or confirmation step before deletion. Per the rubric, missing validation steps in destructive/batch workflows caps workflow clarity at 3. | 3 / 5 |
Progressive Disclosure | No bundle files exist, and the single-file body is well-organized with clear section headers, per-workflow structure, and a Quick Reference table for navigation. This fits anchor 4 ('good structure, minor organization gaps') rather than 5 because all parameter detail is inlined in one ~230-line file instead of an overview plus one-level-deep reference files. | 4 / 5 |
Total | 14 / 20 Passed |