Name: boxhero
Rating: 56.8 (1 reviews)
Author: membranedev

boxhero

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

Quality

65%

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

Quality

Content

68%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, copy-paste CLI commands and a strong connection-state workflow. Weaknesses are the padded "No description" actions table, the absence of validation guidance for destructive create/update operations, and inline reference content that could be split out.

Suggestions

Move the Popular actions table into a separate reference file (or drop the empty "No description" column) to reclaim tokens and improve progressive disclosure.

Add a validation/verification checkpoint for destructive actions, e.g. confirm a record exists or re-fetch it after create/update before reporting success.

Trim definitional padding such as "BoxHero is inventory management software used by small to medium-sized businesses" since Claude can infer the domain from the docs link.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the 20-row "Popular actions" table where every description reads "No description" is low-value token spend, and lines explaining what BoxHero/Membrane is add minor padding.	3 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login incl. headless, connection ensure, polling, action list/run, proxy with a full flag table), fully executable with concrete examples.	5 / 5
Workflow Clarity	The connection-readiness flow is well sequenced with a state machine and polling checkpoints, but the skill exposes create/update/transaction operations (destructive/batch) with no validation or verification guidance, which caps workflow clarity per the rubric.	3 / 5
Progressive Disclosure	Sections are clearly organized (Overview, Install, Auth, Connecting, Searching, Actions, Proxy, Best practices) and the skill is sensibly self-contained, though the bulk actions table is inline reference content that could live in a separate file.	4 / 5
	Total	15 / 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 correctly names the target product and includes an explicit Use-when clause, satisfying the what/when requirement in third-person voice. Its main weakness is generic action language and thin natural trigger terms that omit inventory-specific vocabulary.

Suggestions

Replace generic verbs with concrete BoxHero operations, e.g. "Track stock levels, manage purchase and sales orders, and update inventory records."

Add natural trigger terms users actually say, such as "inventory", "stock", "orders", or "BoxHero" transactions.

Tighten the when-clause to reference concrete scenarios, e.g. "Use when the user wants to query or update BoxHero inventory, orders, or stock movements."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the BoxHero domain with a few actions, but the actions are generic rather than concrete inventory operations, matching the anchor that lists 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with BoxHero data"), but the what is generic, matching the anchor where both are present yet the when could be more specific.	4 / 5
Trigger Term Quality	It surfaces "BoxHero" and "BoxHero data" as relevant keywords but omits the natural terms users would say (inventory, stock, orders), fitting the anchor with some relevant keywords missing common synonyms.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product BoxHero gives it a clear niche with minimal conflict risk, though the generic "manage data, records, automate workflows" phrasing leaves minor overlap with adjacent integration skills.	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/boxhero/SKILL.md
Commit: f484c82

Reviewed: 3 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.