CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/instagram-automation/SKILL.md

The canonical home for this skill is instagram-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

63%Scale 1-5

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, well-organized skill that provides clear tool sequences and practical pitfall warnings for Instagram automation via Rube MCP. Its main weaknesses are redundancy across sections (especially repeated pitfalls), lack of executable code examples for MCP calls, and all content being inlined in a single file when some could be split out. The workflow sequencing is good with status-check validation steps, though error recovery guidance could be more explicit.

Suggestions

Consolidate pitfalls into the 'Known Pitfalls' section only, removing duplicates from individual workflow sections to reduce redundancy and improve conciseness.

Add at least one concrete, executable MCP call example showing actual parameter JSON structure rather than pseudocode descriptions.

Consider splitting detailed workflows (insights, comments/children) into a separate reference file to improve progressive disclosure and reduce the main file length.

Remove the vacuous 'When to Use' section at the end — it adds no information beyond what the title and description already convey.

DimensionReasoningScore

Conciseness

The skill is moderately efficient but contains redundancy — multiple workflows repeat the same pitfalls (public URLs, Business account requirements), the 'Known Pitfalls' section largely restates pitfalls already mentioned in individual workflows, and the 'When to Use' section at the end is vacuous. The quick reference table is useful but some content could be consolidated.

3 / 5

Actionability

The skill provides concrete tool sequences with specific tool names, key parameters, and clear step ordering. However, it lacks executable code examples — the 'Common Patterns' section uses pseudocode-style descriptions rather than actual MCP call examples with real parameter structures. The guidance is specific enough to act on but not fully copy-paste ready.

4 / 5

Workflow Clarity

Multi-step workflows are clearly sequenced with numbered steps, and the two-phase publishing pattern includes a validation checkpoint (poll status before publishing). The carousel workflow correctly sequences child creation before carousel container creation. However, error recovery is mostly limited to 'poll and wait' — there's no explicit guidance on what to do if container creation fails or if publishing returns an error beyond the pitfall notes.

4 / 5

Progressive Disclosure

The content is well-structured with clear sections and a useful quick reference table, but at ~180 lines it's quite long for a single file with no bundle files to offload detail into. The repeated pitfalls across sections and the detailed insights/comments workflows could be split into separate reference files. No external files are referenced despite the content length warranting it.

3 / 5

Total

14

/

20

Passed

Description

70%Scale 1-5

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 does a good job listing concrete Instagram automation capabilities and identifying the specific tooling (Rube MCP/Composio), making it highly distinctive. Its main weakness is the lack of an explicit 'Use when...' clause that would help Claude know exactly when to select this skill. Adding trigger guidance and a few more natural keyword variations would strengthen it.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Instagram posting, social media automation, or managing their Instagram account.'

Include additional natural trigger terms and synonyms such as 'social media', 'IG', 'reels', 'stories', 'schedule posts' to improve keyword coverage.

DimensionReasoningScore

Specificity

Lists several specific actions: 'create posts, carousels, manage media, get insights, and publishing limits.' These are concrete capabilities, though 'manage media' is somewhat vague. Minor gaps in coverage but generally good.

4 / 5

Completeness

The 'what' is clearly stated with specific actions. However, there is no explicit 'when' clause (e.g., 'Use when...'). The instruction to 'always search tools first' is operational guidance, not a trigger condition. Per rubric guidelines, missing 'Use when' caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural keywords like 'Instagram', 'posts', 'carousels', 'insights', 'publishing limits' that users would naturally say. Missing some variations like 'stories', 'reels', 'schedule', 'social media', or 'IG' that could improve coverage.

4 / 5

Distinctiveness Conflict Risk

Highly distinctive with specific platform (Instagram), specific integration (Rube MCP/Composio), and specific actions. Very unlikely to conflict with other skills due to the narrow, well-defined niche.

5 / 5

Total

16

/

20

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.