Name: treezor
Rating: 59.2 (1 reviews)
Author: membranedev

treezor

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

Quality

68%

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

Quality

Content

76%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 CLI commands and a clear connection workflow, and it is well-structured for a single self-contained file. Its main gap is the absence of validation/confirmation checkpoints for destructive financial operations like payouts and transfers.

Suggestions

Add an explicit validation/confirmation step before running irreversible actions (payouts, transfers, card issuance), e.g. 'Confirm the amount and beneficiary with the user before running payout actions.'

Fix the dangling 'Step 2' references by adding a clearly labeled '## Step 2: Discover and run actions' section or removing the cross-reference.

Trim the 'rather than auth plumbing' aside and the 'Use action names and parameters as needed.' filler to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-and-code listings, with minor padding such as 'so you can focus on the integration logic rather than auth plumbing' and the filler line 'Use action names and parameters as needed.' that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready executable commands covering install, auth (including headless), connection, action search, action execution, and proxy requests, plus a flags table — specific examples cover the common cases.	5 / 5
Workflow Clarity	The connect-to-poll sequence is well branched on connection state, but the skill covers destructive money-moving actions (payouts, transfers) with no pre-execution validation or confirmation checkpoints, which caps workflow clarity at 3; the dangling 'Step 2' reference also lacks a matching section.	3 / 5
Progressive Disclosure	No bundle files exist and the ~150-line body is organized into clear headed sections with all content inline and no nested references; structure is good, though the detailed clientAction state machine could be split into a reference file.	4 / 5
	Total	16 / 20 Passed

Description

61%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 cleanly answers both what and when and targets a distinct niche, but its capability list is generic ('manage data, records, automate workflows') rather than naming Treezor's concrete actions. Tightening the action list would lift specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Treezor capabilities, e.g. 'Issue cards, process payins/payouts, manage wallets and beneficiaries'.

Expand the trigger clause with natural user phrasings like 'when the user mentions Treezor cards, wallets, payouts, or transfers'.

Drop the filler 'Manage data, records' phrasing which adds length without specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Treezor integration') but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete API capabilities like issuing cards or processing payments.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Treezor data') are present, though the 'what' is generic rather than concrete.	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with Treezor data' surfaces the key keyword (Treezor) but offers no synonyms or common phrasing variations beyond the single product name.	3 / 5
Distinctiveness Conflict Risk	'Treezor integration' anchored to a specific Banking-as-a-Service product with a distinct trigger phrase makes conflict with other skills minimal.	5 / 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/treezor/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.