Name: craftboxx
Rating: 59.2 (1 reviews)
Author: membranedev

craftboxx

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

Quality

68%

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

Quality

Content

75%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 an efficient, executable guide to the Craftboxx/Membrane integration with a clear connection workflow and state feedback, hampered only by minor intro fluff and inconsistent step numbering.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight command examples and a flag table, with only minor over-explanation in the intro paragraph ("Think of it as a central hub for all things related to creative projects"), fitting the 4-anchor's "minor instances of over-explanation that could be trimmed."	4 / 5
Actionability	It provides copy-paste-ready commands for install, auth, connection, action search/run, and proxying with a clear flag table, but commands require placeholder substitution (CONNECTION_ID, <actionId>) and a few cases are thin, matching the 4-anchor.	4 / 5
Workflow Clarity	There is a clear sequence (install → auth → connect → poll for READY → search → run) with a state-based feedback loop (BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but step numbering is inconsistent ("skip to Step 2" with no Step 1/2 labels), so it is a 4 rather than 5.	4 / 5
Progressive Disclosure	The content is well-organized into clearly headed sections with no external bundle files; since the inline flag table and clientAction details are reasonably placed and no nested references exist, it sits at the 4-anchor rather than the reference-driven 5-anchor.	4 / 5
	Total	16 / 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 pairs a what-claim with an explicit Use-when trigger and leverages a distinct app name, but its action list is generic and its trigger vocabulary is narrow.

Suggestions

Replace generic verbs with concrete Craftboxx actions, e.g. "Create and track projects and tasks, manage materials and suppliers, and pull invoices" instead of "Manage data, records, and automate workflows."

Broaden the trigger with natural phrases a user would say, e.g. "Use when the user wants to manage Craftboxx projects, tasks, materials, suppliers, or invoices."

Optionally add the app's core entity keywords (projects, tasks, invoices) to improve trigger matching against user requests.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Craftboxx integration") and a few actions ("Manage data, records, and automate workflows"), but the verbs ("Manage") and objects ("data, records") are generic rather than the crisp concrete actions the 4-anchor requires.	3 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Craftboxx data"), but the trigger clause is thinner and less varied than the 5-anchor's concrete multi-phrase triggers.	4 / 5
Trigger Term Quality	The only natural keyword is "Craftboxx" (in "Craftboxx integration" and "interact with Craftboxx data"); it lacks synonyms or common variations a user might say, matching the 3-anchor's "some relevant keywords but missing common variations."	3 / 5
Distinctiveness Conflict Risk	The named app "Craftboxx" gives it a clear niche with low conflict risk, but the generic "data, records, workflows" actions keep minor overlap risk with other data-management skills, fitting the 4-anchor.	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/craftboxx/SKILL.md
Commit: f484c82

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