Name: the-media-trust
Rating: 52 (1 reviews)
Author: membranedev

the-media-trust

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

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/the-media-trust/SKILL.md

Quality

Content

57%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 Membrane CLI guide with copy-paste commands and a clear connection state machine. It is held back by a verbose marketing intro, no validation guidance for destructive proxy/action calls, and an absence of progressive disclosure — all detail lives inline with no supporting reference files.

Suggestions

Trim the marketing intro to one line and remove editorializing ('rather than auth plumbing') to respect the token budget.

Add a validation/verification checkpoint before destructive proxy requests (e.g., confirm method and target, then check the response status/output) so the workflow clears the destructive-operation cap.

Extract the clientAction state machine and the proxy flag table into a reference file (e.g., references/connection-states.md) referenced one level deep from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight, command-driven content, but the marketing-style intro ('provides digital safety and anti-malware solutions... helps ad operations, compliance, and security teams monitor and protect their digital ecosystems') and editorializing like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary explanation Claude does not need.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection ensure, action search/run, and proxy requests with a flag table, covering the common cases with only minor gaps such as the thin 'Popular actions' section that just repeats the search command.	4 / 5
Workflow Clarity	The connection flow is well sequenced with a state machine and feedback loops (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but action execution and proxy requests support destructive methods (DELETE/PUT) with no validation or output-verification step, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	The body has reasonable section headers but no bundle files exist and everything — the detailed clientAction state machine, the proxy flag table, action discovery — is inlined in a 140-line SKILL.md rather than split into one-level-deep references, fitting 'content that should be separate is inline'.	3 / 5
	Total	13 / 20 Passed

Description

57%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 the skill does and when to use it in third person, anchored by a distinct product name. Its main weakness is generic capability language ('manage data, records, automate workflows') that lacks the concrete Media Trust actions a user would actually name.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Media Trust capabilities such as 'investigate violations, review campaigns, and audit advertisers and publishers'.

Expand the 'Use when' clause with specific triggers users would say, e.g. 'Use when the user wants to look up Media Trust violations, review campaign quality, or audit advertiser/publisher activity'.

Add domain synonyms (ad quality, malware, compliance) to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ('The Media Trust integration') but the actions 'Manage data, records, and automate workflows' are generic rather than concrete capabilities tied to the product (e.g., violations, campaigns, advertisers), matching the 'actions minimal or generic' anchor better than the 'concrete actions' anchor.	2 / 5
Completeness	Both 'what' (integrate, manage data/records, automate workflows) and 'when' ('Use when the user wants to interact with The Media Trust data') are present, but the 'when' is generic rather than listing concrete trigger phrases, matching the 'both present, when could be more specific' anchor.	4 / 5
Trigger Term Quality	The brand term 'The Media Trust' plus 'data', 'records', 'workflows' give some relevant keywords, but natural variations a user would actually say (violations, campaigns, ad quality, malware) are missing, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The named product 'The Media Trust' gives a clear niche with low conflict risk, but the generic 'manage data, records, automate workflows' phrasing leaves minor overlap risk with other data-management skills.	4 / 5
	Total	13 / 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/the-media-trust/SKILL.md
Commit: f484c82

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