Name: signwell
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

signwell

SignWell integration. Manage Users, Documents, Teams. Use when the user wants to interact with SignWell data.

Quality

64%

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

Quality

Content

67%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 actionable with a clear install-to-run workflow and a genuine polling validation loop, but it pads in background context Claude already knows and repeats the action-discovery instructions. Organization is solid for a single-file skill with only minor inlining.

Suggestions

Remove the "SignWell is an e-signature platform... competitor to DocuSign or Adobe Sign" background paragraph; Claude does not need SignWell explained.

Consolidate the duplicated action-list instructions ("Searching for actions" and "Popular actions") into one section and explicitly show how to pipe the connection id from `connection ensure` into `action run`.

Fix the step numbering ("Step 2" with no Step 1a/2 anchor) so the connection readiness sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands but explains things Claude already knows ("SignWell is an e-signature platform... Think of it as a competitor to DocuSign") and repeats the action-list instruction in two sections, matching the anchor for mostly efficient with some unnecessary explanation.	3 / 5
Actionability	Concrete executable commands are provided throughout (install, login, connection ensure, action run with --input) and the proxy flags are documented, but placeholders like CONNECTION_ID are never wired to the connection id obtained earlier, leaving a minor gap.	4 / 5
Workflow Clarity	There is a clear sequenced workflow with a real polling/validation feedback loop (BUILDING -> CLIENT_ACTION_REQUIRED/READY/error states), but step numbering is inconsistent ("Step 2", "1b") and no checkpoint guards destructive or batch actions, leaving minor validation gaps.	4 / 5
Progressive Disclosure	This single-file skill is organized into clear sections (Overview, Working with SignWell, Popular actions, Best practices), but inlined blocks like the proxy-flag table and the clientAction enum could be split out, matching the anchor for good structure with minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

61%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 identifies its niche (SignWell e-signature) and includes an explicit Use-when clause, but its action verbs are generic ("Manage") and it lacks natural trigger synonyms like "e-signature" or "sign documents." Stronger on distinctiveness than on specificity or trigger coverage.

Suggestions

Replace the generic verb "Manage" with concrete operations, e.g. "Send, sign, and track documents; manage users and teams."

Add natural trigger terms a user would say, e.g. "Use when the user wants to e-sign documents, send for signature, or manage SignWell users, documents, and teams."

Drop the filler phrase "SignWell integration." and lead with the concrete actions to tighten the description.

Dimension	Reasoning	Score
Specificity	"Manage Users, Documents, Teams" names the domain and resources but the action verb "Manage" is generic rather than a concrete operation (create, send, sign), so it sits just below the midpoint where actions are minimal/generic.	2 / 5
Completeness	It answers both "what" ("SignWell integration. Manage Users, Documents, Teams") and "when" ("Use when the user wants to interact with SignWell data"), but the trigger clause is generic rather than a concrete trigger phrase, so it does not reach the fully explicit anchor.	4 / 5
Trigger Term Quality	"SignWell" and the resource names are relevant keywords, but there are no natural synonyms a user would actually say (e.g. "e-signature", "sign documents"), matching the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	"SignWell" names a specific e-signature product, giving it a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	14 / 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/signwell/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.