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

directa24

Directa24 integration. Manage data, records, and automate workflows. Use when the user wants to interact with Directa24 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

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/directa24/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 a strong, command-driven integration guide with copy-pasteable CLI examples and an explicit connection-readiness feedback loop. The main weaknesses are minor: a duplicated action-list command, inconsistent step labels in the workflow, and a loose overview entity list.

Suggestions

Remove the duplicated `membrane action list` invocation (the Popular actions section repeats the searching-for-actions command) to tighten conciseness.

Fix the workflow step labels so "1b" and the referenced "Step 2" are part of a single consistent numbered sequence (e.g. 1. ensure, 2. wait/branch, 3. discover actions, 4. run).

Either give the Overview entity tree (Account/Transaction/Help Center/Article) a purpose (e.g. link to where each is discovered) or drop it to remove the loose end.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-driven with a compact flag table and almost no concept padding, but the duplicated `action list` invocation (searching-for-actions and Popular actions) and the vague entity overview list (Account/Transaction/Help Center/Article) could be trimmed, fitting the 'efficient, minor trimmable instances' anchor rather than a fully lean 5.	4 / 5
Actionability	It provides fully copy-pasteable commands across install, login (including headless `login complete <code>`), connection ensure, `--wait` polling, action list/run with JSON input, and proxy requests with a complete flag table, covering the common cases, matching the 'fully executable, copy-paste ready' anchor.	5 / 5
Workflow Clarity	The connection-readiness flow is sequenced with an explicit feedback loop (ensure -> check state -> poll with --wait -> branch on CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR -> re-poll after user acts), but the step labels are inconsistent ("#### 1b" and an undefined "Step 2"), a minor sequencing gap that keeps it just below the full-checklist 5.	4 / 5
Progressive Disclosure	As a single-file skill with no bundle files, it is organized under clear headers (Overview, Working with Directa24, Popular actions, Proxy, Best practices) and navigable, but the Overview entity list points to nothing and there is no one-level-deep reference structure, fitting the 'good structure, minor organization gaps' anchor rather than a well-signaled-reference 5.	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 what-statement with an explicit Use-when trigger and is anchored to the distinct Directa24 niche. It is held back by generic action verbs and a thin set of natural trigger terms that miss common payment/transaction synonyms.

Suggestions

Replace generic verbs with specific Directa24 actions, e.g. "Create and track payments, manage deposits, and query transaction records" to lift specificity.

Add natural trigger phrases a user would actually say, e.g. "Use when the user wants to create or check Directa24 payments, deposits, or transaction status in LATAM."

Name the LATAM payment context in the trigger so it is distinguishable from generic data-integration skills.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain plus a couple of concrete-ish actions, but "manage data/records" is generic rather than a comprehensive list of specific actions, matching the anchor for 1-2 concrete actions.	3 / 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 Directa24 data"), but the when-clause is generic rather than concrete, fitting the 'both present, when could be more specific' anchor and falling short of explicit concrete triggers (5).	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Directa24 data" provides a trigger anchored on "Directa24", but it misses natural synonyms a user would say (payments, transactions, deposits, LATAM payouts), matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The Directa24 name gives the skill a clear niche with minimal conflict risk, but the generic action verbs (manage data, records, automate workflows) create minor overlap with broad data skills, fitting the 'mostly distinct, minor overlap' anchor rather than the fully-distinct 5.	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/directa24/SKILL.md
Commit: f484c82

Reviewed: ~18 hours 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.