Name: zuora-billing
Rating: 63.2 (1 reviews)
Author: membranedev

zuora-billing

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

Quality

75%

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

Quality

Content

88%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, highly actionable CLI integration guide with executable commands and a clear state-driven workflow including validation feedback loops. It is slightly held back by minor over-explanation and a long inlined object list that could live in a reference file.

Suggestions

Move the 30-item 'Zuora Billing Overview' object list into a separate reference file and link to it from the overview, reducing inlined reference bulk.

Trim minor asides like 'This is the fastest way to get a connection' and the normalize-and-match detail that do not change the executable steps.

Add a short top-of-file summary of the end-to-end flow (install → auth → connect → discover → run) so the sequence is visible before the detailed sections.

Dimension	Reasoning	Score
Conciseness	The body is efficient and command-driven with little padding; only minor asides ('This is the fastest way to get a connection', the normalize-and-match explanation) could be trimmed, matching the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	Copy-paste-ready commands throughout (login, connection ensure, action list/run with --input JSON, request proxy) plus a flag table cover the common cases fully and executably, matching the top anchor.	5 / 5
Workflow Clarity	A clearly sequenced flow (install → login → connect → poll READY → search → run) with an explicit state-machine and CLIENT_ACTION_REQUIRED feedback loop that re-polls after the user acts, providing explicit validation checkpoints and error recovery.	5 / 5
Progressive Disclosure	A single well-organized file with clear section headers and no nested references; structure is good but some dense reference material (the long object list, full flag/options tables) is inlined rather than split off.	4 / 5
	Total	18 / 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 is a solid third-person statement with an explicit 'Use when' trigger and a distinctive product name, satisfying both the what and when. Its main weakness is generic action verbs ('manage data/records') rather than concrete Zuora-specific capabilities.

Suggestions

Replace generic verbs with concrete Zuora Billing capabilities, e.g. 'Create and manage subscriptions, invoices, payments, and credit memos; automate billing workflows.'

Add natural trigger synonyms users would say, such as 'subscriptions', 'invoices', or 'recurring billing'.

Tighten the 'when' clause to name a few representative triggers (e.g. 'Use when the user wants to query Zuora subscriptions, invoices, or payments').

Dimension	Reasoning	Score
Specificity	Names the Zuora Billing domain and 2-3 actions ('Manage data, records, and automate workflows'), but the actions are generic ('manage') rather than concrete, mirroring the 'Processes PDF files and extracts content' anchor.	3 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Zuora Billing data') are present with a concrete trigger phrase, though the 'what' could be more specific.	4 / 5
Trigger Term Quality	'Zuora Billing', 'data', 'records', 'workflows' provide some relevant keywords, but common natural variations/synonyms a user might say (e.g. 'subscriptions', 'invoices', 'billing') are missing, matching the 'Works with PDF files' partial-coverage anchor.	3 / 5
Distinctiveness Conflict Risk	The product-specific 'Zuora Billing' trigger carves a clear niche with minimal conflict risk against other skills, though the generic action verbs leave minor overlap risk with other data-management skills.	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/zuora-billing/SKILL.md
Commit: f484c82

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