Name: api-void
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

api-void

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

Quality

64%

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

Quality

Content

71%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 well-structured and highly actionable with concrete executable commands and a clear state-driven connection workflow, but it is fully monolithic with no progressive disclosure to reference files and has minor conciseness and validation-loop gaps.

Suggestions

Move the Popular actions table and proxy flag reference into separate files (e.g. references/actions.md, references/proxy.md) and link to them from SKILL.md to add one-level-deep progressive disclosure.

Add an explicit validate->fix->retry feedback loop for running actions (e.g. how to interpret error output and re-run) to lift workflow clarity.

Fill the empty Description column in the Popular actions table or drop it, and trim explanatory sentences that restate Membrane's value proposition.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable CLI commands and little padding, though some sections restate the obvious (e.g. 'so you can focus on the integration logic rather than auth plumbing') that could be trimmed; matches 'Efficient; minor instances of over-explanation'.	4 / 5
Actionability	Provides concrete, executable membrane commands for install, auth, connection, action search/run, and proxy requests with flag tables; minor gaps such as the Popular actions table having empty Description columns keep it just short of fully copy-paste ready.	4 / 5
Workflow Clarity	Connection setup is sequenced with state-based branches (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling guidance, providing clear checkpoints; it lacks an explicit validate->fix->retry loop for failed action runs, capping it just below 5.	4 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and everything is inlined in SKILL.md; the structure is well-sectioned but content like the proxy flag table and popular actions could live in separate reference files, matching 'Some structure but could be better organized; content that should be separate is inline'.	3 / 5
	Total	15 / 20 Passed

Description

57%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-formed with an explicit 'Use when' trigger and a distinct branded name, but its capability list is generic ('data, records, automate workflows') rather than concrete. It is competent but not comprehensive.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Api Void capabilities such as URL/domain reputation, email verification, DNS lookup, and SSL inspection.

Add natural trigger keywords and synonyms users actually say, e.g. 'reputation check', 'domain age', 'phone validation', so the description surfaces for those requests.

Tighten the 'when' clause to mention specific Api Void use cases rather than only 'interact with Api Void data'.

Dimension	Reasoning	Score
Specificity	Names the domain (Api Void) and 'data, records, automate workflows' but the actions are minimal/generic — no concrete capabilities listed; closest to anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	Has both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Api Void data'), though the 'when' is fairly generic; matches anchor 'Has both what and when; when could be more explicit or specific'.	4 / 5
Trigger Term Quality	Includes 'interact with Api Void data' as a trigger phrase with a 'Use when' clause, but offers only a couple generic keywords and lacks natural synonyms/variations users would say.	3 / 5
Distinctiveness Conflict Risk	The branded 'Api Void' trigger is fairly distinct and unlikely to fire for the wrong skill, though the generic 'data, records, workflows' framing carries minor overlap risk with other integration skills.	4 / 5
	Total	13 / 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/api-void/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.