Name: beeple
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

beeple

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

Quality

72%

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

Quality

Content

82%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, packed with executable Membrane CLI commands and a well-structured connection workflow with validation checkpoints. Its only real weaknesses are minor prose padding and the lack of any progressive disclosure into reference files for the longer reference-style sections.

Suggestions

Define 'Step 2' explicitly (e.g. label the action-search/run sections as numbered steps) so the 'skip to Step 2' references resolve.

Trim explanatory filler like 'so you can focus on the integration logic rather than auth plumbing' and the introductory Beeple marketing sentence.

Move the proxy-flag options table and the full clientAction state reference into a separate REFERENCE.md linked one level deep to reduce inline bulk.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean operational guidance with copy-paste commands, but includes minor over-explanation such as 'so you can focus on the integration logic rather than auth plumbing' and the introductory 'Beeple is a tool used by digital artists...' that could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request proxy) with concrete flags and JSON examples covering the common cases.	5 / 5
Workflow Clarity	The connect-and-poll flow has clear state-based checkpoints and a feedback loop (re-poll after CLIENT_ACTION_REQUIRED), but references to 'Step 2' are never explicitly defined and the overall sequence is section-based rather than a strictly numbered workflow.	4 / 5
Progressive Disclosure	The single SKILL.md is well organized into clear sections with no nested references, but at ~137 lines with no bundle files, bulk such as the proxy-flag table and detailed state handling is inlined rather than split into one-level-deep reference files.	4 / 5
	Total	17 / 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 is functional, naming the Beeple domain and providing a 'Use when' clause, so it clears the completeness bar. Its main weakness is generic action verbs and thin trigger-term coverage that keep specificity and trigger quality at the midpoint.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Manage Beeple shifts, participants, and documents, and automate workforce workflows.'

Expand the trigger clause with natural variations users might say, e.g. 'Use when the user wants to query Beeple shifts, manage participants, or automate scheduling workflows.'

Add file/record terms users reference (e.g. 'Beeple records, shift data, documents') to strengthen distinctiveness and trigger quality.

Dimension	Reasoning	Score
Specificity	Names the Beeple domain with a couple of actions ('Manage data, records, and automate workflows'), but the verbs are generic ('manage') and coverage is not comprehensive, fitting the 3 anchor better than 4.	3 / 5
Completeness	It states both what ('Beeple integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Beeple data'), but the 'when' clause is somewhat generic, fitting the 4 anchor rather than the fully explicit 5.	4 / 5
Trigger Term Quality	The natural trigger term 'Beeple' / 'Beeple data' is present, but only one phrasing is given with no synonyms or variations, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The named product 'Beeple' gives it a clear niche with minimal conflict risk, but the generic 'interact with Beeple data' phrasing leaves minor overlap risk versus a more trigger-rich 5.	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/beeple/SKILL.md
Commit: f484c82

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