Content
71%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, genuinely actionable reference for Instagram publishing workflows with strong validation checkpoints (connection status, container polling, publishing limits). Its main weaknesses are redundancy across sections, a monolithic single-file layout with no progressive disclosure, and the absence of concrete example calls and explicit error-recovery loops.
Suggestions
Move the 16-row Quick Reference table and the detailed insights/comments workflows into a references/ file (e.g. TOOL_REFERENCE.md) and link to it from SKILL.md, keeping only the setup and core publishing workflows inline.
Deduplicate: state the RUBE_SEARCH_TOOLS-first rule, the 25-post limit, and the Business/Creator account requirement once each instead of repeating them across Prerequisites, Setup, individual workflows, and Known Pitfalls.
Add one concrete example tool call (with realistic parameter values and an abbreviated response) for the two-phase publish flow, and an explicit error-recovery loop for container-status polling and 429 backoff.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Tool sequences, key parameters, and pitfalls are dense with signal, but content is duplicated: 'Always call RUBE_SEARCH_TOOLS first' appears three times, the 25-posts/24-hour limit and account requirements are each stated in two sections, and 'Common Patterns' partially restates workflows 1-2. This matches the efficient-with-minor-trimmable-redundancy anchor at 4 rather than the every-token-earns-its-place anchor at 5. | 4 / 5 |
Actionability | Concrete tool slugs with [Required]/[Optional] markers, named parameters ('children': Array of media container IDs'), and a 16-row quick reference make the guidance mostly executable, but no example tool-call payloads or response shapes are shown and ID-resolution patterns are prose steps rather than demonstrated calls, so it falls short of the fully-executable anchor at 5. | 4 / 5 |
Workflow Clarity | Each workflow has a numbered tool sequence with explicit validation checkpoints (confirm connection ACTIVE, poll GET_POST_STATUS until 'FINISHED', check publishing limits before bulk posting), matching the clear-sequence-with-most-checkpoints anchor. It is not 5 because error-recovery feedback loops are only named as pitfalls (e.g. 'implement exponential backoff') rather than spelled out as poll -> fix -> retry steps. | 4 / 5 |
Progressive Disclosure | The body is a single ~190-line monolithic file with no references/ bundle; content that would fit reference files (the 16-row tool table, the detailed insights workflow) is all inline. Sections are well-organized, which matches the some-structure anchor at 3, but no one-level-deep reference split is signaled anywhere, and the under-50-line exception does not apply, so 4 is not reached. | 3 / 5 |
Total | 15 / 20 Passed |