Automate Instagram tasks via Rube MCP (Composio): create posts, carousels, manage media, get insights, and publishing limits. Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:Lingjie-chen/MT5 --skill instagram-automation73
Quality
65%
Does it follow best practices?
Impact
82%
2.27xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./.trae/skills/instagram-automation/SKILL.mdDiscovery
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.
This description effectively communicates specific Instagram automation capabilities and is clearly distinguishable from other skills. However, it lacks an explicit 'Use when...' clause and could benefit from additional natural trigger terms that users might say when requesting Instagram-related help.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to post to Instagram, schedule content, or analyze Instagram performance.'
Include additional natural trigger terms like 'IG', 'social media posting', 'Instagram analytics', 'schedule Instagram posts', or 'Instagram stories/reels'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'create posts, carousels, manage media, get insights, and publishing limits.' These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' (automate Instagram tasks with specific actions listed), but lacks an explicit 'Use when...' clause. The 'when' is only implied by the Instagram context, not explicitly stated. | 2 / 3 |
Trigger Term Quality | Includes 'Instagram', 'posts', 'carousels', 'media', 'insights' which are relevant keywords, but missing common variations like 'IG', 'social media', 'stories', 'reels', or 'schedule posts' that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Instagram', 'Rube MCP (Composio)', and Instagram-specific terms like 'carousels' and 'publishing limits'. Unlikely to conflict with other skills due to platform-specific focus. | 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 skill provides comprehensive Instagram automation guidance with excellent workflow clarity and validation checkpoints. However, it lacks executable code examples (only pseudocode patterns) and is somewhat verbose with repeated pitfall information across sections. The structure is good but could benefit from splitting detailed reference material into separate files.
Suggestions
Add executable code examples showing actual MCP tool calls with concrete parameters and response parsing, not just numbered pseudocode steps
Consolidate repeated pitfall information (media URLs, rate limits) into the 'Known Pitfalls' section only, removing duplicates from individual workflows
Consider moving the Quick Reference table and detailed pitfalls to a separate REFERENCE.md file to reduce the main skill length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy - pitfalls are repeated across sections (media URLs mentioned multiple times), and the Quick Reference table duplicates information already covered in workflows. Some sections could be tightened. | 2 / 3 |
Actionability | Provides clear tool sequences and parameter names, but lacks executable code examples. The 'Common Patterns' section uses pseudocode-style numbered lists rather than actual API call examples with concrete payloads or response parsing. | 2 / 3 |
Workflow Clarity | Excellent multi-step workflow documentation with clear sequences, explicit validation checkpoints (polling GET_POST_STATUS before publishing), and feedback loops for video processing. Each workflow clearly marks required vs optional steps. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's somewhat monolithic at ~180 lines. The toolkit docs link is provided but detailed API reference could be split out. The Quick Reference table helps navigation but the document could benefit from separating detailed pitfalls into a reference file. | 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 | |
Table of Contents
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.