Name: bexio
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

bexio

Bexio integration. Manage Organizations, Users. Use when the user wants to interact with Bexio data.

Quality

65%

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

Quality

Content

68%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 executable CLI commands and a useful actions table, and is well structured for navigation. Its main gaps are an unnecessary intro/background paragraph and a lack of explicit validation checkpoints before destructive action runs or proxy mutations.

Suggestions

Trim the opening background paragraph ('Bexio is a business management software...') and the auth-plumbing filler; Claude does not need Bexio's company background to use the skill.

Add an explicit validation/confirmation checkpoint before destructive operations, e.g. 'Before running create/update/delete actions or proxy mutations, confirm the target ID and dry-run a list/get first.'

Consider moving the popular-actions table and proxy flag reference into a one-level-deep reference file (e.g. ACTIONS.md) and linking from the body to reach a cleaner progressive-disclosure structure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and tables, but opens with a background paragraph on what Bexio is ('business management software designed for small businesses, particularly in Switzerland...') and includes light filler ('so you can focus on the integration logic rather than auth plumbing'), fitting the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	It provides copy-paste-ready commands for every stage (install, login, connection ensure/get with --wait, action list/run, request proxy) plus a full popular-actions table and a concrete JSON-input example, matching the 'fully executable; copy-paste ready; covers common cases' anchor.	5 / 5
Workflow Clarity	The connection flow is well branched on state (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with polling loops, but the action-running and proxy paths allow destructive operations (update-contact, create-*, and proxy DELETE/PUT) with no pre-validation or verification checkpoint, so the destructive/batch cap holds it at 3.	3 / 5
Progressive Disclosure	No bundle files exist, so everything is inline in a single file with clear, well-ordered sections; structure is good and navigation is easy, but the large popular-actions table and proxy-option table are inlined rather than split into one-level-deep reference files, leaving it just short of the score 5 anchor.	4 / 5
	Total	15 / 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 successfully pairs a 'what' with an explicit 'Use when...' trigger and leverages a distinct named product for low conflict risk. Its weaknesses are generic action verbs ('Manage') and a thin, single-keyword trigger clause that lacks concrete synonyms or phrases.

Suggestions

Replace the generic 'Manage Organizations, Users' with concrete verbs and broader coverage, e.g. 'Create and update contacts, invoices, orders, projects, and timesheets in Bexio.'

Expand the trigger clause with concrete natural phrases, e.g. 'Use when the user wants to manage Bexio contacts, invoices, orders, quotes, projects, or timesheets.'

Add the file/record terms users actually say (contacts, invoices, deals, quotes) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Bexio) and a couple of concrete entities ('Manage Organizations, Users'), but 'Manage' is a generic verb and coverage is far from comprehensive, matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor rather than the more action-rich score 4.	3 / 5
Completeness	It states both what ('Bexio integration. Manage Organizations, Users.') and when ('Use when the user wants to interact with Bexio data'), but the 'when' clause is generic rather than listing concrete trigger phrases, so it stops short of the score 5 anchor.	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with Bexio data' surfaces the core keyword 'Bexio', but offers only that single term with no natural synonyms or variations, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Bexio is a specific named SaaS product, giving it a clear niche with minimal conflict risk, though the generic 'interact with Bexio data' phrasing leaves minor overlap risk with adjacent Bexio-related skills rather than the fully distinct score 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/bexio/SKILL.md
Commit: f484c82

Reviewed: ~3 hours 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.