Content
68%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 well-structured, actionable reference for Amplitude MCP automation with concrete tool sequences, parameter specs, and a worked JSON example. Its main gaps are missing verification steps for batch event and IDENTIFY operations (capping workflow clarity) and minor duplication across the pitfalls sections.
Suggestions
Add a verification step for batch event ingestion (e.g. re-query or check processing status) and for IDENTIFY to confirm property changes landed, since these are batch/eventually-consistent operations.
De-duplicate the per-workflow 'Pitfalls' blocks and the consolidated 'Known Pitfalls' section — keep one canonical location and cross-reference it to save tokens.
Provide one full end-to-end worked example (find user -> get activity -> identify) to push actionability from concrete fragments to a complete copy-paste-ready flow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is largely efficient, listing tool sequences and parameters without explaining concepts Claude already knows; the main trim opportunity is duplication between each workflow's 'Pitfalls' block and the consolidated 'Known Pitfalls' section, plus a Quick Reference table that re-lists tool slugs — matching 'efficient; minor instances that could be trimmed'. | 4 / 5 |
Actionability | Guidance is concrete and actionable — exact tool slugs, parameter objects, and a copy-paste-ready JSON example for $set/$add operations — fitting 'mostly executable guidance; concrete code or commands with minor gaps'; not a 5 because there is no full end-to-end worked example combining the steps. | 4 / 5 |
Workflow Clarity | Multi-step processes are clearly sequenced with some checkpoints (connection ACTIVE verification, cohort async status retry loop), but batch event ingestion and IDENTIFY operations lack verification steps, and the batch/destructive-without-validation cap holds at 3 — so it does not reach the 'most checkpoints present' level. | 3 / 5 |
Progressive Disclosure | Single-file skill with no bundle files present; structure is good — clear prerequisites, five labeled workflows, Common Patterns, Known Pitfalls, and a Quick Reference table giving easy navigation — matching 'good structure; most content appropriately placed; minor organization gaps'. | 4 / 5 |
Total | 15 / 20 Passed |