Name: simplero
Rating: 64 (1 reviews)
Author: membranedev

simplero

Simplero integration. Manage Persons, Organizations, Deals, Pipelines, Activities, Notes and more. Use when the user wants to interact with Simplero data.

Quality

76%

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/simplero/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.

The body is highly actionable with copy-paste-ready CLI commands and a clear connection workflow that includes validation and feedback loops. Its main weakness is conciseness — a padded intro and a repetitive entity-overview list — plus slightly disjointed step numbering that keeps workflow clarity just below the top level.

Suggestions

Collapse the "Simplero Overview" list: instead of repeating "List — a collection of X" for each entity, state the pattern once and list the entities inline, or drop it if the description already enumerates them.

Tighten the opening paragraph to a one-line platform summary or remove it, since it explains general knowledge Claude already has.

Make the connection workflow's step numbering coherent (e.g., label "Step 2" and fold Searching/Running actions into the same numbered sequence) so the skip-to and poll-after-action jumps are unambiguous.

Dimension	Reasoning	Score
Conciseness	The commands are efficient, but the intro paragraph explains what Simplero is and the "Simplero Overview" repeats "List — a collection of X" eight times, which is noticeable padding that could be tightened.	3 / 5
Actionability	Copy-paste-ready commands cover the common cases throughout (login, connection ensure/wait, action list/run with JSON input, request proxy) and a flags table documents the proxy options, matching fully executable guidance.	5 / 5
Workflow Clarity	The connection workflow has explicit validation (poll until state is not BUILDING, inspect state values) and feedback loops (re-poll after CLIENT_ACTION_REQUIRED), but step numbering is disjointed ("1b", an unlabeled "Step 2") and search/run are separate from the numbered flow.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections and is self-contained with no external references needed; at over 50 lines some material (proxy flags table, clientAction states) could be split into a reference file, so it sits at good structure with minor organization gaps rather than a 5.	4 / 5
	Total	16 / 20 Passed

Description

78%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 strong: it names a concrete platform and the data entities it manages, and includes an explicit "Use when" trigger. It falls just short of top marks on specificity and completeness because it relies on one generic verb and a single trigger phrase rather than enumerating distinct actions and multiple natural triggers.

Dimension	Reasoning	Score
Specificity	Lists many concrete entities ("Persons, Organizations, Deals, Pipelines, Activities, Notes and more") but only a single generic verb ("Manage"), so it shows several specific items with minor action gaps rather than comprehensive distinct actions.	4 / 5
Completeness	Both the "what" ("Manage Persons, Organizations...") and an explicit "when" ("Use when the user wants to interact with Simplero data") are present; not a 5 because the trigger is a single phrase rather than the richer multi-trigger pattern in the anchor 5 example.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Simplero data" plus the brand name "Simplero" gives good natural trigger coverage; not comprehensive enough for a 5 (no synonyms or variations), but clearly above a 3.	4 / 5
Distinctiveness Conflict Risk	"Simplero" is a specific named platform, giving a clear niche with distinct triggers and minimal risk of firing for the wrong skill.	5 / 5
	Total	17 / 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/simplero/SKILL.md
Commit: f484c82

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