Name: belco-bv
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

belco-bv

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

Quality

63%

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

Quality

Content

61%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 a solid, command-heavy integration guide with strong actionability and good structure, weakened by a stray non-actionable line, a redundant 'Popular actions' section, and a lack of validation/verification checkpoints before running actions against external data.

Suggestions

Delete the stray line 'I don't have enough information about that app to do that. I'm sorry.' and the vague 'Use action names and parameters as needed.' — neither is actionable.

Merge the 'Popular actions' section into 'Searching for actions' to remove the duplicated action-list command and reduce token cost.

Add a verification checkpoint for action runs, e.g. before executing a write/update action, query the target record first and confirm intent; after running, re-query to verify the expected result.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and lean, but includes padding: a stray non-actionable sentence ('I don't have enough information about that app to do that. I'm sorry.'), the vague line 'Use action names and parameters as needed.', and a 'Popular actions' section that duplicates the action-list command.	3 / 5
Actionability	Concrete executable commands appear throughout (install, login, connection ensure, action run, proxy flags table), giving mostly copy-paste-ready guidance with only minor gaps like required placeholder substitution (CONNECTION_ID, actionId).	4 / 5
Workflow Clarity	The connect sub-flow has explicit state branching (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) with a re-poll feedback loop, but running actions against external data lacks validation/verification checkpoints, so per the destructive/batch cap workflow_clarity cannot exceed 3.	3 / 5
Progressive Disclosure	The single SKILL.md uses clear section headers with content appropriately placed inline; with no static reference files (actions are discovered at runtime via the CLI) the structure is well-organized, though there are no one-level-deep references to elevate it to 5.	4 / 5
	Total	14 / 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 covers what and when with a clear, distinct app-name trigger, but the action vocabulary is generic ('manage data, automate workflows') rather than concrete, capping specificity and trigger-term richness. It is competent but could name the actual capabilities (orders, customers, products) shown in the body.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with the concrete entities/actions the body lists, e.g. 'Query and update orders, customers, and products, and automate Belco B.V. workflows'.

Expand the trigger clause with natural synonyms, e.g. 'Use when the user wants to interact with Belco B.V. data, such as orders, customers, or products, or automate Belco workflows'.

Dimension	Reasoning	Score
Specificity	It names the domain ('Belco B.V.') and a few actions ('Manage data, records, and automate workflows'), but those actions are generic rather than several specific concrete actions, matching the 'domain + 1-2 concrete actions' anchor.	3 / 5
Completeness	It states both the 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Belco B.V. data'), though the 'when' could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	The trigger phrase 'Use when the user wants to interact with Belco B.V. data' surfaces the natural app name but lacks common variations or synonyms, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The proper-noun trigger 'Belco B.V.' carves out a clear niche with minimal overlap risk against other skills, matching the 'clear niche with distinct triggers' anchor.	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/belco-bv/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.