CtrlK
BlogDocsLog inGet started
Tessl Logo

unione

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

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/unione/SKILL.md
SKILL.md
Quality
Evals
Security

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 content is highly actionable with executable commands and a well-validated connection workflow. Its weaknesses are mild padding/redundancy and the absence of an output-verification step after running actions.

Suggestions

Trim the introductory UniOne description and remove filler like 'Use action names and parameters as needed.' to recover tokens.

Add an explicit verification step after 'membrane action run' (e.g., check the response 'output'/'error' fields and retry or surface errors) to close the workflow validation gap.

De-duplicate the 'membrane action list' command, which appears in both 'Searching for actions' and 'Popular actions'.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands, but includes unnecessary padding such as the introductory 'Think of it as a communication platform...' sentence, the filler line 'Use action names and parameters as needed.', and repeated membrane action list invocations.

3 / 5

Actionability

It provides copy-paste ready, fully executable commands across the whole workflow (install, login, connection ensure/get with --wait, action list/run, request proxy) plus a concrete flags table, covering the common cases.

5 / 5

Workflow Clarity

The connection setup is a clear sequence with explicit state-based validation and a feedback loop (poll until READY, branch on CLIENT_ACTION_REQUIRED, re-poll after action), but the run-action step lacks an explicit verification of output success, leaving a minor validation gap.

4 / 5

Progressive Disclosure

Content is well organized into clearly signaled sections (Overview, Install, Authentication, Connecting, Searching, Actions, Proxy, Best practices) with no nested references, though the full action-category enumeration and flags table are inlined rather than split into a reference file.

4 / 5

Total

16

/

20

Passed

Description

66%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 identifies a distinct named product and includes an explicit 'Use when' trigger, satisfying both what and when. Its main weakness is generic action language and thin trigger-term coverage beyond the product name.

Suggestions

Replace generic verbs ('Manage data, records') with concrete UniOne capabilities such as 'send transactional and marketing email, SMS, and Viber messages'.

Broaden the trigger clause with natural user terms, e.g., 'Use when the user wants to send or automate email, SMS, Viber, or other UniOne messages.'

DimensionReasoningScore

Specificity

Names the UniOne domain and lists a few action phrases ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, matching the anchor for naming a domain with 1-2 non-comprehensive actions.

3 / 5

Completeness

It explicitly answers both 'what' (UniOne integration; manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with UniOne data'), but the 'when' clause is somewhat generic and could be more specific.

4 / 5

Trigger Term Quality

The trigger relies almost entirely on the proper noun 'UniOne' and 'interact with UniOne data', with no synonyms or related natural terms (e.g., email, SMS, messaging), so relevant keywords are present but common variations are missing.

3 / 5

Distinctiveness Conflict Risk

UniOne is a specific named product, giving the skill a clear niche with distinct triggers and minimal risk of firing for the wrong skill.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.