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

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers concrete, well-sequenced Instagram workflows with real validation checkpoints and a useful quick-reference table. Its main weaknesses are duplicated pitfall content and an empty 'When to Use' section that add tokens without value.

Suggestions

Remove the redundant 'Known Pitfalls' section or fold it into the per-workflow 'Pitfalls' so each pitfall appears once, cutting token cost.

Replace the vacuous 'When to Use' line with concrete trigger conditions (e.g. publishing posts/carousels, pulling insights, checking publishing limits) or delete the section.

Add an explicit error-recovery loop for publishing failures (e.g. on non-FINISHED status or 429, poll/back off and retry) to strengthen workflow_clarity for batch operations.

DimensionReasoningScore

Conciseness

The body is mostly lean and avoids explaining concepts Claude already knows, but the 'Known Pitfalls' section duplicates per-workflow pitfalls (public URLs, 25-post limit, Business/Creator requirement) and the 'When to Use' section is vacuous, so it could be tightened.

3 / 5

Actionability

Concrete tool slugs, ordered tool sequences, and key parameters are given for each workflow; exact schemas are intentionally deferred to RUBE_SEARCH_TOOLS, leaving only minor gaps.

4 / 5

Workflow Clarity

Workflows are clearly sequenced with [Required]/[Optional] markers and validation checkpoints (FINISHED status polling, publishing-limit checks, ACTIVE connection confirmation), but explicit validate-fix-retry feedback loops are absent.

4 / 5

Progressive Disclosure

Well-organized into Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, and Quick Reference with no nested or broken references; no bundle files exist, and the single-file structure is appropriate with only minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

66%Weight 40%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 is specific and distinct, listing five concrete Instagram actions under a clear Rube MCP framing, but it omits an explicit 'Use when...' trigger clause, which caps its completeness. Adding a usage-trigger sentence would raise the completeness and trigger-term scores.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user wants to publish or analyze Instagram Business/Creator content via Composio's Rube MCP.'

Add natural synonyms users say, such as 'Instagram post', 'IG carousel', 'post analytics', or 'schedule Instagram media', to broaden trigger-term coverage.

Optionally mention the Business/Creator account requirement in the description so the niche and prerequisites are clearer up front.

DimensionReasoningScore

Specificity

Names the Instagram domain and lists several concrete actions ('create posts, carousels, manage media, get insights, and publishing limits'), with only minor gaps (comments/children/user-info from the body are omitted).

4 / 5

Completeness

Clearly states what the skill does but provides no 'Use when...' trigger clause; the trailing 'Always search tools first' is operational guidance, not a usage trigger, so completeness is capped at 3.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('posts', 'carousels', 'insights', 'publishing limits') but lacks synonyms or file-format-style variations, leaving a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

Scoped to Instagram automation via Rube MCP (Composio), a distinct niche with mostly distinct triggers and only minor overlap risk with generic social-media skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.