Name: eci-software-solutions
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

eci-software-solutions

ECi Software Solutions integration. Manage data, records, and automate workflows. Use when the user wants to interact with ECi Software Solutions 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/eci-software-solutions/SKILL.md

Quality

Content

61%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 largely actionable, well-structured CLI integration guide with a solid connection-state workflow, but it is dragged down by a marketing-style intro, missing validation around destructive Update actions, and a couple of structural redundancies. Tightening the prose and adding verification checkpoints would raise the weakest dimensions.

Suggestions

Add a validation/verification checkpoint before destructive Update actions, e.g. run the matching Get action first and confirm the change with the user before updating.

Remove the company-background paragraph and the filler line "Use action names and parameters as needed" to improve token efficiency.

Fix the dangling "skip to Step 2" reference by explicitly labeling Step 2 (e.g. searching/running actions), and merge the redundant 'Popular actions' section into 'Searching for actions'.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient operational detail (CLI commands, state transitions), but the opening company-background paragraph ("They serve small to medium-sized businesses...") and filler like "Use action names and parameters as needed" are unnecessary padding Claude does not need.	3 / 5
Actionability	It provides many concrete executable commands (install, login, connection ensure/get --wait, action list/run, request) plus a flags table, but examples rely on abstract placeholders (<actionId>, CONNECTION_ID) with no fully-realized worked example, leaving minor gaps.	4 / 5
Workflow Clarity	The connection flow has a clear state machine with a poll/re-poll feedback loop, but the destructive Update actions (Update Customer/Sales Order/etc.) have no validation or verification guidance, capping clarity at 3, and "skip to Step 2" references an undefined step.	3 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no bundle files and none strictly required for this focused CLI guide, but the redundant 'Popular actions' section overlaps 'Searching for actions' and the dangling Step 2 reference leaves minor navigation gaps.	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 correctly includes both a capability summary and an explicit 'Use when' trigger anchored to a named product, but its actions and trigger terms are generic. Sharpening them with concrete entity types (customers, invoices, sales orders) would lift specificity, trigger quality, and distinctiveness.

Suggestions

Replace generic verbs with concrete ECi actions, e.g. "Get and update customers, sales orders, invoices, items, purchase orders, and quotes" to raise specificity.

Add natural entity trigger terms to the 'Use when' clause, e.g. "Use when the user wants to manage ECi customers, invoices, sales orders, or purchase orders."

Drop the marketing-style phrase "automate workflows" in favor of the specific CRUD operations the skill actually exposes.

Dimension	Reasoning	Score
Specificity	Names the domain plus a few action categories ("Manage data, records, and automate workflows"), but these are generic rather than concrete verbs like extract/fill/merge, so it sits at the named-domain-with-actions level rather than comprehensive.	3 / 5
Completeness	It states both a what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with ECi Software Solutions data"), but the when clause uses generic "data" rather than concrete trigger phrases, so it is not a 5.	4 / 5
Trigger Term Quality	"ECi Software Solutions" is a strong product-name trigger and "data"/"records" appear, but the description omits the natural entity terms (customers, sales orders, invoices, items) that users would actually say, leaving common variations missing.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to a single named product gives a clear niche with low conflict risk, but the generic capability verbs (manage data, records, workflows) create minor overlap with other data/integration skills rather than fully distinct triggers.	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/eci-software-solutions/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.