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

Blog Docs Log in Get started

bizzon

Bizzon integration. Manage data, records, and automate workflows. Use when the user wants to interact with Bizzon 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/bizzon/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 delivers a tight, executable Membrane-based workflow with a strong validation feedback loop for connection setup. Minor weaknesses are a dangling 'Step 2' reference, placeholder operands, and a moderately long single-file layout with no progressive references.

Suggestions

Fix the dangling cross-reference: either label the post-connection section as 'Step 2' or rewrite 'skip to Step 2' as a concrete link to the 'Searching for actions' section.

Add one fully-resolved worked example (e.g. a real connectionId and actionId) so the run/proxy commands are copy-paste complete.

Consider moving the proxy flag table and entity overview into a references file and signaling it from SKILL.md to push progressive disclosure toward 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands and flag tables with only minor over-explanation ('so you can focus on the integration logic rather than auth plumbing'); it respects Claude's competence without padding, fitting the 'efficient, minor trimmable instances' anchor and short of the fully lean 5.	4 / 5
Actionability	It provides concrete, copy-paste-ready commands (install, login, connection ensure/get, action list/run, request) with a full flag table and JSON examples, but some operands remain placeholders (CONNECTION_ID, <actionId>) keeping it just below fully executable 5.	4 / 5
Workflow Clarity	The connect step has an explicit state machine with a poll→act→re-poll feedback loop and error states (CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), but a dangling 'skip to Step 2' reference with no labeled Step 2 and some implicit sequencing hold it below the explicit-checklist 5.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized with clear section headers and no nested references, and no bundle files exist to split out; at ~150 lines it is a touch monolithic but well-structured, matching the 'good structure, minor organization gaps' anchor rather than 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 cleanly covers what and when in third person with a distinctive app-specific niche, but its action list is generic and the trigger term coverage is narrower than the stated scope. Strong on completeness and distinctiveness, weaker on specificity and trigger phrasing.

Suggestions

Replace generic verbs with concrete Bizzon operations (e.g. 'Create and update leads, invoices, and customers; sync product catalogs') to lift specificity toward 5.

Broaden the trigger clause to cover the full scope, e.g. 'Use when the user wants to manage Bizzon leads, customers, invoices, products, or automate sales workflows.'

Add a few natural synonyms users would actually say ('Bizzon CRM', 'Bizzon sales data', 'Bizzon records') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	It names the Bizzon domain plus a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete API-level operations, so it sits at the 'names domain and 1-2 actions, not comprehensive' anchor and below 4.	3 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Bizzon data'); the 'when' is explicit but narrower than the 'what', matching the 'both present, when could be more specific' anchor rather than 5.	4 / 5
Trigger Term Quality	It includes relevant terms ('Bizzon', 'data', 'records', 'workflows', 'interact') and a natural trigger ('Use when the user wants to interact with Bizzon data'), but lacks synonyms or broader natural variations a user might say for the records/workflows half of the scope.	3 / 5
Distinctiveness Conflict Risk	'Bizzon integration' carves a clear app-specific niche with low conflict risk, but the trigger only names 'Bizzon data' so it may not surface for the records/workflows scope, keeping it just below the minimal-conflict 5 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/bizzon/SKILL.md
Commit: f484c82

Reviewed: 8 minutes 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.