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

digiteal

Digiteal integration. Manage data, records, and automate workflows. Use when the user wants to interact with Digiteal 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/digiteal/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 highly actionable with concrete, executable CLI commands and a mostly clear workflow including state-based polling checkpoints. Its main weaknesses are a slightly padded marketing intro and an incoherent step-numbering scheme ("skip to Step 2" with no Step 2) that breaks workflow sequencing.

Suggestions

Fix the broken step numbering: either label the post-connection section as "Step 2" or replace the "skip to Step 2" references with concrete anchor text (e.g. "skip to Searching for actions").

Trim the marketing intro ("Digiteal is a secure platform... used by businesses and individuals who need a reliable way...") to a one-line factual description; Claude does not need the platform pitch.

Consider moving the proxy flags table and the detailed clientAction spec into a separate reference file linked from the body to improve progressive disclosure and token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete commands and minimal concept explanation, but the marketing-style intro ("Digiteal is a secure platform... used by businesses and individuals") and phrases like "so you can focus on the integration logic rather than auth plumbing" are over-explanation that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready, executable membrane CLI commands throughout — install, login, connection ensure, action list/run with --input JSON, and a full proxy flags table — covering the common cases with concrete examples.	5 / 5
Workflow Clarity	There is a clear install→login→connect→poll→search→run sequence with a polling feedback loop and state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but the broken "skip to Step 2" reference (with no labeled Step 2 and an orphaned "1b.") introduces a sequence gap that keeps it below the top anchor.	4 / 5
Progressive Disclosure	The body is well organized into clear sections with an external docs link and no nested references, but with no bundle files the inlined proxy-flags table and clientAction detail sit inline rather than in one-level-deep reference files, so it falls just short of the clean overview-with-signaled-references anchor.	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 successfully pairs a clear capability statement with an explicit "Use when" trigger, but its actions are generic and trigger phrasing lacks concrete synonyms or variations. It is mostly distinct due to the Digiteal app name yet would benefit from more specific capability and trigger terms.

Suggestions

Replace generic verbs ("Manage data, records") with concrete Digiteal-specific actions such as "send and sign documents, create templates, manage workspaces and users".

Expand the trigger clause with concrete user phrases, e.g. "Use when the user wants to send or sign documents, create templates, or manage Digiteal workspaces and users".

Add natural synonyms / file-format-style triggers (e.g. contracts, invoices, e-signatures) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain plus a couple of actions, but "manage" is generic and the action list is not comprehensive, matching the anchor that names a domain with 1-2 concrete actions.	3 / 5
Completeness	It states a clear "what" (manage data/records, automate workflows) and an explicit "Use when the user wants to interact with Digiteal data" clause, but the trigger guidance could be more concrete, matching the anchor where both what and when are present yet when could be more specific.	4 / 5
Trigger Term Quality	The main natural trigger is "interact with Digiteal data" plus the app name itself; common synonyms and variations are missing, fitting the anchor for some relevant keywords without full coverage.	3 / 5
Distinctiveness Conflict Risk	The named app "Digiteal" plus a Digiteal-specific trigger gives a clear niche with low conflict risk, though the generic verbs (manage data/records) leave minor overlap risk with related 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/digiteal/SKILL.md
Commit: f484c82

Reviewed: 1 day 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.