Name: bilionis
Rating: 60 (1 reviews)
Author: membranedev

bilionis

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

Quality

70%

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/bilionis/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 content is highly actionable with concrete, executable Membrane CLI commands and a well-sequenced workflow, but it is marred by a stray LLM-refusal paragraph at the top and lacks explicit validation checkpoints between connection and action execution.

Suggestions

Remove the opening 'I don't have enough information to do that...' paragraph, which is irrelevant noise that wastes tokens.

Add a validation checkpoint after connecting (e.g. confirm the connection appears in `membrane connection list`) before running actions.

Consider moving the full actions table and proxy flag reference into a separate reference file, keeping SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and tables, but it opens with a stray LLM-refusal paragraph ('I don't have enough information to do that...') that is pure noise, fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connect, action list/run, request proxy) plus a table of named actions with keys and input guidance, matching 'fully executable; copy-paste ready; covers common cases'.	5 / 5
Workflow Clarity	Steps are clearly sequenced (install → login → connect → search actions → run → proxy) with a discover-before-build practice, but there are no explicit validation checkpoints for confirming connection or action success, matching 'clear sequence with minor validation gaps'.	4 / 5
Progressive Disclosure	The single file is well-organized with clear section headers and no nested references, and no bundle files exist to split out; it sits just below the ideal 'clear overview with well-signaled references' because the actions table and proxy details are all inlined rather than pointed to dedicated references.	4 / 5
	Total	16 / 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 correctly includes both a what and an explicit when clause anchored to a distinctive app name, giving it strong distinctiveness. Its weakness is generic, non-concrete action language that omits the message/lead vocabulary users would actually say.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete operations like 'search and retrieve Bilionis messages/leads by city, email, ID, or date range'.

Add natural trigger phrases such as 'leads', 'messages', or 'Bilionis contacts' so the description matches what users actually ask for.

Tighten the when-clause to reference specific intents, e.g. 'Use when the user wants to search or look up Bilionis messages and leads'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Bilionis integration') and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than the concrete message/lead operations the skill actually performs, matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor.	3 / 5
Completeness	It answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Bilionis data') with an explicit Use-when clause, but the 'what' is vague and the 'when' could name concrete triggers, matching the 'both present, when could be more specific' anchor.	4 / 5
Trigger Term Quality	The distinctive term 'Bilionis' and the phrase 'interact with Bilionis data' provide some natural triggers, but the common user phrases the body actually serves (search leads, find messages by email/city) are missing, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the named app 'Bilionis' creates a clear niche with a distinctive trigger and minimal conflict risk with 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/bilionis/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.