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

upbooks

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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/upbooks/SKILL.md

Quality

Content

67%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 action-packed with executable Membrane CLI commands and a solid connection-state feedback loop, weakened mainly by a redundant product intro and a broken step cross-reference. Trimming inference-level context and fixing the "Step 2" labels would lift it.

Suggestions

Delete or condense the opening paragraph explaining what UpBooks is; Claude does not need the product background to run CLI commands.

Resolve the dangling "Step 2" references by either labeling the "Searching for actions" section as Step 2 or removing the cross-references.

Add one concrete UpBooks-specific action example (e.g., listing or running an invoice/reports action) so the actionability coverage reaches the common cases.

Dimension	Reasoning	Score
Conciseness	Mostly command-driven and efficient, but the opening "UpBooks is a cloud-based accounting software designed for small business owners..." and the agent-types aside explain context Claude could infer, fitting the "mostly efficient but includes some unnecessary explanation" anchor.	3 / 5
Actionability	Concrete, executable commands throughout (npm install, membrane login, connection ensure, action list/run, request) with parameterized placeholders and a flags table, matching the "mostly executable guidance with minor gaps" anchor; falls short of 5 because no UpBooks-specific action example is shown.	4 / 5
Workflow Clarity	A clear install→authenticate→connect→poll→search→run sequence exists with an explicit state feedback loop (BUILDING/READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but dangling "skip to Step 2" references with no matching "Step 2" header leave a minor navigation gap, fitting the 4 anchor over the fully-checkpointed 5.	4 / 5
Progressive Disclosure	Single-file skill with no bundle files, organized into well-labeled sections (Overview, Working with UpBooks, Best practices); structure is good and navigation is clear, but at ~140 lines with all content inline it sits at the "good structure, minor organization gaps" anchor rather than the lean 5.	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 answers both what and when with a clear brand-specific trigger, but its action verbs are generic and trigger-term coverage is narrow. Tightening the actions to concrete UpBooks operations and adding synonyms would raise it.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete UpBooks operations (e.g., "create invoices, reconcile transactions, pull financial reports").

Expand the trigger clause with natural synonyms users might say (e.g., "Use when the user mentions UpBooks, accounting books, invoices, or expense tracking").

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the UpBooks domain plus a couple of actions, but the actions are generic ("data", "records") rather than concrete, matching the anchor that lists 1-2 actions without comprehensive coverage.	3 / 5
Completeness	Both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with UpBooks data") are present; the "when" clause is explicit but generic, matching the anchor where both exist yet the trigger could be more specific.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with UpBooks data" supplies the brand keyword and a trigger phrase, but coverage is thin — missing natural synonyms or variations users might say, fitting the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	The UpBooks brand name gives a distinct niche with a clear trigger, but the generic "data/records/workflows" phrasing leaves minor overlap risk with other accounting/integration skills, fitting the "mostly distinct; minor overlap risk" anchor rather than the fully-distinct 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/upbooks/SKILL.md
Commit: f484c82

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