Name: sage-accounting
Rating: 62.4 (1 reviews)
Author: membranedev

sage-accounting

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

Quality

74%

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

Quality

Content

82%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 executable CLI commands and a clear connection workflow including polling feedback loops. Minor trimming of the introductory overview and moving the large reference tables to a separate file would further improve conciseness and progressive disclosure.

Suggestions

Trim or remove the opening 'Sage Accounting is an online accounting software...' paragraph, which explains concepts Claude already knows.

Move the popular-actions table and/or the 35-item entity overview into a separate reference file (e.g. ACTIONS.md) referenced from the body.

Reconcile the step numbering (e.g. add a '1a'/'Step 2' label) so the '1b. Wait for the connection' and 'Step 2' references form a coherent sequence.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands and tables, but the opening paragraph explains what Sage Accounting is and who uses it — concepts Claude already knows — which is mild padding.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands covering the full lifecycle (install, login incl. headless, connection ensure/wait, action list, action run with JSON input, proxy) with real flags and examples.	5 / 5
Workflow Clarity	Clear multi-step sequence with feedback loops (poll until not BUILDING; re-poll after user acts to confirm READY) and explicit state handling, but section numbering is inconsistent ('1b' without a matching '1a'/'2') and action-result validation is not formalized.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references and no bundle files, but the large entity-type list and popular-actions table are inlined reference material that could live in a separate file.	4 / 5
	Total	17 / 20 Passed

Description

66%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 tied to a distinct named product and includes an explicit 'Use when...' trigger, but its action list and trigger vocabulary are generic. Tightening the actions and adding concrete accounting terms would raise specificity and trigger quality.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Create and list invoices, bills, contacts, journal entries, and bank accounts.'

Expand trigger terms with natural synonyms users say, such as 'invoices', 'bills', 'expenses', 'chart of accounts', or 'financial reports'.

Make the 'when' clause more specific, e.g. 'Use when the user wants to query or create Sage Accounting records like invoices, contacts, or payments.'

Dimension	Reasoning	Score
Specificity	Names the Sage Accounting domain and a few actions ('Manage accounting data, records, and workflows'), but the actions are generic rather than multiple specific concrete operations like 'create invoices' or 'list contacts'.	3 / 5
Completeness	Provides a clear 'what' and an explicit 'Use when...' trigger clause, but the 'when' is generic ('when the user wants to interact with Sage Accounting data') rather than enumerating concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes relevant natural terms ('Sage Accounting', 'accounting data, records, and workflows') but misses common variations and synonyms users would say, such as invoices, bills, contacts, or expenses.	3 / 5
Distinctiveness Conflict Risk	Tied to a specific named vendor product (Sage Accounting), giving it a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	15 / 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/sage-accounting/SKILL.md
Commit: f484c82

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