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.

2.27x

Quality

65%

Does it follow best practices?

Impact

82%

2.27x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.trae/skills/instagram-automation/SKILL.md

Quality

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 like 'social media', 'IG', or 'schedule a post'.

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 mentions IG/social media publishing.'

Include additional natural trigger terms users might say, such as 'social media', 'IG', 'schedule post', 'reels', 'stories', 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 context.	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 appear in user requests.	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 skill provides comprehensive coverage of Instagram automation workflows with clear sequencing and validation steps, making it strong on workflow clarity. However, it suffers from moderate redundancy (pitfalls repeated in multiple places) and lacks concrete executable examples of actual MCP tool invocations, relying instead on tool name references and parameter lists. The monolithic structure could benefit from splitting detailed workflow content into separate files.

Suggestions

Add at least one concrete, executable MCP tool invocation example showing the actual call syntax with parameters filled in, rather than just listing tool names and parameter names.

Consolidate duplicated pitfalls—remove per-workflow pitfall entries that are repeated verbatim in the 'Known Pitfalls' section, or vice versa, to reduce token usage.

Consider splitting detailed workflow sections (carousel, insights, comments) into a separate WORKFLOWS.md file, keeping SKILL.md as a concise overview with the quick reference table and links.

Dimension	Reasoning	Score
Conciseness	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 workflow 4 and Known Pitfalls). The 'Known Pitfalls' section largely duplicates per-workflow pitfalls. Some information like 'Personal accounts cannot use the Instagram Graph API' is stated twice.	2 / 3
Actionability	Tool sequences are clearly listed with named tools and key parameters, which is helpful. However, there are no executable code examples or concrete MCP call syntax—just tool names and parameter lists. The 'Common Patterns' section uses pseudocode-style numbered lists rather than actual invocation examples. Claude would need to search for tool schemas anyway (as the skill itself instructs), reducing the actionability of the parameter documentation.	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. Each workflow marks steps as Required/Optional, and pitfalls call out what happens if steps are skipped.	3 / 3
Progressive Disclosure	The content is well-organized with clear sections and a quick reference table, but it's quite long (~180 lines of content) with no references to external files for detailed information. The per-workflow pitfalls and the consolidated 'Known Pitfalls' section could be split out. The toolkit docs link is provided but there's no layered structure—everything is inline in one file.	2 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

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: Lingjie-chen/MT5
Commit: 3069d33

Reviewed: 26 days ago

Table of Contents

Discovery Implementation Validation

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.