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

wbiztool

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

Quality

69%

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

Quality

Content

72%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 CLI commands and a reasonable connection-readiness workflow, but it is a single monolithic file with no progressive disclosure and lacks validation safeguards around destructive proxy operations.

Suggestions

Add an explicit validation/confirmation checkpoint before destructive or batch proxy requests (e.g. '-X DELETE'), such as confirming the target or doing a dry-run GET first.

Move the detailed clientAction state spec and the proxy flags table into a separate reference file (e.g. REFERENCE.md) and link to it from SKILL.md to improve progressive disclosure.

Fix the dangling 'Step 2' reference or relabel the sections so the skip-to navigation is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is largely command-driven with a compact flags table and minimal prose, though a few marketing-style lines ('focus on the integration logic rather than auth plumbing') and the introductory product blurb could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready CLI commands for install, login, connection, action discovery, action execution, and proxying, plus a flags table covering the common cases.	5 / 5
Workflow Clarity	There is a clear install→authenticate→connect→poll→search→run sequence with state checkpoints, but the proxy path permits destructive methods (-X DELETE) with no validation/verification step before acting, capping this dimension.	3 / 5
Progressive Disclosure	The skill is over 50 lines with all content inlined in SKILL.md and no bundle references; material that could live in separate files (the clientAction spec, the proxy flags table) is inline, though section headers provide some structure.	3 / 5
	Total	15 / 20 Passed

Description

66%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 product-specific and includes both a capability statement and an explicit 'Use when' trigger, making it distinct and reasonably complete. Its main weakness is generic action verbs and limited trigger-term variation.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Wbiztool capabilities such as creating invoices, managing customers, or tracking work orders.

Broaden the trigger with natural synonyms, e.g. 'Use when the user wants to interact with Wbiztool data, such as invoices, customers, projects, or work orders.'

Dimension	Reasoning	Score
Specificity	Names the Wbiztool domain plus a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than comprehensive concrete capabilities.	3 / 5
Completeness	Provides both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' trigger ('Use when the user wants to interact with Wbiztool data'), though the 'when' could be more specific.	4 / 5
Trigger Term Quality	Includes the natural product keyword 'Wbiztool' and the phrase 'interact with Wbiztool data', but lacks synonyms or common variations users might say.	3 / 5
Distinctiveness Conflict Risk	Tied to a named product ('Wbiztool integration') with a product-specific trigger, giving it a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	15 / 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/wbiztool/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.