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

Blog Docs Log in Get started

beebole

Beebole integration. Manage Users, Organizations, Filters. Use when the user wants to interact with Beebole 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/beebole/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 integration guide with explicit connection-state validation checkpoints. It is slightly padded in places and the workflow numbering is inconsistent, but it largely lets Claude execute directly.

Suggestions

Trim non-essential prose such as 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection.'

Reconcile the 'skip to Step 2' reference by labeling the connection steps as a numbered Step 1 / Step 2 sequence.

Add one end-to-end example running a popular action (e.g. list-time-entries) with realistic input and parsed output to close the actionability gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient code and tables, but includes some unnecessary prose ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') and an introductory paragraph that could be tightened.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for every stage (install, login, connection ensure, action list/run, request) plus a popular-actions table with keys, with only minor gaps such as no end-to-end example with realistic input for a specific action.	4 / 5
Workflow Clarity	The connection setup has explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with polling, giving a clear sequence; minor gaps include a 'skip to Step 2' reference with no labeled Step 1/2.	4 / 5
Progressive Disclosure	The single-file body is well-organized with clear section headers and no nested references; the large inline popular-actions table is borderline bulky but reasonable to keep inline given there are no bundle files.	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 answers both what and when and is clearly distinct via the Beebole niche, but it relies on one generic verb and a narrow set of trigger terms. Adding concrete action verbs and natural synonyms (time tracking, timesheet) would raise specificity and trigger quality.

Suggestions

Replace the generic 'Manage' with concrete verbs, e.g. 'Create, list, update, and delete Users, Organizations, and Filters.'

Expand the trigger clause with natural terms users say, e.g. 'Use when the user wants to track time, manage timesheets, or interact with Beebole data.'

Consider mentioning time tracking/timesheets explicitly so the skill surfaces for the most common user phrasing.

Dimension	Reasoning	Score
Specificity	It names the Beebole domain and three resources ('Manage Users, Organizations, Filters'), but the single generic verb 'Manage' covers CRUD without distinguishing concrete actions, so it is not comprehensive.	3 / 5
Completeness	Both 'what' ('Beebole integration. Manage Users, Organizations, Filters.') and 'when' ('Use when the user wants to interact with Beebole data') are present and explicit, though the trigger could list more concrete phrases.	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with Beebole data' surfaces the 'Beebole' keyword, but it misses common natural variations users would say (e.g. 'time tracking', 'timesheet', 'time entry').	3 / 5
Distinctiveness Conflict Risk	'Beebole' is a distinct product niche with a unique trigger term, making overlap with other skills minimal.	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/beebole/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.