instagram-automation
Automate Instagram tasks via Rube MCP (Composio): create posts, carousels, manage media, get insights, and publishing limits. Always search tools first for current schemas.
73
65%
Does it follow best practices?
Impact
82%
2.27xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/instagram-automation/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is strong in specificity and distinctiveness, clearly naming Instagram as the platform and listing concrete actions like creating posts, carousels, and getting insights. However, it lacks an explicit 'Use when...' clause which caps completeness, and the trigger terms could be broader to capture more natural user language variations.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about posting to Instagram, managing Instagram content, checking Instagram analytics, or automating social media tasks on Instagram.'
Include additional natural trigger terms users might say, such as 'IG', 'social media', 'reels', 'stories', 'schedule Instagram post', or 'Instagram analytics'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'create posts, carousels, manage media, get insights, and publishing limits.' These are distinct, actionable capabilities. | 3 / 3 |
Completeness | 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 (Instagram tasks). | 2 / 3 |
Trigger Term Quality | 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. | 2 / 3 |
Distinctiveness Conflict Risk | 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. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid instructional skill with clear workflow sequences and good validation checkpoints for the two-phase publishing model. Its main weaknesses are moderate verbosity from repeated information across sections and the lack of concrete, executable tool call examples. The content would benefit from deduplication and splitting detailed reference material into separate files.
Suggestions
Add at least one concrete, executable MCP tool call example with actual parameter values (e.g., a complete RUBE_SEARCH_TOOLS call followed by INSTAGRAM_CREATE_MEDIA_CONTAINER with sample parameters) to improve actionability.
Consolidate repeated pitfalls (public URLs, publishing limits, account requirements) into the single 'Known Pitfalls' section and remove duplicates from individual workflow sections to improve conciseness.
Extract the quick reference table and detailed pitfalls into a separate REFERENCE.md file, keeping SKILL.md as a leaner overview with pointers to the reference material.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some redundancy—pitfalls are repeated across sections (e.g., public URLs mentioned multiple times, publishing limits stated in both the workflow section and Known Pitfalls), and some information Claude would already know (like what a carousel is). The quick reference table at the end duplicates information already covered in the workflows. | 2 / 3 |
Actionability | Tool sequences are clearly listed with specific tool names and parameters, which is good. However, there are no executable code examples—the 'Common Patterns' section uses pseudocode-style descriptions rather than actual MCP call examples with concrete parameter values. The guidance is specific enough to follow but lacks copy-paste-ready examples showing actual tool invocations with sample parameters. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with numbered steps, explicit validation checkpoints (polling container status before publishing), and feedback loops (wait until status is 'FINISHED'). The two-phase publishing pattern is well-documented with clear ordering constraints, and destructive operations have appropriate guards (check publishing limits before bulk posting). | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a useful quick reference table, but it's quite long (~180 lines) with no bundle files to offload detailed content. The pitfalls sections, detailed parameters, and the quick reference table could be split into separate reference files. The single external link to Composio docs is appropriate but the skill itself is monolithic. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
74c7031
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.