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

billsby

Billsby integration. Manage data, records, and automate workflows. Use when the user wants to interact with Billsby 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

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/billsby/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 delivers highly actionable, copy-paste-ready Membrane commands and a clear connection workflow, but it pads the opening with business context Claude already infers and omits validation checkpoints before destructive operations like deleting customers or canceling subscriptions. It is a strong, well-structured skill that would benefit from trimming fluff and adding verify-before-destructive-action steps.

Suggestions

Add an explicit validation/verification step before destructive actions: e.g. before running delete-customer or cancel-subscription, fetch and confirm the target with the user, then re-fetch to verify the resulting state.

Trim the opening overview paragraph ("Billsby is a subscription billing platform... used by businesses of all sizes...") to a one-line context statement; Claude does not need the business primer.

Consider moving the popular-actions catalog and proxy flag reference into a separate references file so SKILL.md stays a lean overview with one-level-deep navigation.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening business-context paragraph ("Billsby is a subscription billing platform... used by businesses of all sizes...") and some redundant connection-state prose pad what Claude does not need, matching the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	Copy-paste-ready membrane commands (install, login, connection ensure, action list/run, request) plus a concrete popular-actions table and proxy flag reference fully cover the common integration cases, matching the fully-executable anchor.	5 / 5
Workflow Clarity	The install-authenticate-connect-poll-search-run sequence is clear with state-based decision guidance, but destructive/batch actions (delete-customer, cancel-subscription, list operations) lack any validation or verify-before-proceeding checkpoint, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	The skill is well organized with clear section headers and navigable structure; no bundle files exist so everything is inline, and the popular-actions and proxy-option tables could arguably live in separate reference files, giving minor organization gaps rather than the ideal one-level-deep reference split.	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 clearly identifies the Billsby domain and includes an explicit Use-when clause, but its action language and trigger phrasing are generic rather than naming concrete capabilities or natural entity keywords. It is solid but could be sharpened with specific triggers like subscriptions, invoices, and customers.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Billsby actions such as "create customers, manage subscriptions, list invoices, and apply one-time charges."

Expand the trigger clause to mention natural user phrases and entities, e.g. "Use when the user wants to manage Billsby subscriptions, customers, invoices, or billing."

Add common synonym/extension terms (subscriptions, plans, coupons, addons) so the trigger matches varied user phrasings.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Billsby domain plus a couple of actions, but the actions are generic rather than concrete capabilities like creating customers or listing invoices, fitting the 1-2 concrete-actions anchor.	3 / 5
Completeness	It states a clear "what" ("Billsby integration. Manage data, records, and automate workflows.") and an explicit "Use when the user wants to interact with Billsby data." clause, but the trigger phrasing is generic rather than concrete, fitting the both-present-but-when-could-be-more-specific anchor.	4 / 5
Trigger Term Quality	"Billsby" and "interact with Billsby data" provide a relevant domain keyword and one natural trigger phrase, but common entity synonyms a user would say (subscriptions, invoices, billing) are missing, matching the some-keywords anchor.	3 / 5
Distinctiveness Conflict Risk	The named brand "Billsby" makes it clearly distinguishable from other skills, though the surrounding generic action and trigger language leaves minor overlap risk, matching the mostly-distinct 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/billsby/SKILL.md
Commit: f484c82

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