Name: beeswax
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

beeswax

Beeswax integration. Manage Organizations. Use when the user wants to interact with Beeswax data.

Quality

74%

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/beeswax/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 body is highly actionable with executable commands and a well-sequenced connection workflow that includes real validation feedback loops; its main weaknesses are minor conversational padding and the lack of result-verification guidance for create/update operations.

Suggestions

Tighten the intro and auth prose by dropping explanatory sentences about what Beeswax/DSPs are and the "so you can focus" framing.

Add a brief verification step after create/update actions (e.g. re-fetch the resource to confirm the change applied) to close the validation gap for destructive operations.

Consider moving the 20-row Popular actions table into a references file linked from the body to improve progressive disclosure and token budget.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven, with only minor over-explanation such as the opening "Beeswax is a programmatic advertising platform..." line and conversational phrasing like "so you can focus on the integration logic rather than auth plumbing" that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands for the full lifecycle (install, login, connection ensure/get with --wait, action list/run with --input, request proxy) plus a flag-option table and a Popular actions table, covering the common cases concretely.	5 / 5
Workflow Clarity	The connect → search → run sequence is clear and the connection setup includes explicit state-based validation with a poll-and-retry feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED), but there is no verification guidance for the destructive create/update actions the skill exposes.	4 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections with no nested or buried references and no external bundle files, though the inline Popular actions and proxy-flag tables are bulky enough that they could live in a separate reference file.	4 / 5
	Total	17 / 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 is well-structured with an explicit Use-when clause and a distinctive product niche, but it undersells the skill: the only named action ("Manage Organizations") is generic and the rich entity vocabulary in the body is absent from the trigger terms.

Suggestions

Replace the generic "Manage Organizations" with the concrete entities the skill exposes, e.g. "Manage campaigns, line items, creatives, and advertisers."

Expand the trigger clause to include natural user phrases such as "campaigns", "line items", "creatives", "audiences", or "Beeswax reporting".

Keep the third-person voice and concise structure, just swap in specific Beeswax nouns for the abstract "interact with Beeswax data."

Dimension	Reasoning	Score
Specificity	The description names the domain ("Beeswax integration") and one concrete action ("Manage Organizations"), but the action is generic and coverage is far from comprehensive given the many entities the skill actually exposes.	3 / 5
Completeness	Both "what" ("Beeswax integration. Manage Organizations.") and "when" ("Use when the user wants to interact with Beeswax data.") are present, but the trigger is generic rather than packed with concrete phrases, so it stops short of a 5.	4 / 5
Trigger Term Quality	It includes relevant keywords ("Beeswax", "Beeswax data", "Organizations") via an explicit trigger clause, but misses the natural variations a user would say (campaigns, line items, creatives, advertisers, targeting, reporting) that the body actually supports.	3 / 5
Distinctiveness Conflict Risk	Beeswax is a specific named product (a programmatic ad DSP), giving the skill a clear niche with a distinctive trigger term and minimal risk of overlapping with unrelated 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/beeswax/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.