Name: heyzine
Rating: 55.2 (1 reviews)
Author: membranedev

heyzine

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

Quality

62%

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/heyzine/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 well-structured, actionable Membrane CLI guide with concrete commands and clear connection-state checkpoints. Its main weaknesses are minor verbosity in the intro and best-practices prose, and the absence of progressive disclosure into reference files for the denser detail blocks.

Suggestions

Trim the marketing intro and editorializing ('so you can focus on the integration logic...') to reduce token spend.

Move the proxy flag table and the clientAction state detail into a reference file referenced one level deep, keeping SKILL.md an overview.

Resolve the dangling 'Step 2' reference by explicitly labeling the searching/running actions step.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete CLI commands, but includes unnecessary padding such as the marketing intro ('used by marketers, educators, and businesses...'), 'so you can focus on the integration logic rather than auth plumbing', and 'This is the fastest way to get a connection'; fits 'Mostly efficient but includes some unnecessary explanation or could be tightened'; not a 4 because several sentences could be trimmed.	3 / 5
Actionability	It provides concrete, executable commands (membrane login, connection ensure, action run, request) plus a flag table, covering common cases; minor gaps remain (CONNECTION_ID placeholders, some described-not-commanded steps), fitting 'Mostly executable guidance; concrete code or commands with minor gaps'; not a 5 because not every common case is copy-paste ready.	4 / 5
Workflow Clarity	The install -> authenticate -> connect -> wait-for-ready -> search -> run sequence is clear with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop; fits 'Clear sequence with most checkpoints present; minor validation gaps' — the dangling 'Step 2' reference and unlabeled steps keep it from a 5.	4 / 5
Progressive Disclosure	The body is well-organized into clear sections with no nested references and no bundle files to navigate; however the proxy flag table and clientAction detail block are inlined content that could live in separate reference files, fitting 'Good structure; most content appropriately placed; minor organization gaps'; not a 5 because there is no one-level-deep reference split.	4 / 5
	Total	15 / 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 uses third person and covers both what and when, but its actions are generic and it omits the Heyzine-specific terms (flipbooks, PDFs, hotspots) that users would naturally say. It is competent but leaves distinctiveness and trigger coverage underdeveloped.

Suggestions

Replace generic verbs with concrete Heyzine capabilities, e.g. 'Convert PDFs into interactive flipbooks, manage hotspots, and view publication statistics.'

Add natural trigger terms users would say, such as 'flipbooks', 'PDFs', 'magazines', 'catalogs', or 'brochures'.

Tighten the 'Use when' clause to specific intents, e.g. 'Use when the user wants to create or manage Heyzine flipbooks, hotspots, or publication statistics.'

Dimension	Reasoning	Score
Specificity	It names the Heyzine domain but the actions ('Manage data, records, and automate workflows') are generic verbs rather than concrete capabilities like flipbook creation, PDF conversion, or hotspot editing; matches the anchor 'Names the domain but actions are minimal or generic' rather than the 3-anchor which requires concrete actions.	2 / 5
Completeness	Both 'what' ('Heyzine integration. Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Heyzine data') are present, but the trigger phrase is generic rather than concrete, matching 'Has both what and when; when could be more explicit or specific'; not a 5 because the when lacks concrete trigger phrases.	4 / 5
Trigger Term Quality	'Heyzine' and 'data, records' are relevant keywords, but it misses the natural terms users would actually say (flipbooks, PDFs, magazines, catalogs, hotspots), fitting 'Some relevant keywords but missing common variations or synonyms'; not a 4 because keyword coverage is thin.	3 / 5
Distinctiveness Conflict Risk	Naming the specific Heyzine app gives it a clear niche with minimal conflict risk, but 'interact with Heyzine data' and 'manage data, records' are broad enough to overlap slightly with general data skills, fitting 'Mostly distinct; minor overlap risk'; not a 5 because the triggers are not sharply distinctive.	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/heyzine/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.