Name: open-accounting
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

open-accounting

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

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/open-accounting/SKILL.md

Quality

Content

75%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 an efficiently structured, actionable guide centered on concrete Membrane CLI commands with a solid connection-state feedback loop; its main weaknesses are a missing worked end-to-end example and slightly loose step numbering.

Suggestions

Add one complete worked example tying the steps together (e.g. connect, discover an invoice action, run it, and read the output) to lift actionability.

Fix the step numbering: replace the dangling '1b' heading and 'skip to Step 2' references with explicit numbered steps or named anchors.

Trim the introductory marketing paragraph and the 'Use action names and parameters as needed.' filler to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven with minimal over-explanation of concepts Claude already knows; minor padding remains, such as the introductory SaaS marketing paragraph and the filler line 'Use action names and parameters as needed.'.	4 / 5
Actionability	Provides concrete, executable commands throughout (install, login, connection ensure/get, action list/run, request) plus a flags table; it stops short of a fully worked end-to-end example (e.g. creating and retrieving an invoice) covering common cases.	4 / 5
Workflow Clarity	Clear install-authenticate-connect-search-run sequence with an explicit state-machine feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED polling); minor gaps from unanchored 'skip to Step 2' references and a '1b' heading with no matching step labels.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no external bundle files to misroute; the inline entity dump and proxy flag table could optionally live in a reference file, leaving only minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

57%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 cleanly answers what and when with an explicit trigger clause tied to a named app, but its action language is generic and it omits the concrete accounting nouns that would sharpen triggers and specificity.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete accounting actions such as 'create and pay invoices, track bills and expenses, and reconcile accounts'.

Add natural trigger keywords users say ('invoices', 'bills', 'expenses', 'bookkeeping') to broaden trigger term coverage.

Name a few Open Accounting entities (Invoice, Bill, Vendor, Chart of Accounts) to distinguish the skill from generic data-management skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('Open Accounting') but the actions listed ('Manage data, records, and automate workflows') are generic rather than concrete accounting verbs; it does not surface the specific capabilities (invoices, bills, expenses, reports) that appear in the body.	2 / 5
Completeness	Has both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Open Accounting data'); the 'when' is clear but the 'what' is somewhat generic rather than concrete.	4 / 5
Trigger Term Quality	Includes the app name plus 'data', 'records', and an explicit 'interact with' trigger, but misses common accounting-domain terms users would naturally say (invoices, bills, expenses, bookkeeping) and their synonyms.	3 / 5
Distinctiveness Conflict Risk	Tied to a named product ('Open Accounting') with a distinct trigger, giving a clear niche and low conflict risk; the generic 'manage data, records' phrasing leaves only minor overlap with other app-integration skills.	4 / 5
	Total	13 / 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/open-accounting/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.