Name: facebook-messenger
Rating: 62.4 (1 reviews)
Author: membranedev

facebook-messenger

Facebook Messenger integration. Manage Users, Contacts, Stories, Reactions. Use when the user wants to interact with Facebook Messenger data.

Quality

73%

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/facebook-messenger/SKILL.md

Quality

Content

75%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 highly actionable, with concrete copy-paste Membrane CLI commands and a well-sequenced workflow. Its main drag is an introductory paragraph that over-explains what Facebook Messenger is — knowledge Claude already has — which costs token efficiency.

Suggestions

Delete or drastically trim the opening "Facebook Messenger is a messaging app and platform..." paragraph and the "Businesses also leverage it..." sentence; assume Claude knows what Messenger is.

Add an explicit validation checkpoint after connecting (e.g., re-run `connection list --json` to confirm the new connectionId appears) to strengthen the workflow's feedback loop.

Tighten the "Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing" aside, which over-explains the value proposition.

Dimension	Reasoning	Score
Conciseness	The opening "Facebook Messenger is a messaging app and platform where users connect with friends, family, and businesses. It's used by billions of people worldwide..." explains a concept Claude already knows, and "Businesses also leverage it for customer support and marketing" is fluff; the rest is mostly efficient CLI guidance.	3 / 5
Actionability	Copy-paste-ready commands are given throughout (login, search, connect, connection list, action list, action run, request) plus a full proxy flag table, covering the common cases concretely.	5 / 5
Workflow Clarity	A clear sequenced flow (setup → connect → list existing → discover actions → run → proxy) with headings and numbered steps; minor validation gaps (e.g., no explicit "verify the connection succeeded" checkpoint), and the skill is not destructive/batch so the workflow cap does not apply.	4 / 5
Progressive Disclosure	No bundle files exist, and the body is well-organized into clearly headed sections (Overview, Working with, setup, connecting, actions, proxy, best practices); content is appropriately self-contained for a CLI integration skill, though it exceeds the simple <50-line exception for a 5.	4 / 5
	Total	16 / 20 Passed

Description

71%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 cleanly names the platform and scope, and explicitly states a use-when trigger, giving strong distinctiveness. Its weakness is trigger breadth — only the literal product name is offered, with no natural synonyms or variations a user might actually say.

Suggestions

Broaden trigger terms: add natural phrasings like "Messenger", "messages", "chats", "conversations", or "DMs" so it fires on how users actually phrase the request.

Replace the single generic verb "Manage" with distinct concrete actions (e.g., "list, create, update, and delete Users, Contacts, Stories, and Reactions") to raise specificity.

Make the "Use when" clause enumerate concrete triggers (e.g., "Use when reading or sending Messenger messages, managing contacts, or pulling story/reaction data").

Dimension	Reasoning	Score
Specificity	"Manage Users, Contacts, Stories, Reactions" names the domain and lists four concrete entity targets, but reuses one generic verb ("Manage") rather than multiple distinct actions, so it falls short of comprehensive coverage.	4 / 5
Completeness	It answers both what ("Facebook Messenger integration. Manage Users, Contacts, Stories, Reactions.") and when ("Use when the user wants to interact with Facebook Messenger data."), but the trigger clause is single and broad rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	Only the literal phrase "Facebook Messenger" (repeated as "Facebook Messenger data") appears; common variations a user might say ("Messenger", "messages", "chats", "conversations", "DMs") are missing.	3 / 5
Distinctiveness Conflict Risk	"Facebook Messenger integration" carves a clear, product-specific niche with minimal overlap risk against other skills; the trigger is tightly bound to a named platform.	5 / 5
	Total	16 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

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

Reviewed: ~19 hours 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.