Name: lessaccounting
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

lessaccounting

LessAccounting integration. Manage Organizations. Use when the user wants to interact with LessAccounting data.

Quality

69%

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

Quality

Content

76%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 a lean, actionable Membrane CLI integration guide with executable commands throughout. Its main weakness is workflow clarity: it lacks validation/verification checkpoints and error-recovery feedback loops for action runs and proxy requests.

Suggestions

Add explicit validation after key steps, e.g. verify a connection exists and was created before running actions, and check the JSON output for errors before proceeding.

Include an error-recovery feedback loop (e.g. 'if action run fails with an auth error, re-run connection list to confirm the connectionId, then retry').

Trim the opening product-description paragraph and the best-practices rationale, which explain value Claude can infer, to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands and minimal concept-explanation, though the opening product description and the best-practices rationale add minor padding that could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands for login, connecting, listing connections, discovering actions, running actions with JSON input, and proxying requests with a clear options table.	5 / 5
Workflow Clarity	A clear sequence exists (setup → connect → search → run), but there are no explicit validation or verification checkpoints, and no feedback loop for when an action or proxy request fails.	3 / 5
Progressive Disclosure	A single, well-organized file with clear section headers and no nested or buried references; no bundle files exist, so structure carries it, with only minor organization gaps.	4 / 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 is third-person and includes an explicit trigger clause, covering both what and when. It is hampered by minimal concrete actions and limited trigger-term variety, keeping it in the mid-range.

Suggestions

Replace the generic 'interact with LessAccounting data' with specific actions like 'create invoices, track expenses, and manage clients' to lift specificity.

Add natural trigger synonyms users might say, e.g. 'Use when the user asks about invoices, expenses, time tracking, or LessAccounting reports.'

Drop or expand 'Manage Organizations' — it is one narrow action and doesn't reflect the overview's broader capabilities (invoices, expenses, contacts).

Dimension	Reasoning	Score
Specificity	Names the domain (LessAccounting) and one concrete action ('Manage Organizations'), but 'interact with LessAccounting data' is generic and coverage is not comprehensive.	3 / 5
Completeness	Both a 'what' ('LessAccounting integration. Manage Organizations.') and a 'when' ('Use when the user wants to interact with LessAccounting data') are present, though the 'what' is thin and could be more specific.	4 / 5
Trigger Term Quality	Includes the natural keyword 'LessAccounting' and an explicit 'Use when...' trigger, but lacks synonyms or common variations users might say.	3 / 5
Distinctiveness Conflict Risk	The named LessAccounting product gives it a clear niche with minimal conflict risk; 'Manage Organizations' is generic but anchored by the brand.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: membranedev/application-skills
Path: skills/lessaccounting/SKILL.md
Commit: f484c82

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