Name: sellsy
Rating: 63.2 (1 reviews)
Author: membranedev

sellsy

Sellsy integration. Manage Deals, Persons, Organizations, Leads, Projects, Pipelines and more. Use when the user wants to interact with Sellsy data.

Quality

75%

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

Quality

Content

75%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.

Highly actionable CLI documentation with executable commands and a clear, validated connection workflow. The main weakness is conciseness — several explanatory prose passages pad material a competent agent already understands.

Suggestions

Trim explanatory filler such as 'so you can focus on the integration logic rather than auth plumbing' and the URL-normalization paragraph; keep only command-relevant detail.

Fix the inconsistent step numbering (referenced 'Step 2' and '1b' with no preceding 'Step 1'/'1a') so the connection workflow reads as a coherent numbered sequence.

Consider extracting the proxy flag table and the clientAction state taxonomy into a separate reference file to reduce inline bulk and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Command-driven content is mostly efficient, but several prose paragraphs pad concepts a competent agent doesn't need ('so you can focus on the integration logic rather than auth plumbing', the URL-normalization explanation, and the awkward agent-types sentence).	3 / 5
Actionability	Fully executable, copy-paste-ready membrane commands cover install, login, connection ensure, polling, action search/run, and proxy requests, with a concrete JSON-input example and a flag table covering the common cases.	5 / 5
Workflow Clarity	Clear install->auth->connect->poll/handle-client-action->search->run sequence with explicit validation (state polling, the clientAction decision tree, and a re-poll feedback loop), but inconsistent step numbering (an orphan 'Step 2' and '1b' with no '1a') fragments the flow.	4 / 5
Progressive Disclosure	A single self-contained document with well-organized section headers and no bundle files to navigate; some inline bulk content (the proxy flag table and clientAction state taxonomy) could be split into reference files, leaving minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

75%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.

A solid, product-specific description that answers both what and when with several concrete entity types. It falls just short of top marks because the action verb is generic and the trigger clause lacks concrete synonyms or specific trigger phrases.

Dimension	Reasoning	Score
Specificity	Lists several concrete Sellsy objects to manage ('Deals, Persons, Organizations, Leads, Projects, Pipelines'), matching the 'several specific actions; minor gaps' anchor, but the single generic verb 'Manage' keeps it from comprehensive coverage.	4 / 5
Completeness	Has both a clear 'what' (manage the listed Sellsy entities) and an explicit 'when' ('Use when the user wants to interact with Sellsy data'), but the 'when' is generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes the product name plus concrete CRM entity nouns a user would naturally say, but misses common synonyms/variations like 'CRM', 'contacts', 'customers', or 'invoices'.	4 / 5
Distinctiveness Conflict Risk	Naming the specific product Sellsy gives it a clear niche and low conflict risk, but the broad trigger 'interact with Sellsy data' leaves minor overlap with closely related tooling.	4 / 5
	Total	16 / 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/sellsy/SKILL.md
Commit: f484c82

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