Content
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid workflow guidance for Instagram automation via Rube MCP with clear step sequences and good validation checkpoints. Its main weaknesses are redundancy across sections (pitfalls repeated in both per-workflow and consolidated sections) and lack of concrete executable examples showing actual tool invocations with parameters and expected responses. The document would benefit from deduplication and either adding concrete call examples or splitting detailed reference material into separate files.
Suggestions
Add at least one concrete, executable tool invocation example showing actual parameters and expected response structure (e.g., a complete RUBE_SEARCH_TOOLS call followed by INSTAGRAM_CREATE_MEDIA_CONTAINER with real parameter values).
Consolidate pitfalls into the 'Known Pitfalls' section only and remove the per-workflow pitfall subsections to eliminate redundancy, or keep per-workflow pitfalls minimal with a reference to the consolidated section.
Consider splitting the quick reference table and detailed workflow descriptions into a separate REFERENCE.md file to improve progressive disclosure and reduce the main file's length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some redundancy—pitfalls are repeated across sections (e.g., public URLs, account requirements mentioned multiple times), and the 'Known Pitfalls' section largely restates what was already covered in individual workflow pitfalls. The quick reference table adds value but the overall document could be tightened by ~30%. | 2 / 3 |
Actionability | Tool sequences are clearly listed with key parameters and labeled steps, which is good. However, there are no executable code examples or concrete API call demonstrations—everything is described at the tool-name level with pseudocode-style sequences rather than actual invocation examples showing parameters and expected responses. The guidance is specific enough to follow but not copy-paste ready. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with explicit validation checkpoints (e.g., poll GET_POST_STATUS before publishing, check publishing limits before bulk operations, confirm connection is ACTIVE before running workflows). The two-phase publishing pattern and carousel workflow both include clear feedback loops for container status checking. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a useful quick reference table, but it's a long monolithic document (~180 lines of substantive content) with no bundle files to offload detailed reference material. The pitfalls, common patterns, and detailed workflow sections could benefit from being split into separate referenced files, especially given the repetition between inline pitfalls and the consolidated 'Known Pitfalls' section. | 2 / 3 |
Total | 9 / 12 Passed |