Name: easyly
Rating: 56.8 (1 reviews)
Author: membranedev

easyly

Easyly integration. Manage Organizations, Projects, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Easyly data.

Quality

65%

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/easyly/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 content is a strongly actionable CLI integration guide with a real feedback loop for connection readiness. It is held back by some conceptual padding, a confusing entity/action mismatch, and a lack of validation steps around destructive lead operations.

Suggestions

Add a validation/confirmation checkpoint before destructive actions (e.g. "Before delete-lead, confirm the lead ID with the user or run get-lead first to verify").

Trim the marketing background ("used by sales, marketing, and customer success teams...") and the filler line "Use action names and parameters as needed".

Reconcile the Easyly Overview entities (Candidate, Job Application, Job, User) with the Popular actions table (Leads only) so the agent knows the true entity model, and fix the dangling "skip to Step 2" reference with explicit step labels.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command reference, but includes unnecessary padding such as "It's used by sales, marketing, and customer success teams to onboard users" and the filler line "Use action names and parameters as needed", plus a sparse Overview list that adds little.	3 / 5
Actionability	Concrete, copy-paste-ready commands cover the common cases (install, login, connection ensure, action list/run, request proxy) with a flags table, but placeholders like CONNECTION_ID and a disconnect between the Overview entities and the Leads-only Popular actions leave minor gaps.	4 / 5
Workflow Clarity	The connect-and-poll flow has explicit state checkpoints and a feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but destructive actions like "Delete Lead" and "Update Lead" are run with no validation or confirmation step, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	The single-file skill is well-sectioned (Overview, Working with Easyly, Connecting, Searching, Running, Proxy, Best practices) with no nested references and easy navigation; minor gaps are the dangling "Step 2" reference and the sparse Overview section.	4 / 5
	Total	14 / 20 Passed

Description

70%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 cleanly states both what the skill does and when to use it, anchored to a distinct product name. Its main weakness is the generic verb "Manage" covering all entities and a broad when-clause rather than concrete triggers.

Suggestions

Replace the generic verb "Manage" with the concrete CRUD verbs actually supported (e.g. "Create, list, update, and delete Organizations, Projects, Pipelines, Users, Goals, and Filters").

Tighten the when-clause with concrete triggers, e.g. "Use when the user wants to create or update Easyly leads, pipelines, goals, or other Easyly records."

Align the listed entities with the skill's actual actions (the body emphasizes Leads, which is absent from the description).

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Projects, Pipelines, Users, Goals, Filters" names the domain and enumerates many concrete resources, but the single generic verb "Manage" does not differentiate the actual actions (create/list/update/delete), so it names domain and entities without comprehensive concrete actions.	3 / 5
Completeness	It explicitly answers "what" ("Manage Organizations, Projects, Pipelines, Users, Goals, Filters") and "when" ("Use when the user wants to interact with Easyly data"), but the when-clause is generic rather than concrete trigger phrases, so it is not a 5.	4 / 5
Trigger Term Quality	Natural terms a user would say are present — the product name "Easyly" plus entity names "Organizations, Projects, Pipelines, Users, Goals, Filters" — giving good keyword coverage, though a few common variations (e.g. "leads") are missing.	4 / 5
Distinctiveness Conflict Risk	Scoping everything to the distinct product name "Easyly" gives it a clear niche with minimal conflict risk, but standalone entity words like "Projects", "Goals", and "Users" carry minor overlap risk with generic project-management skills.	4 / 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/easyly/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.