Name: beehiiv
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

beehiiv

Beehiiv integration. Manage Users, Publications. Use when the user wants to interact with Beehiiv data.

Quality

66%

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/beehiiv/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 body is actionable and well-structured with a clear, checkpoint-driven connection workflow and concrete CLI commands. Its main weaknesses are a padded introductory explanation of what Beehiiv is and an inline actions table that could be split out for better token economy.

Suggestions

Trim or remove the opening paragraph explaining what Beehiiv is, since Claude already knows the platform; lead with the integration overview instead.

Consider moving the popular-actions table into a reference file and linking it, keeping only a few representative actions inline in SKILL.md.

Add an explicit validation/check step after running destructive actions like delete-post or delete-subscription (e.g., verify with a get/list call) to strengthen the feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but opens with an unnecessary explainer about what Beehiiv is ('an email newsletter platform built for writers and creators... used by individuals and organizations') and includes some phrasing that could be tightened, matching the score-3 anchor.	3 / 5
Actionability	It provides concrete, executable membrane commands throughout (action list/run, connection ensure/get, request with a flags table), with only minor gaps like the CONNECTION_ID placeholder, matching the score-4 anchor.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with polling and explicit state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a re-poll feedback loop, with only minor validation gaps, matching the score-4 anchor.	4 / 5
Progressive Disclosure	The skill is a single well-organized file with clear sections, but the large inline popular-actions table could arguably live in a separate reference; no bundle files are present, so it lands at the score-4 anchor rather than 5.	4 / 5
	Total	15 / 20 Passed

Description

66%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 clearly identifies the Beehiiv niche and includes both a 'what' and a 'when' clause, but the listed capabilities are minimal and the trigger term coverage is thin. It is distinct but could enumerate more concrete actions and natural trigger phrases.

Suggestions

List more concrete actions beyond 'Manage Users, Publications' (e.g., create posts, list subscriptions, manage automations) to raise specificity.

Expand the 'Use when' clause with natural trigger phrases users might say, such as 'newsletter subscribers', 'Beehiiv posts', or 'publication tiers'.

Dimension	Reasoning	Score
Specificity	The description names the domain (Beehiiv) and one to two concrete actions ('Manage Users, Publications'), but the actions are minimal and not comprehensive, matching the score-3 anchor.	3 / 5
Completeness	It states both what it does ('Beehiiv integration. Manage Users, Publications.') and when to use it ('Use when the user wants to interact with Beehiiv data.'), but the 'when' could be more specific, matching the score-4 anchor.	4 / 5
Trigger Term Quality	'interact with Beehiiv data' is a relevant natural phrase, but the description misses common variations, synonyms, or related trigger terms, fitting the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	The Beehiiv niche is clear and specific with a distinct trigger, leaving minimal conflict risk with other skills, matching the score-5 anchor.	5 / 5
	Total	15 / 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/beehiiv/SKILL.md
Commit: f484c82

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