Name: beekeeper
Rating: 60.8 (1 reviews)
Author: membranedev

beekeeper

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

Quality

71%

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

Quality

Content

76%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 executable commands and a well-validated connection workflow, but it lacks a validation checkpoint for destructive actions and inlines a sizable actions table that could be split into a reference file.

Suggestions

Add an explicit validation/checkpoint step before destructive actions (e.g. confirm the target ID and use --json dry-run or confirm with the user before running delete-user/delete-post) so the workflow can score higher.

Consider moving the 20-row 'Popular actions' table into a references/ file (e.g. ACTIONS.md) and linking to it from a short summary inline, improving progressive disclosure.

Trim minor filler phrases ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and tables, but contains minor padding such as 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection' that could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request proxy) plus a parameterized JSON-input example, covering the common cases executably.	5 / 5
Workflow Clarity	The connection workflow is well-sequenced with state-based validation (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR and re-polling), but the skill surfaces destructive actions (delete-post, delete-user) with no validation checkpoint before running them, capping this dimension at 3.	3 / 5
Progressive Disclosure	Clear section structure with headers and tables makes navigation easy, and there are no bundle files to reference; the large inlined 20-row 'Popular actions' table is borderline API-reference material that could live in a separate file but is reasonable as a quick-reference.	4 / 5
	Total	16 / 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 covers both what and when and is clearly tied to a distinct named platform, but its capability verbs are generic and it omits the natural trigger terms (messages, posts, users) that frontline-worker Beekeeper users would actually invoke.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Beekeeper actions such as 'Send messages, create and moderate posts, manage users and groups'.

Expand the trigger clause with natural phrases users would say, e.g. 'Use when the user wants to send Beekeeper messages, manage posts, or list/manage users and groups'.

Keep the third-person voice but make the 'when' clause enumerate 2-3 concrete scenarios rather than the abstract 'interact with Beekeeper data'.

Dimension	Reasoning	Score
Specificity	Names the Beekeeper domain plus a few actions ('Manage data, records, and automate workflows') but the verbs are generic ('manage', 'automate') rather than concrete Beekeeper actions like send messages or create posts, so not comprehensive.	3 / 5
Completeness	Explicitly states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Beekeeper data'), but the 'when' clause is generic rather than listing concrete trigger scenarios.	4 / 5
Trigger Term Quality	Includes the core keyword 'Beekeeper' and a trigger phrase ('interact with Beekeeper data'), but misses the natural terms users would actually say such as messages, posts, chats, or users.	3 / 5
Distinctiveness Conflict Risk	Names a specific named platform (Beekeeper) with a clear niche and product-specific trigger, giving it minimal conflict risk with other skills.	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/beekeeper/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.