Name: signaturely
Rating: 60.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

signaturely

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

Quality

71%

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

Quality

Content

81%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 executable CLI commands and a clear state-machine-driven workflow including validation feedback loops, held back only by an unnecessary introductory paragraph and a lack of any progressive-disclosure file split.

Suggestions

Cut the opening paragraph explaining what Signaturely/e-signatures are and the vacuous 'When to use which actions' line; assume Claude's competence.

Move the flags table and proxy details into a short reference file linked from the main body to improve progressive disclosure and token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands, but the opening paragraph ('Signaturely is an e-signature platform that allows users to create, send...') explains concepts Claude already knows and 'When to use which actions: Use action names and parameters as needed.' is non-instructive padding, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	The body is full of copy-paste-ready commands (npm install, membrane login, connection ensure, action list/run, request) plus a concrete flags table, fully covering common cases and matching 'fully executable; copy-paste ready code or commands'.	5 / 5
Workflow Clarity	The flow (install -> authenticate -> connect -> poll for READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR -> retry after action -> search -> run) is a clear sequence with explicit state-based validation checkpoints and a feedback loop ('poll again... to check if the state moved to READY'), matching the top anchor.	5 / 5
Progressive Disclosure	The content is well-sectioned with clear headers and no deep nested references, but everything lives in a single ~140-line file with no offloaded detail files, so it sits at 'good structure; most content appropriately placed' rather than the fully-split top anchor.	4 / 5
	Total	17 / 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 answers both what and when and is anchored to a distinctive product name, but its action vocabulary is generic ('Manage') and it lacks natural trigger synonyms like e-signature or signing that users would actually say.

Suggestions

Replace the generic verb 'Manage' with concrete actions, e.g. 'Create, send, and track e-signature documents; invite signers; manage users and teams.'

Expand the trigger clause with natural terms users say, e.g. 'Use when the user mentions Signaturely, e-signatures, electronic signatures, or sending documents for signing.'

Dimension	Reasoning	Score
Specificity	The description names the domain and entities ('Manage Documents, Users, Teams') but relies on a single generic verb ('Manage') rather than concrete actions, matching the 'names the domain but actions are minimal or generic' anchor; it does not reach 3 because it lists no specific operations like create/send/sign.	2 / 5
Completeness	Both 'what' ('Manage Documents, Users, Teams') and 'when' ('Use when the user wants to interact with Signaturely data') are present and explicit, but the trigger clause is generic rather than enumerating concrete scenarios, matching 'has both what and when; when could be more explicit'.	4 / 5
Trigger Term Quality	'Signaturely' and 'interact with Signaturely data' provide the core product keyword, but common natural variations users would say (e-signature, signing, documents) are absent, matching 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	'Signaturely integration' names a specific SaaS product with a distinct niche, making it unlikely to trigger for unrelated skills and matching 'clear niche with distinct triggers; minimal conflict risk'.	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/signaturely/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.