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.
The body is a solid, executable CLI guide with well-structured sections and good auth/connection state handling. Its weaknesses are the lack of validation guidance for the destructive and batch operations it exposes, some padded introductory content, and the absence of worked action examples with real inputs.
Suggestions
Add verification steps around destructive and batch operations: confirm identity/GUID before delete-user-profile, check stop-campaign status after stopping, and verify upload counts after uploading events or profiles.
Fix the broken step reference — "skip to Step 2" points to a label that does not exist; label the "Searching for actions" section as Step 2 (and rename the oddly numbered "1b").
Trim the introductory platform paragraph and the 18-item feature bullet list, and move the popular-actions catalog into a references file to keep the overview lean.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient command-first documentation, but the introductory marketing paragraph ("CleverTap is a customer engagement and retention platform. It helps mobile-first brands personalize...") and the 18-item feature bullet list are unnecessary padding that could be trimmed. | 3 / 5 |
Actionability | Commands are concrete and executable throughout (install, login, connection ensure, action list/run, proxy flags), but there is no worked example of running a real action with actual input parameters — the run example only shows a generic '{"key": "value"}' placeholder, leaving a minor gap. | 4 / 5 |
Workflow Clarity | The connection workflow has good state-based branching and polling feedback loops, but the skill enables destructive and batch operations (Delete User Profile, Stop Campaign, Upload Events/Profiles) with no validation or verification steps, which caps workflow clarity at 3; additionally "skip to Step 2" references a step label that does not exist. | 3 / 5 |
Progressive Disclosure | The single-file body is well-organized with clear section headers and a coherent flow from setup to execution; the main gap is that the 15-row popular-actions catalog and the proxy flag table are bulk reference content inlined in the overview rather than split into a separate file. | 4 / 5 |
Total | 14 / 20 Passed |