Name: annature
Rating: 55.2 (1 reviews)
Author: membranedev

annature

Annature integration. Manage data, records, and automate workflows. Use when the user wants to interact with Annature data.

Quality

62%

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

Quality

Content

63%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 delivers strong executable CLI guidance and a well-checkpointed connection workflow, but it carries padding (an intro paragraph and a 'No description' actions table) and is monolithic with no progressive disclosure into reference files.

Suggestions

Remove the marketing-style opening paragraph about what Annature is and replace or drop the 20-row 'Popular actions' table whose 'No description' entries add tokens without value.

Add a validation/verification step after running actions (e.g. inspect the `output` field for errors and confirm resulting envelope/account state) to support batch and potentially destructive operations.

Move the bulk actions reference into a separate reference file and link to it from SKILL.md so the main file stays an overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly operational but includes unnecessary padding — a marketing-style intro paragraph ('Annature is a digital signature platform that streamlines document signing...') and a 20-row 'Popular actions' table where every row says 'No description' — fitting 'Mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	Concrete, copy-paste-ready CLI commands are provided throughout (install, login with headless variant, connection ensure/get --wait, action list/run, request with full flag table), with only minor gaps such as the 'No description' actions table and a lack of full input examples, matching 'Mostly executable guidance; concrete code or commands with minor gaps'.	4 / 5
Workflow Clarity	The connect→authenticate→search→run sequence is clear with explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-after-action feedback loop, but there is no validation of action-run results or error recovery for the data operations themselves, fitting 'Clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	All content lives in a single ~177-line SKILL.md with no bundle files or external references, and the large actions table is inlined rather than split out, matching 'Some structure but could be better organized; content that should be separate is inline'.	3 / 5
	Total	14 / 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 correctly uses third person and includes an explicit 'Use when' trigger tied to a distinctive product name, but its capability phrasing is generic and its trigger terms omit the natural vocabulary (signatures, envelopes, documents) users would say.

Suggestions

Replace the generic actions ('Manage data, records, and automate workflows') with Annature-specific capabilities such as creating and sending envelopes for signature, managing templates, and organizing contacts.

Expand the trigger clause with natural user phrasing, e.g. 'Use when the user wants to send documents for signature, manage envelopes, or work with Annature templates and contacts.'

Dimension	Reasoning	Score
Specificity	The description names the domain ('Annature integration') but the actions are generic ('Manage data, records, and automate workflows') rather than concrete Annature capabilities like sending envelopes for signature, managing templates, or organizing contacts, matching the anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Annature data') are present, but the 'what' is generic and the 'when' could name concrete triggers, fitting 'Has both what and when; when could be more explicit or specific'.	4 / 5
Trigger Term Quality	The only natural keyword is the proper noun 'Annature'; it omits the phrases users would actually say such as 'sign a document', 'send an envelope', or 'templates', matching 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	Tied to the unique proper noun 'Annature', the trigger is clearly niche with minimal overlap risk against other skills, 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/annature/SKILL.md
Commit: f484c82

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