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

Blog Docs Log in Get started

billy

Billy integration. Manage data, records, and automate workflows. Use when the user wants to interact with Billy 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/billy/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 is a well-structured, mostly executable guide to driving Billy through the Membrane CLI, with a clear workflow and state-handling feedback loop. Its weaknesses are a stray placeholder sentence, placeholder-laden commands, and slightly inconsistent step numbering.

Suggestions

Remove the placeholder line "I don't have enough information about that app to provide a description." and replace it with a one-line description of Billy.

Normalize the step numbering so referenced labels ("Step 2") match actual headings, or drop the cross-references in favor of linear steps.

Add one worked end-to-end example with representative values (a sample connectionId and actionId) so the run/proxy commands are copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands and a compact flags table, but the placeholder line "I don't have enough information about that app to provide a description." and the "auth plumbing" aside are minor trimmable bits that keep it just below a 5.	4 / 5
Actionability	Concrete, runnable commands cover the common cases (install, login, connection ensure, action list/run, request proxy) with a flags table, but placeholders like CONNECTION_ID and actionId and the lack of a worked example with real values leave minor gaps versus fully copy-paste ready guidance.	4 / 5
Workflow Clarity	There is a clear install -> authenticate -> connect -> poll-for-ready -> search -> run -> proxy sequence with explicit state checkpoints and a poll-again feedback loop for CLIENT_ACTION_REQUIRED, but slightly inconsistent step labeling (a referenced "Step 2" and a "1b" heading) prevents a 5.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no nested references (no bundle files exist), though the inline clientAction state reference and proxy flag table could be split out given the body exceeds 50 lines, leaving a minor organization gap.	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 covers both what the skill does and when to use it, anchored to a named app for decent distinctiveness. Its main weakness is generic action language and thin trigger-term coverage that omit Billy-specific concepts.

Suggestions

Replace generic verbs ("manage data, records, automate workflows") with concrete Billy capabilities such as creating invoices, managing contacts, and syncing accounting records.

Expand the "Use when" clause with natural trigger phrases users would say, e.g. "Use when the user wants to create invoices, manage contacts, or query Billy accounting data."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Billy domain and a few actions, but the actions are generic ("manage data") rather than concrete capabilities like creating invoices or syncing contacts, so it is not comprehensive enough for a 4.	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 Billy data"), but the "when" clause could be more specific with concrete trigger phrases, keeping it just below a 5.	4 / 5
Trigger Term Quality	Trigger terms are limited to "Billy", "Billy data", and "Billy integration"; it misses common natural synonyms a user might say (invoices, accounting, contacts) that map to Billy's actual domains, so it lands at some-relevant-keywords rather than good coverage.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to a named app (Billy) gives it a clear niche with low conflict risk, but the generic action language ("manage data, automate workflows") leaves minor overlap risk with other integration skills, so it does not reach the minimal-conflict 5.	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/billy/SKILL.md
Commit: f484c82

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