Name: kickbox
Rating: 55.2 (1 reviews)
Author: membranedev

kickbox

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

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/kickbox/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 concrete, executable Membrane CLI commands and well-structured reference tables, and the connection workflow includes clear state-based checkpoints. The main gap is the absence of validation and polling guidance for batch verification jobs, which limits workflow clarity.

Suggestions

Add a feedback loop for batch verification: after 'create-batch-verification-job', poll 'get-batch-verification-job-status' until completion and surface how to interpret the result.

Trim the marketing opening paragraph and the filler line 'Use action names and parameters as needed.' to improve token efficiency.

Add a brief validation note for 'membrane action run' output (e.g. check the 'output'/'error' fields and retry or report failures) so destructive or batch runs have an explicit checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands, tables, and flag references, with only minor trimmable padding such as the marketing intro and the filler line 'Use action names and parameters as needed.'	4 / 5
Actionability	It provides copy-paste-ready CLI commands for install, login, connection, action search/run, and proxying, plus parameter-passing examples and concrete action/flag tables covering the common cases.	5 / 5
Workflow Clarity	The connect-search-run sequence is clearly laid out with connection-state checkpoints and polling, but batch verification operations are listed without validation or job-polling guidance, capping workflow clarity per the batch-operations rule.	3 / 5
Progressive Disclosure	The single file is well-organized with clear section headers and no nested references; the inlined action and proxy-flag tables are appropriate for a single-app CLI skill, though the file is over 50 lines with no external reference split.	4 / 5
	Total	16 / 20 Passed

Description

48%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 has an explicit activation trigger and names a distinct service, but its capability statement relies on generic verbs ('manage data, records, automate workflows') instead of concrete Kickbox actions. Adding specific trigger phrases and a sharper 'what' would materially improve it.

Suggestions

Replace generic verbs with concrete Kickbox actions, e.g. 'Verify email addresses, check disposable domains, run batch verification jobs, and retrieve credit balances.'

Add natural user trigger terms such as 'email verification', 'clean email list', 'bounce rate', or 'disposable email' to the 'Use when...' clause.

Tighten the 'what' so it reads as a capability list rather than 'Kickbox integration. Manage data, records, and automate workflows.'

Dimension	Reasoning	Score
Specificity	The description names the Kickbox domain but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete Kickbox capabilities like email verification or batch jobs.	2 / 5
Completeness	An explicit 'Use when the user wants to interact with Kickbox data' trigger is present, but the 'what' ('Kickbox integration. Manage data, records, and automate workflows') is vague, leaving the capability statement weak.	3 / 5
Trigger Term Quality	It includes the brand term 'Kickbox' and 'interact with Kickbox data', but misses the natural phrases a user would actually say such as 'verify emails', 'email list', 'bounce rate', or 'disposable email'.	3 / 5
Distinctiveness Conflict Risk	Naming the specific Kickbox service gives it a clear niche with low conflict risk, though the generic 'interact with Kickbox data' trigger leaves minor overlap with other data-integration skills.	4 / 5
	Total	12 / 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/kickbox/SKILL.md
Commit: f484c82

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