Lists multiple specific concrete actions: 'create posts, carousels, manage media, get insights, and publishing limits.' These are distinct, actionable capabilities.

Clearly answers 'what does this do' with specific Instagram automation tasks, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the domain context.

Includes relevant keywords like 'Instagram', 'posts', 'carousels', 'media', 'insights', and 'publishing limits', but misses common user variations like 'stories', 'reels', 'schedule post', 'social media', or 'IG'. The mention of 'Rube MCP (Composio)' is technical jargon unlikely to be used by end users.

Highly distinctive due to the specific platform (Instagram) and tooling (Rube MCP/Composio). Unlikely to conflict with other skills given the narrow niche of Instagram automation.

The skill is reasonably well-structured but includes some redundancy—pitfalls are repeated across sections (e.g., media URLs must be public appears multiple times, publishing limits mentioned in both the workflow and Known Pitfalls). The 'Known Pitfalls' section largely duplicates per-workflow pitfall notes. Some explanations like 'User wants to publish a single photo or video to Instagram' are unnecessary padding.

Tool sequences are clearly listed with named tools and key parameters, which is helpful. However, there are no executable code examples or actual MCP call syntax—just tool names and pseudocode-style sequences. The 'Common Patterns' section uses plain text blocks rather than actual executable calls. Claude would need to discover exact call signatures via RUBE_SEARCH_TOOLS anyway, but concrete call examples would improve actionability.

Multi-step workflows are clearly sequenced with numbered steps, explicit validation checkpoints (polling container status before publishing), and feedback loops (wait until 'FINISHED' before proceeding). The two-phase publishing pattern is well-articulated, and the carousel workflow correctly notes that all children must complete before creating the carousel container. Destructive/batch operation guidance includes checking publishing limits first.

The content is well-organized with clear sections and a quick reference table, but it's a monolithic document (~170 lines) with no bundle files to offload detailed content. The per-workflow pitfalls, known pitfalls section, and quick reference table could be split into separate files. The single external link to Composio docs is appropriate but the skill itself could benefit from splitting detailed workflow guides into separate files.