Name: mediatoolkit
Rating: 62.4 (1 reviews)
Author: membranedev

mediatoolkit

Mediatoolkit integration. Manage Alerts, Users, Dashboards, Reports. Use when the user wants to interact with Mediatoolkit data.

Quality

74%

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/mediatoolkit/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.

A highly actionable integration guide with executable CLI commands, a solid connection-state workflow, and clear section structure. Its weaknesses are minor verbosity in the framing/auth prose, a duplicated action-list invocation, and an all-inlined structure that foregoes file-based progressive disclosure.

Suggestions

Trim the introductory 'Mediatoolkit is a media monitoring...' paragraph and the 'so you can focus on the integration logic' aside; assume Claude's competence.

De-duplicate the action-list command (it appears once as `membrane action list` and again as `npx @membranehq/cli@latest action list`) into one canonical form.

Move the detailed clientAction state machine and the proxy flag table into referenced files (e.g. CONNECTION_STATES.md, PROXY_REFERENCE.md) to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	It is mostly efficient with concrete commands, but includes unnecessary padding such as the opening 'Mediatoolkit is a media monitoring...' framing paragraph and phrases like 'so you can focus on the integration logic rather than auth plumbing', fitting the 'mostly efficient but could be tightened' anchor.	3 / 5
Actionability	It provides copy-paste-ready, fully executable commands throughout (install, login, connection ensure/get with --wait, action list/run with --input JSON, request proxy) plus a complete flag table, covering the common cases concretely.	5 / 5
Workflow Clarity	The connection setup is a clearly sequenced multi-step flow with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-after-action feedback loop; minor gaps include a duplicated action-list command form and loosely sequenced action-discovery sections.	4 / 5
Progressive Disclosure	The body is well-organized into clear single-level sections with no nested/deep references and easy navigation; however everything is inlined in one ~150-line file (e.g. the clientAction state machine and proxy flag table could live in referenced files), keeping it just short of the well-split score-5 anchor.	4 / 5
	Total	16 / 20 Passed

Description

73%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.

A concise, third-person description that clearly names both the integration's scope and a use-trigger, anchored on a distinctive product name. Its main weakness is the generic 'Manage' verb covering several entities and a trigger clause that could be more specific.

Suggestions

Replace the single generic verb 'Manage' with distinct concrete actions per entity (e.g. 'Create and resolve Alerts, invite Users, build Dashboards, schedule Reports').

Expand the 'Use when...' trigger with concrete natural-language scenarios a user would actually say (e.g. 'when the user mentions media monitoring, brand mentions, or PR crisis tracking').

Dimension	Reasoning	Score
Specificity	It names the domain and four concrete entities ('Manage Alerts, Users, Dashboards, Reports'), but the single generic verb 'Manage' applied to all four leaves the actions more enumerated-than-distinct, fitting the 'names domain and 1-2 concrete actions but not comprehensive' anchor better than the multi-verb score-4 example.	3 / 5
Completeness	Both 'what' ('Manage Alerts, Users, Dashboards, Reports') and 'when' ('Use when the user wants to interact with Mediatoolkit data') are present, but the 'when' clause is somewhat generic and could name concrete triggering scenarios more explicitly.	4 / 5
Trigger Term Quality	It anchors on the specific product name 'Mediatoolkit' plus the natural trigger phrase 'interact with Mediatoolkit data', giving good keyword coverage, though a few natural synonyms (e.g. 'mentions', 'media monitoring') a user might say are missing.	4 / 5
Distinctiveness Conflict Risk	The unique product name 'Mediatoolkit' carves a clear niche with distinct, product-specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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/mediatoolkit/SKILL.md
Commit: f484c82

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