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

Blog Docs Log in Get started

digio

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

Quality

63%

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

Quality

Content

68%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 an efficient, command-driven integration guide with strong actionability and reasonable structure. Its main weaknesses are a broken step-numbering scheme and missing validation feedback loops for destructive proxy operations.

Suggestions

Fix the broken step references: label the connection section '1a'/'1b' or remove the dangling 'skip to Step 2' so the workflow is unambiguous.

Add a validation/verification checkpoint for destructive proxy requests (e.g., 'For POST/PUT/DELETE, confirm with `membrane request ... --method GET` that the change applied before proceeding') to satisfy the destructive-operation feedback-loop requirement.

Tighten the intro paragraph and remove the 'Popular actions' duplication of 'Searching for actions' to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean — command blocks and a flags table carry the load with little padding — but the opening 'Digio is a platform that automates document signing...' paragraph and the aside 'so you can focus on the integration logic rather than auth plumbing' could be trimmed. It is efficient enough to clear 3 but not perfectly lean for a 5.	4 / 5
Actionability	It gives concrete, copy-paste-ready commands for every phase (`npm install -g @membranehq/cli@latest`, `membrane connection ensure ...`, `membrane action run ...`, `membrane request ...`) plus a detailed proxy flags table. Minor gaps (unfilled placeholders like CONNECTION_ID and <actionId>) keep it just below fully-turnkey 5.	4 / 5
Workflow Clarity	There is a real sequence with a connection-state checkpoint (poll until READY, handle CLIENT_ACTION_REQUIRED), but the step numbering is broken — 'skip to Step 2' points at a non-existent Step 2 and '1b' has no '1a'. Per the rubric, the proxy section supports destructive methods (PUT/DELETE) with no validation/verification feedback loop, capping this at 3.	3 / 5
Progressive Disclosure	No bundle files exist, so all content is inline in a single well-sectioned SKILL.md (Install, Authentication, Connecting, Searching, Running actions, Proxy, Best practices). Structure is good and navigation is clear, but odd gaps — the bare 'Digio Overview' bullet list and 'Popular actions' duplicating 'Searching for actions' — keep it from a clean 5.	4 / 5
	Total	15 / 20 Passed

Description

57%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 an explicit 'Use when' trigger and a distinct product name, but its capability verbs are generic and lack concrete, comprehensive actions. It is solid but unspecific.

Suggestions

Replace generic verbs with concrete Digio-specific actions (e.g., 'send documents for signature, verify signer identity, retrieve signed agreements') to lift specificity.

Expand the 'Use when' clause with concrete trigger phrases users would actually say, such as 'e-sign documents, signature requests, or Digio verification'.

Add file-type or keyword synonyms (e.g., 'e-sign', 'document signing', 'Digio agreements') to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the Digio domain but its actions are generic — 'Manage data, records, and automate workflows' lists objects rather than concrete capabilities like 'extract', 'fill', or 'merge'. It does not reach the 3-anchor's '1-2 concrete actions' bar because the verbs remain abstract.	2 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Digio data'), so it clears the missing-trigger cap of 3. It is not a 5 because the 'when' clause is generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	The only natural keyword is the product name 'Digio' in 'interact with Digio data'; it lacks common variations or synonyms users might say. It is above a 2 because the product name is a genuine trigger, but below 4 due to the thin, generic phrasing.	3 / 5
Distinctiveness Conflict Risk	The 'Digio' product name gives it a clear niche with low conflict risk, but the generic action verbs ('manage data', 'automate workflows') leave minor overlap risk with adjacent data skills, keeping it just below the 5-anchor's distinct concrete triggers.	4 / 5
	Total	13 / 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/digio/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.