Name: clear-books
Rating: 60 (1 reviews)
Author: membranedev

clear-books

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

Quality

70%

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/clear-books/SKILL.md

Quality

Content

78%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 is highly actionable with copy-paste-ready membrane CLI commands and a well-sequenced connection state machine, but it keeps everything inline with no reference files and adds light introductory padding. Validation feedback loops around action execution could be made more explicit.

Suggestions

Add an explicit validation step after running actions (e.g. check the `output` field / error status before proceeding) to strengthen the feedback loop.

Trim the opening descriptive paragraph about what Clear Books is, since Claude already knows, and avoid restating the `action list` command in two places.

Consider extracting the proxy flag reference table or webhook/action catalog into a reference file to reduce SKILL.md weight if the skill grows.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with executable commands and minimal over-explanation of concepts Claude already knows, though a few lines (e.g. the introductory paragraph and restating the action-list command) could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure, polling, action search/run, and proxy requests, covering the common cases with concrete flags and JSON examples.	5 / 5
Workflow Clarity	The connect-to-READY flow is sequenced with state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling feedback, but there is no explicit validation checkpoint after running actions or before relying on proxy results, a minor gap.	4 / 5
Progressive Disclosure	There are no bundle files and no one-level-deep references; the entire API surface (overview, auth, connection, actions, proxy, best practices) is inlined in SKILL.md, which is acceptable for a small skill but leaves structure as section headers only.	3 / 5
	Total	16 / 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 a distinct niche (Clear Books) and includes an explicit 'Use when' clause, but its action verbs ('Manage data, records, automate workflows') are generic rather than concrete. Tightening the what with specific operations would raise specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Clear Books operations, e.g. 'Create and track invoices, manage contacts, record bill payments, and react to webhook events'.

Add natural trigger terms and synonyms users would say, such as 'invoice', 'expense', 'bookkeeping', or 'accounting'.

Make the 'when' clause more specific by listing the concrete scenarios that should invoke the skill.

Dimension	Reasoning	Score
Specificity	It names the domain ('Clear Books integration') and a couple of generic actions ('Manage data, records, and automate workflows') but the actions are not concrete or comprehensive, matching the score-3 anchor of 1-2 concrete actions.	3 / 5
Completeness	It states what the skill does ('Manage data, records, and automate workflows') and gives an explicit 'when' clause ('Use when the user wants to interact with Clear Books data'), but the 'when' could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	It includes 'Clear Books data' as a relevant keyword but misses common variations or synonyms a user would naturally say, fitting the score-3 anchor of some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	The Clear Books niche is fairly distinct with a clear named app trigger, carrying only minor overlap risk with other accounting-related 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/clear-books/SKILL.md
Commit: f484c82

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