Name: signiflow
Rating: 60 (1 reviews)
Author: membranedev

signiflow

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

Quality

70%

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

Quality

Content

78%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 highly actionable, dominated by executable CLI commands and a clearly sequenced connection workflow with state checkpoints. Its main weaknesses are the lack of progressive disclosure (no bundle files, everything inline) and the absence of explicit error-recovery feedback loops for failed operations.

Suggestions

Move the proxy request flag table and detailed clientAction field reference into a separate reference file (e.g. references/proxy.md) and link to it from the body to improve progressive disclosure.

Add an explicit validate/feedback loop for CONFIGURATION_ERROR and SETUP_FAILED states (e.g. 'read the error field, fix the cause, re-run connection ensure') rather than only 'check the error field for details'.

Trim mild padding such as 'so you can focus on the integration logic rather than auth plumbing' to keep every token earning its place.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete CLI commands and minimal over-explanation of concepts Claude already knows, though a few lines ('Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic') are slightly padded.	4 / 5
Actionability	It provides copy-paste-ready, executable bash commands for install, login, connection, action discovery, action execution, and proxy requests, covering the common cases with specific flags and JSON output examples.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-checking checkpoints (READY / BUILDING / CLIENT_ACTION_REQUIRED) and a poll loop, but it lacks an explicit validate-then-fix feedback loop for failed actions or CONFIGURATION_ERROR recovery beyond 'check the error field'.	4 / 5
Progressive Disclosure	There are no bundle files (references/scripts/assets) and the body is a single inline document; while it is sectioned, the reference to external docs (https://developers.signiflow.com/) is not clearly signaled as a progressive-disclosure path and bulk content is inline rather than split.	3 / 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 is third-person and includes an explicit 'Use when...' trigger, which is good, but its listed actions ('Manage data, records, and automate workflows') are generic and abstract rather than concrete capabilities. It reads as boilerplate Membrane integration text rather than skill-specific guidance.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete SigniFlow actions such as 'send documents for signature, track signing status, manage templates, and retrieve signed records'.

Add natural user trigger phrases like 'when the user wants to send a document for e-signature, check signature status, or manage SigniFlow documents'.

Tighten the 'when' clause to reference the actual domain events (e-signature, document signing) rather than the generic phrase 'interact with SigniFlow data'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('SigniFlow integration') and a few generic actions ('Manage data, records, and automate workflows'), but these actions are abstract rather than concrete capabilities, matching the anchor that names the domain with minimal/generic actions.	3 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with SigniFlow data'), and the explicit 'Use when...' clause lifts completeness above 3, though the 'when' could be more specific.	4 / 5
Trigger Term Quality	'SigniFlow data' and 'records' are relevant but the description lacks common synonyms or natural user phrases beyond the product name, fitting the anchor with some relevant keywords but missing common variations.	3 / 5
Distinctiveness Conflict Risk	The SigniFlow product name gives it a clear niche with distinct triggers, leaving only minor overlap risk with generic data-management 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/signiflow/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.