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

commbox

CommBox integration. Manage data, records, and automate workflows. Use when the user wants to interact with CommBox 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/commbox/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 a well-structured, command-driven guide with strong actionability and a clear connection workflow including state-based feedback. Main weaknesses are redundant sections, broken step numbering, and an empty 'Popular actions' heading.

Suggestions

Fix the step numbering: define 'Step 1'/'Step 2' headers explicitly or reword the 'skip to Step 2' and '1b' references to point at real sections.

Make 'Popular actions' actually list the common CommBox actions (e.g. send message, list conversations, search tickets) instead of repeating the discovery command.

Add a brief validation/check step after running actions or proxy requests (e.g. inspect the `output` field or HTTP status) to close the workflow validation gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-driven prose, but the action-list command appears twice (in 'Searching for actions' and 'Popular actions') and the intro paragraph lightly over-explains, keeping it at anchor 4 rather than a lean 5.	4 / 5
Actionability	Concrete, copy-paste-ready commands cover install, login, connection, action search/run, and proxy with a flags table, but the 'Popular actions' heading only repeats a discovery command instead of listing actual actions, a minor gap that caps it at 4.	4 / 5
Workflow Clarity	The install→authenticate→connect→poll→search→run sequence is clear and includes a polling feedback loop with explicit state handling (READY, BUILDING, CLIENT_ACTION_REQUIRED), but broken step labels ('Step 2' never defined, '1b' with no '1a') and no validation for executed actions keep it from 5.	4 / 5
Progressive Disclosure	It is a single self-contained file with well-organized headers and no nested references, which is appropriate given there are no bundle files, but the redundancy between 'Searching for actions' and 'Popular actions' is a minor organization gap that prevents a 5.	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 is third-person, names the domain, and includes an explicit 'Use when' trigger, giving it solid completeness and distinctiveness. Its weakness is generic action verbs and thin trigger-term coverage.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete CommBox-specific actions like 'send and receive messages, search conversations, manage contacts, automate ticket workflows'.

Broaden the trigger phrase with natural user phrasings, e.g. 'Use when the user wants to send or read CommBox messages, search conversations, or automate customer-support workflows'.

Dimension	Reasoning	Score
Specificity	Names the CommBox domain plus two-to-three actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete like 'extract text' or 'fill forms', so it sits at anchor 3 and not 4.	3 / 5
Completeness	It states what the skill does ('Manage data, records, and automate workflows') and gives an explicit 'Use when the user wants to interact with CommBox data' trigger, but the 'when' is only moderately specific, so it is anchor 4 not 5.	4 / 5
Trigger Term Quality	The natural keywords are essentially limited to 'CommBox' and 'CommBox data'; relevant but missing common variations or synonyms, matching anchor 3 rather than the broader coverage of 4.	3 / 5
Distinctiveness Conflict Risk	The product-specific 'CommBox' name and 'interact with CommBox data' trigger give it a clear niche with minor overlap risk, though the generic action verbs keep it from a 5.	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/commbox/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.