Name: softledger
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

softledger

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

Quality

61%

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

Quality

Content

60%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 delivers strong, executable CLI guidance with a clear connection workflow. Its main weakness is token efficiency, dominated by an over-explained intro and a long undirected entity list.

Suggestions

Trim the introductory paragraph to one line; Claude does not need a feature inventory of accounting software.

Move the ~100-entity list into a separate reference file (e.g., entities.md) and link to it, or group entities by domain with brief usage notes.

Fix step numbering so 'Step 2' referenced in the connection section actually exists as a labeled heading.

Dimension	Reasoning	Score
Conciseness	Noticeably verbose: the opening paragraph explains what accounting software is and its features, and a ~100-item bullet list of entity names consumes significant tokens with no guidance on using them.	2 / 5
Actionability	Provides concrete, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) with documented flags covering the common integration cases.	4 / 5
Workflow Clarity	Clear sequence from install → authenticate → connect → poll until READY → search → run, with a real feedback loop for connection state transitions, though step numbering is inconsistent ('1b', referenced 'Step 2').	4 / 5
Progressive Disclosure	Well-organized into logical sections in a single file with no nested references; the giant entity list is arguably reference data that could live elsewhere, but navigation is otherwise clear.	4 / 5
	Total	14 / 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 covers both what the skill does and when to use it, anchored to a distinct named product. It is held back by generic action verbs and a lack of natural keyword variations.

Suggestions

Replace generic verbs with concrete SoftLedger actions (e.g., 'create invoices, post journal entries, reconcile payments').

Add natural trigger variations such as 'accounting', 'ledger', 'bills', or 'financials' alongside 'SoftLedger'.

Tighten the 'Use when' clause with specific scenarios (e.g., 'Use when the user wants to query or update SoftLedger accounting data').

Dimension	Reasoning	Score
Specificity	Names the SoftLedger domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete like 'extract content' or 'fill forms'.	3 / 5
Completeness	Clearly states both what ('SoftLedger integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with SoftLedger data'), though the 'when' is somewhat generic.	4 / 5
Trigger Term Quality	Includes the product name 'SoftLedger' and the trigger phrase 'interact with SoftLedger data', but lacks synonyms, file extensions, or common variations users might say.	3 / 5
Distinctiveness Conflict Risk	Targets a specific named product niche (SoftLedger) with a dedicated trigger, making overlap with other skills unlikely, though the trigger phrasing is broad.	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/softledger/SKILL.md
Commit: f484c82

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