Name: flippingbook
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

flippingbook

FlippingBook integration. Manage FlippingBooks, Users, Groups, Brandings. Use when the user wants to interact with FlippingBook data.

Quality

63%

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/flippingbook/SKILL.md

Quality

Content

61%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 concrete Membrane CLI commands and a clear connection state machine, but it loses points for marketing-fluff padding and for lacking validation/confirmation checkpoints around destructive and batch publication operations.

Suggestions

Remove the marketing sentence about who uses FlippingBook ("It's used by marketers, sales teams, and educators...") since it does not aid execution.

Add an explicit validation/confirmation checkpoint before destructive actions (e.g., "Before running delete-publication, confirm the publication id with the user and verify it exists via get-publication").

Include one fully-worked end-to-end example with realistic values (connection → list-publications → get-publication) to close the actionability gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-focused with tight code blocks, but opens with marketing prose ("It's used by marketers, sales teams, and educators to create engaging content like brochures, catalogs, and presentations.") and explanatory padding that could be trimmed, matching the "mostly efficient but includes some unnecessary explanation" anchor.	3 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands for every stage (install, login, connection ensure/get, action list/run, request proxy) plus a Popular actions table, but commands rely on placeholders (CONNECTION_ID, <actionId>, QUERY) with no fully worked end-to-end example, leaving minor gaps short of anchor 5.	4 / 5
Workflow Clarity	The connection flow is well sequenced with a state machine and polling feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED), but the skill covers destructive operations ("Delete Publication") and batch operations ("List Publications") with no validation or confirmation checkpoints, which caps workflow clarity at 3 per the destructive/batch guideline.	3 / 5
Progressive Disclosure	The body is organized into clear, well-signaled sections (Overview, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with content appropriately placed; at ~150 lines with no bundle files it is a single-file skill, and the inline action/flag tables are reasonable though they could optionally be split into reference files.	4 / 5
	Total	14 / 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 cleanly answers both what the skill does and when to use it, anchored on a distinctive product name that avoids conflict risk. Its main weakness is the generic action verb "Manage" and a lack of varied natural trigger terms.

Suggestions

Replace the single verb "Manage" with several concrete actions (e.g., "List, create, update, and delete FlippingBook publications, sources, and tracked links") to lift specificity.

Expand the "Use when..." clause with concrete trigger phrases and synonyms users actually say (e.g., "Use when the user mentions flipbooks, FlippingBook publications, or tracked links").

Dimension	Reasoning	Score
Specificity	"Manage FlippingBooks, Users, Groups, Brandings" names the domain plus several concrete entities, but the single generic verb "Manage" is the only action described — not the multiple distinct verbs that anchor 4 requires.	3 / 5
Completeness	It states both a clear "what" ("FlippingBook integration. Manage FlippingBooks, Users, Groups, Brandings.") and an explicit "when" ("Use when the user wants to interact with FlippingBook data."), but the trigger is generic rather than listing concrete trigger phrases, so it does not reach anchor 5.	4 / 5
Trigger Term Quality	The product name "FlippingBook"/"FlippingBooks" appears repeatedly and is a natural user phrase, but common lowercase variations ("flipbook", "flipbooks") and synonyms are missing, matching the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	"FlippingBook" is a unique product name forming a clear niche with distinct triggers, making accidental activation by unrelated skills highly unlikely — matching the clear-niche/minimal-conflict 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/flippingbook/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.