Name: hellosign
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

hellosign

HelloSign integration. Manage Templates, Teams, Accounts. Use when the user wants to interact with HelloSign data.

Quality

72%

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

Quality

Content

82%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 a strong, actionable integration guide with executable commands, real action names, and a well-sequenced connection workflow featuring explicit state checkpoints. It is slightly held back by a minor marketing-style preamble and a monolithic structure that inlines reference-style tables.

Suggestions

Trim the opening product paragraph and remove filler lines like 'Use action names and parameters as needed.' to tighten token usage.

Move the popular-actions table and proxy flag reference into a separate reference file (e.g. references/actions.md) and link to it from the overview.

Add a short numbered master sequence for the connection lifecycle and a brief recovery checklist for the CONFIGURATION_ERROR / SETUP_FAILED states.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, tables, and brief explanations, but the opening product blurb ('HelloSign is an e-signature platform...') and filler lines like 'Use action names and parameters as needed.' could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready commands are given throughout (install, login, connection ensure, action list/run with --input JSON, proxy with a flag table) plus a popular-actions table with real action keys covering common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state checkpoints and a poll-then-branch feedback loop (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but cross-references like 'Step 2' and '1b' are slightly jumbled and error-state recovery lacks a checklist.	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers, tables, and logical flow, and there are no deeply nested references; however the skill is monolithic (~157 lines) with no detail files, and the popular-actions/proxy-reference tables could live in separate reference files.	4 / 5
	Total	17 / 20 Passed

Description

62%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 clearly identifies the HelloSign niche and includes an explicit 'Use when' clause, satisfying basic completeness. Its main weaknesses are a generic 'Manage' verb, the absence of natural signing/signature trigger terms, and a somewhat vague 'when' condition.

Suggestions

Replace the generic verb 'Manage' with specific actions, e.g. 'Create and send signature requests, manage templates and teams, retrieve signed documents'.

Add natural trigger terms a user would say: 'sign documents', 'request signatures', 'e-signature', 'signature request'.

Tighten the 'Use when' clause with concrete scenarios, e.g. 'Use when the user wants to send or request e-signatures, manage HelloSign templates, or track signature requests.'

Dimension	Reasoning	Score
Specificity	Names the HelloSign domain and concrete entities ('Manage Templates, Teams, Accounts') but relies on a single generic verb ('Manage') rather than distinct specific actions, so it is not comprehensive.	3 / 5
Completeness	Both 'what' ('HelloSign integration. Manage Templates, Teams, Accounts.') and an explicit 'when' ('Use when the user wants to interact with HelloSign data.') are present, though the trigger is generic rather than concrete scenarios.	4 / 5
Trigger Term Quality	The brand keyword 'HelloSign' and entity types (Templates, Teams, Accounts) are present, but the natural terms a user would actually say ('sign', 'signature', 'e-signature', 'document') are missing.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'HelloSign' with distinct entity types gives it a clear niche and minimal conflict risk, but the generic 'interact with HelloSign data' trigger leaves minor overlap risk.	4 / 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/hellosign/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.