Name: e-conomic
Rating: 60.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

e-conomic

E-conomic integration. Manage Organizations, Users. Use when the user wants to interact with E-conomic data.

Quality

71%

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/e-conomic/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 highly actionable with copy-paste CLI commands and a strong connection workflow, and it is reasonably concise with clear section structure. The main weakness is the lack of validation/verification steps around the destructive and create/update/delete actions the skill exposes, which caps workflow clarity.

Suggestions

Add an explicit validation/verification step before destructive action runs, e.g. list and confirm the target (get-draft-invoice) before running delete-draft-invoice, and check the response error field after the call.

Introduce a feedback loop for action execution (run -> inspect output/error -> retry or report), especially for create/update/delete operations on invoices, customers, suppliers, and products.

Trim the opening explanatory paragraph about what E-conomic is, since it restates context Claude can infer, to push conciseness toward 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands, tables, and flags, but the opening "E-conomic is an online accounting software primarily used by small to medium-sized businesses..." is minor over-explanation of context Claude can infer, matching anchor 4. It is above 3 because the bulk is efficient and below 5 due to that padded intro and a few explanatory asides.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands with flags and JSON input examples covering the common cases (login, connection ensure/wait, action list, action run with --input, request proxy), matching anchor 5. It is not 4 because the guidance is concrete and complete rather than having minor gaps.	5 / 5
Workflow Clarity	The connection setup is a well-sequenced flow with checkpoints (poll --wait until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but the skill exposes destructive actions (delete-draft-invoice, create/update/delete on customers/invoices/products) with no validation or verification step before running them, so the destructive-operations cap holds at 3. It is not 4 because that validation gap is explicit in the rubric and takes precedence.	3 / 5
Progressive Disclosure	No bundle files exist, and the body is one self-contained SKILL.md with well-organized section headers (Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices), matching anchor 4. It is below 5 because the sizable inline Popular-actions table and proxy-flag table are reference-like content that could be split out, and above 3 because structure is otherwise clear and navigable.	4 / 5
	Total	16 / 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 correctly answers both what and when and is anchored to a distinct, named application niche, but its capability list and trigger terms are thin compared to the actions the body actually exposes. Expanding concrete actions and natural-language synonyms would raise specificity and trigger quality.

Suggestions

Replace the minimal "Manage Organizations, Users" with the concrete actions the skill exposes (e.g., create/list/update invoices, customers, suppliers, products, accounts) to lift specificity toward a comprehensive 5.

Add natural trigger phrases and synonyms users actually say, such as "accounting", "invoicing", "bookkeeping", and "E-conomic customers/invoices", to improve trigger_term_quality.

Make the "when" clause more scenario-specific (e.g., "Use when the user wants to manage E-conomic invoices, customers, suppliers, or accounting data") to move completeness from 4 to 5.

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Users" names the E-conomic domain plus 1-2 concrete actions, but the coverage is minimal and generic compared to the many actions the body documents (invoices, customers, products, suppliers, accounts). It fits anchor 3 rather than 4 because the action list is not comprehensive, and is above 2 because it does name real actions rather than only the domain.	3 / 5
Completeness	It states both a clear "what" ("E-conomic integration. Manage Organizations, Users") and an explicit "when" ("Use when the user wants to interact with E-conomic data"), matching anchor 4. It does not reach 5 because the "when" trigger is general and lacks concrete scenario phrases.	4 / 5
Trigger Term Quality	The terms "E-conomic" and "E-conomic data" are relevant keywords a user might say, but the description omits common synonyms and variations the body uses (accounting, invoicing, bookkeeping, customers, invoices), matching anchor 3. It is above 2 because there is more than one generic keyword, but below 4 due to missing natural variations.	3 / 5
Distinctiveness Conflict Risk	"E-conomic" is a specific named accounting application, giving the skill a clear niche with distinct triggers and minimal overlap risk with other skills, matching anchor 5. It is not 4 because the app name alone is sufficiently distinctive rather than merely "mostly distinct."	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/e-conomic/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.