Name: eversign
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

eversign

Eversign integration. Manage Users, Organizations. Use when the user wants to interact with Eversign data.

Quality

67%

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

Quality

Content

68%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 highly actionable with concrete CLI commands and a strong connection-state workflow, but it carries an unnecessary marketing intro and lacks validation guidance for its destructive document operations. Splitting the action catalogue into a reference file and adding confirmation steps would meaningfully improve it.

Suggestions

Remove or trim the opening background paragraph ("Eversign is a cloud-based platform...") since Claude does not need the product pitch.

Add an explicit confirmation/validation step before destructive actions, e.g. verify the document hash with get-document and confirm with the user before running delete-document, trash-document, or cancel-document.

Move the Popular actions table into a referenced file (e.g. references/actions.md) and link to it from SKILL.md to keep the overview lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-focused guidance, but the opening marketing paragraph ("Eversign is a cloud-based platform that provides legally binding e-signatures...") and prose like "so you can focus on the integration logic rather than auth plumbing" explain background Claude does not need.	3 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) plus concrete flag tables and a popular-actions table, covering the common cases with executable specifics.	5 / 5
Workflow Clarity	The connection setup has a clear state-machine sequence with polling feedback loops, but destructive actions (delete-document, trash-document, cancel-document) are listed without any validation or confirmation checkpoint, capping this dimension at 3.	3 / 5
Progressive Disclosure	The skill is a single well-organized file with clear section headers and no nested references (no bundle files exist), so structure is good; it sits just below a 5 because the popular-actions table is somewhat bulky inline and there are no signaled reference files for deeper detail.	4 / 5
	Total	15 / 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 cleanly states a named-product niche with both a what and a when clause, but the actions are generic ("Manage") and the trigger terms lack the natural synonyms users would actually say. Tightening the verb choices and adding concrete trigger phrases would lift it from good to strong.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "Create, send, and track documents and templates, manage users and teams".

Expand the trigger clause with natural phrasings users say, e.g. "Use when the user wants to send documents for e-signature, track signing status, or manage Eversign documents, templates, and teams".

Reflect the full object model (Document, Template, Team) in the description rather than only Users and Organizations.

Dimension	Reasoning	Score
Specificity	Names the domain ("Eversign integration") and two concrete targets ("Manage Users, Organizations"), matching the anchor for domain plus 1-2 actions, but "Manage" is a generic verb and coverage is not comprehensive.	3 / 5
Completeness	Both what ("Manage Users, Organizations") and when ("Use when the user wants to interact with Eversign data") are present, but the trigger clause is generic rather than concrete.	4 / 5
Trigger Term Quality	The only natural keyword is "Eversign"; common user phrasings like e-signature, signing documents, or contracts are absent, so coverage has relevant terms but misses common variations.	3 / 5
Distinctiveness Conflict Risk	Naming a specific product (Eversign) gives it a clear niche with distinct triggers and minimal risk of firing for an unrelated skill.	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/eversign/SKILL.md
Commit: f484c82

Reviewed: 5 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.