Name: signaturit
Rating: 59.2 (1 reviews)
Author: membranedev

signaturit

Signaturit integration. Manage Persons, Organizations, Users, Roles, Files. Use when the user wants to interact with Signaturit data.

Quality

68%

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

Quality

Content

75%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 copy-paste CLI commands and a well-structured connection workflow including error-state feedback, though it carries some marketing padding and lacks validation guidance for destructive entity operations.

Suggestions

Trim the introductory marketing paragraph about Signaturit's industry use to a one-line factual description.

Add a validation/verification step for actions that mutate Users, Roles, or Files (e.g. confirm before delete, verify the result after run).

Consider moving the proxy flags reference table into a separate reference file and linking to it to keep the main flow lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands, but the opening marketing paragraph ('Businesses across various industries use it to streamline...') and a few editorial comments ('so you can focus on the integration logic rather than auth plumbing') could be trimmed.	3 / 5
Actionability	Copy-paste-ready commands cover the common cases end to end — install, login, connection ensure, action list/run with JSON input, and proxy requests — reinforced by a concrete flags table.	5 / 5
Workflow Clarity	The connection flow has an explicit state machine with polling and a feedback loop (re-poll after CLIENT_ACTION_REQUIRED), but running actions on potentially destructive entities (Users, Roles, Files) lacks validation or verification checkpoints.	4 / 5
Progressive Disclosure	No bundle files exist, and the single SKILL.md is organized into clear, well-labeled sections with content appropriately kept inline; only minor organization gains would come from splitting the proxy/action reference.	4 / 5
	Total	16 / 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 correctly includes both a capability statement and a 'Use when' trigger for a clearly named product, but its action language is generic ('Manage') and its trigger clause is vague rather than tied to concrete user phrases.

Suggestions

Replace the generic verb 'Manage' with concrete actions, e.g. 'Create, list, update, and delete Persons, Organizations, Users, Roles, and Files'.

Make the 'Use when' trigger concrete and natural, e.g. 'Use when the user wants to create or manage Signaturit users, roles, or files, or interact with the Signaturit API'.

Add synonyms a user might say (e.g. 'Signaturit users', 'Signaturit roles', 'Signaturit API') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists several Signaturit resources ('Persons, Organizations, Users, Roles, Files') but only the single generic action verb 'Manage', so it names the domain and a coarse action without comprehensive concrete verbs.	3 / 5
Completeness	Both 'what' ('Manage Persons, Organizations, Users, Roles, Files') and 'when' ('Use when the user wants to interact with Signaturit data') are present, but the 'when' is generic rather than explicit and specific.	4 / 5
Trigger Term Quality	'Signaturit' and the entity names are relevant keywords, but the trigger clause 'interact with Signaturit data' is generic and misses common natural variations a user would actually say.	3 / 5
Distinctiveness Conflict Risk	'Signaturit integration' is a clear, named niche with minimal conflict risk, though the generic entity terms (Users, Roles, Files) leave minor overlap risk with adjacent CRM-style skills.	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/signaturit/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.