Name: quickbooks
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

quickbooks

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

Quality

61%

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/quickbooks/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 body is highly actionable with concrete, runnable Membrane commands and a strong connection-state workflow, but it opens with unnecessary background on what Quickbooks is and omits validation/verification steps for the financial write operations it enables.

Suggestions

Delete or condense the intro paragraph explaining what Quickbooks is; Claude already knows this and it costs tokens for no guidance value.

Add a verification checkpoint after write operations (e.g. re-query the created entity via 'get-invoice'/'get-bill' to confirm it persisted), especially since this skill creates financial records.

Resolve the dangling 'Step 2' reference by either labeling the steps (Step 1 / Step 2) or removing the forward reference so the workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ('Quickbooks is a popular accounting software used by small businesses... Many small business owners and accountants use Quickbooks to keep their books in order') explains a concept Claude already knows, while the rest is efficient, matching the 'mostly efficient but some unnecessary explanation' anchor.	3 / 5
Actionability	Concrete copy-paste commands appear throughout ('npm install -g @membranehq/cli@latest', 'membrane connection ensure', 'membrane action run <actionId> --input ...', 'membrane request CONNECTION_ID /path'), with only minor gaps such as un-enumerated real action ids in run examples.	4 / 5
Workflow Clarity	The connection setup is well-sequenced with polling and state checkpoints (BUILDING/READY/CLIENT_ACTION_REQUIRED), but write operations (create invoice/bill/payment) have no validation or verification step and the referenced 'Step 2' is never shown, leaving sequence gaps that cap this at 3.	3 / 5
Progressive Disclosure	With no bundle files present, the ~180-line body is organized into clear sections (Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices); the 20-row action table is inline but reasonable, matching the 'good structure, minor organization gaps' anchor.	4 / 5
	Total	14 / 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 establishes a Quickbooks niche and answers both 'what' and 'when', but its action verbs and trigger terms are generic and lack the concrete synonyms (invoicing, accounting, books) that would make discovery reliable.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Query, create, and update invoices, customers, bills, and payments in Quickbooks'.

Add natural trigger synonyms users actually say, e.g. 'Use when the user mentions Quickbooks, invoicing, accounting, bookkeeping, or managing financial records'.

Tighten the 'when' clause to reference specific Quickbooks entities (customers, invoices, bills, payments) rather than 'interact with Quickbooks data'.

Dimension	Reasoning	Score
Specificity	Names the Quickbooks domain and a few actions ('Manage accounting data, records, and workflows'), but the verbs are generic ('manage') rather than concrete, matching the anchor for 1-2 domain actions that aren't comprehensive.	3 / 5
Completeness	Both 'what' ('Manage accounting data, records, and workflows') and 'when' ('Use when the user wants to interact with Quickbooks data') are present, but the 'when' clause is generic and could be more specific, matching the anchor for having both with an improvable trigger.	4 / 5
Trigger Term Quality	'interact with Quickbooks data' provides some natural keywords but misses common variations users would say (invoicing, accounting, books, expenses), fitting the anchor where some relevant keywords are present but synonyms are missing.	3 / 5
Distinctiveness Conflict Risk	'Quickbooks integration' carves a clear niche with minimal conflict risk, but the single generic trigger ('interact with Quickbooks data') leaves minor overlap risk versus other accounting skills, fitting just below the fully 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/quickbooks/SKILL.md
Commit: f484c82

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