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

newsman

Newsman integration. Manage data, records, and automate workflows. Use when the user wants to interact with Newsman 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/newsman/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 highly actionable with executable Membrane commands and a clear connection workflow including state checkpoints and feedback loops. Its main weaknesses are a padded introductory paragraph and minor structural redundancy between the action-search sections.

Suggestions

Cut or condense the introductory paragraph explaining what Newsman is and its audience; Claude already knows email-marketing platform basics.

Either populate "Popular actions" with named example actions or fold it into "Searching for actions" to remove the redundant discovery instruction.

Re-number the connection steps consistently (1a/1b/2) and add an explicit validation check before running actions that could be destructive or batch.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and tables, but the opening paragraph explaining what Newsman is and who uses it ("Marketing teams and small business owners use Newsman...") is background Claude does not need, fitting the "mostly efficient but includes some unnecessary explanation" anchor.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, action search/run, and proxying with a flags table, but the "Popular actions" heading only re-issues a discovery command rather than listing actual actions, leaving a minor gap versus fully-worked examples.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, but step numbering is inconsistent ("1b" and a referenced "Step 2" without a clean 1a/1b/2 structure) and running actions lacks explicit pre-flight validation.	4 / 5
Progressive Disclosure	With no bundle files present, the single-file body is well-organized into logical sections (Overview, Auth, Connecting, Searching, Running, Proxy, Best practices), but the "Newsman Overview" list and overlapping "Searching for actions"/"Popular actions" sections show minor organization gaps.	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 correctly uses third person and includes an explicit "Use when" clause covering both what and when, but its action language and trigger terms are generic rather than tied to Newsman's email-marketing specifics. It is solid but could be sharpened with concrete campaign/contact keywords.

Suggestions

Replace generic verbs with concrete Newsman actions, e.g. "Create and send email campaigns, manage contact lists, and track campaign reports".

Add natural trigger terms users say, such as "email campaigns", "newsletters", "contact lists", or "subscriber lists", alongside "Newsman".

Tighten the "when" clause to concrete triggers, e.g. "Use when the user wants to send or manage Newsman email campaigns and contacts."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Newsman domain plus a couple of actions, but the actions are generic abstractions rather than concrete email-marketing operations, matching the anchor that names a domain with 1-2 non-comprehensive actions.	3 / 5
Completeness	It states both a clear "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Newsman data"), but the trigger phrase is generic rather than concrete, matching the anchor where both are present yet the "when" could be more specific.	4 / 5
Trigger Term Quality	It surfaces the brand keyword "Newsman" plus "data", "records", and "workflows", but omits the natural email-marketing phrases users would actually say (campaigns, email lists, contacts, newsletters), fitting the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	The named product "Newsman" gives it a clear niche with low conflict risk, but the generic "manage data, records, automate workflows" phrasing leaves minor overlap with broad data-skill triggers, fitting the "mostly distinct; minor overlap risk" anchor.	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/newsman/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.