Name: instagram-messenger
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

instagram-messenger

Instagram Messenger integration. Manage Users. Use when the user wants to interact with Instagram Messenger data.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/instagram-messenger/SKILL.md

Quality

Content

63%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 is a genuinely actionable CLI integration guide with a clear workflow and validation loop, but it opens with unnecessary concept explanation and inlines a large actions catalog that would benefit from a separate reference file. Conciseness and progressive disclosure are the main weaknesses.

Suggestions

Delete or compress the opening paragraph explaining what Instagram Messenger is; Claude already knows this and it costs context tokens.

Move the 'Popular actions' table and proxy flag reference into a separate references file (e.g. actions.md) and link to it from the body to improve progressive disclosure.

Fix the step numbering inconsistency (references to 'Step 2' with no clearly labeled Step 2) and add one runnable example with a real parameter payload for `membrane action run`.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete CLI commands, but the opening paragraph ('Instagram Messenger is a direct messaging platform integrated within the Instagram app...') explains a concept Claude already knows, and a few prose passages could be trimmed.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands for install, login, connection, action search/run, and proxy requests plus a flags table; minor gaps remain where placeholders like CONNECTION_ID need substitution and action parameters lack examples.	4 / 5
Workflow Clarity	Clear install → authenticate → connect → search → run sequence with an explicit state-polling feedback loop (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and re-poll guidance; minor gaps include the slightly inconsistent step numbering ('skip to Step 2' without a clearly labeled Step 2).	4 / 5
Progressive Disclosure	No bundle files exist and the body is well-sectioned, but the 18-row 'Popular actions' table and the proxy flag reference are inlined content that would navigate better as a separate reference file, and there are no one-level-deep references for deeper material.	3 / 5
	Total	14 / 20 Passed

Description

62%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 correctly answers both what and when with an explicit 'Use when' trigger and a distinct domain, but it undersells the skill's actual messaging capabilities and lacks common synonyms like 'DM' or 'direct message'. Specificity and trigger coverage are the weakest aspects.

Suggestions

Replace the generic 'Manage Users' with concrete messaging actions, e.g. 'Send and receive Instagram direct messages, manage conversations, react to messages, and retrieve user profiles.'

Add natural trigger synonyms users say, such as 'DM', 'direct message', and 'Instagram inbox', to the 'Use when' clause.

Tighten the 'when' clause to specific intents, e.g. 'Use when the user wants to send or read Instagram DMs, manage inbox conversations, or retrieve Instagram user profiles.'

Dimension	Reasoning	Score
Specificity	Names the domain ('Instagram Messenger integration') and one concrete action ('Manage Users'), but does not enumerate the messaging capabilities that make up the bulk of the skill, so coverage is not comprehensive.	3 / 5
Completeness	Both a 'what' ('Manage Users') and an explicit 'when' ('Use when the user wants to interact with Instagram Messenger data') are present; the 'what' is thin but the trigger guidance is explicit, sitting above the midpoint.	4 / 5
Trigger Term Quality	Includes the natural keyword 'Instagram Messenger' and the trigger phrase 'interact with Instagram Messenger data', but misses common variations users say such as DM, direct message, or inbox.	3 / 5
Distinctiveness Conflict Risk	The 'Instagram Messenger' niche is mostly distinct with clear triggers, though there is minor overlap risk with a generic Instagram or Facebook Messenger skill.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/instagram-messenger/SKILL.md
Commit: f484c82

Reviewed: 5 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.