Name: mentionlytics
Rating: 56.8 (1 reviews)
Author: membranedev

mentionlytics

Mentionlytics integration. Manage data, records, and automate workflows. Use when the user wants to interact with Mentionlytics data.

Quality

65%

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

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 content is a solid, actionable integration guide with executable Membrane CLI commands and a well-validated connection workflow. It is held back from the top tier by light verbosity and a minor broken step cross-reference.

Suggestions

Trim explanatory filler such as "so you can focus on the integration logic rather than auth plumbing" and the product-marketing overview of what Mentionlytics is.

Resolve the dangling "skip to Step 2" reference by labeling the Searching/Running sections as Step 2/3 or removing the cross-reference.

Add a brief validation note for action execution and proxy requests (e.g., check the response state/error field before proceeding) to close the workflow-clarity gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands with prose, but includes unnecessary padding such as "so you can focus on the integration logic rather than auth plumbing" and the introductory product overview of what Mentionlytics is, so it could be tightened toward anchor 4.	3 / 5
Actionability	It provides concrete, mostly copy-paste-ready commands throughout (install, login, connection ensure, action list/run, proxy flags table) covering the common cases, with only minor gaps from placeholder values like <actionId> and CONNECTION_ID.	4 / 5
Workflow Clarity	The connection setup has a clear sequence with explicit checkpoints (poll --wait until READY, handle CLIENT_ACTION_REQUIRED, inspect error fields), but the loose "skip to Step 2" cross-reference and the absence of validation guidance for action execution keep it just below anchor 5.	4 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is organized into clearly headed sections (Overview, Authentication, Connecting, Searching, Actions, Proxy, Best practices) giving good navigation, though the connection-state detail is somewhat long to keep fully inline.	4 / 5
	Total	15 / 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 is functional and distinct thanks to the Mentionlytics brand, with an explicit Use-when clause. Its main weakness is generic action language that under-specifies what the integration actually does.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete Mentionlytics actions such as monitors, mentions, sources, dashboards, alerts, and reports.

Broaden trigger terms to natural user phrasing like brand monitoring, social mentions, or online reputation tracking.

Keep the explicit "Use when..." clause but tie it to specific Mentionlytics nouns to sharpen both completeness and distinctiveness.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Mentionlytics domain plus a few action categories, but the actions are generic rather than concrete (no mention of monitors, mentions, alerts, or reports), landing between the minimal/generic and concrete anchors.	3 / 5
Completeness	It states a "what" ("Mentionlytics integration. Manage data, records, and automate workflows.") and an explicit "when" ("Use when the user wants to interact with Mentionlytics data."), but the "what" is somewhat generic so it does not reach the fully concrete anchor 5.	4 / 5
Trigger Term Quality	The trigger phrase "Use when the user wants to interact with Mentionlytics data" includes the key brand term and "data", but lacks common variations or synonyms a user might naturally say (mentions, brand monitoring, alerts), matching the "some relevant keywords but missing variations" anchor.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the specific Mentionlytics brand gives it a clear niche and low conflict risk, though the generic action phrasing ("manage data, records") leaves minor overlap risk with other data-management skills.	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/mentionlytics/SKILL.md
Commit: f484c82

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