BF quickbooks-api
Production-grade integration and automation with the QuickBooks Online API. Covers OAuth 2.0 authentication, accounting entities (Customers, Invoices, Payments, Bills, Journal Entries), real-time Webhooks, Reports API, Payments API, IDS query language, Change Data Capture, Batch operations, and AI/MCP server integration.
Production-grade integration and automation with the QuickBooks Online API.
As a process F 26/100 · Will not run — References files that are not bundled: references/authentication.md, references/accounting_entities.md, references/webhooks.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: references/authentication.md - warning
missing-refreference to a missing file: references/accounting_entities.md - warning
missing-refreference to a missing file: references/webhooks.md - warning
missing-refreference to a missing file: references/queries_and_errors.md - warning
missing-refreference to a missing file: references/ai_and_mcp.md
Process rating: all ten parameters 26/100
- 0Tools and files. 5 referenced file(s) missing: references/authentication.md, references/accounting_entities.md, references/webhooks.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 10 mutating operations with no state check
- 40Consistency. Frontmatter name (quickbooks-api) differs from the folder (quickbook)
- 85Steps. 8 steps, 1 vague phrases
- 100Execution cost. Instruction body is 1378 tokens
- low The response is described with custom markup (15 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 322: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 8 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.