Name: dixa
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

dixa

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

Quality

74%

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/dixa/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 content is an actionable, command-driven CLI integration guide with real feedback loops for connection state. Weaknesses are minor: a little explanatory padding and an inconsistent step-numbering scheme that slightly muddies the workflow sequence.

Suggestions

Fix the step numbering: label the post-connection section as "Step 2" explicitly or drop the "1b"/"Step 2" references in favor of a single consistent numbered flow.

Tighten prose like "so you can focus on the integration logic rather than auth plumbing" and the token-burn rationale to keep only what Claude cannot infer.

Consider splitting the verbose connection-state reference (clientAction fields, polling rules) into a short inline checklist to improve scanability.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands and tables with brief context; minor over-explanation like "so you can focus on the integration logic rather than auth plumbing" and the token-burn rationale in best practices could be trimmed, fitting the efficient-with-minor-padding anchor.	4 / 5
Actionability	It gives copy-paste-ready commands throughout (install, login, connection ensure/get with --wait, action list/run with --input, request proxy with a full flag table) covering the common cases, matching the fully-executable anchor.	5 / 5
Workflow Clarity	A clear install→auth→connect→search→run sequence exists with polling feedback loops (BUILDING→READY, CLIENT_ACTION_REQUIRED→re-poll), but the "Step 2"/"1b" numbering references a Step 2 that is never labeled and the search/run steps are not explicitly numbered, leaving minor sequencing gaps.	4 / 5
Progressive Disclosure	No bundle files exist; the single SKILL.md is organized under clear headers (Overview, Working with Dixa, Searching, Popular actions, Proxy, Best practices) with content appropriately inline for a CLI skill, though the detailed connection-state handling could justify its own section for a 5.	4 / 5
	Total	17 / 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 is third-person, concise, and provides an explicit Use-when trigger tied to a distinct platform niche. Its main weakness is generic action verbs and limited trigger-term variation, which keep specificity and trigger quality at mid-range.

Suggestions

Replace generic verbs with concrete Dixa actions, e.g. "Search and send conversations, manage users and messages, automate ticket workflows".

Expand the trigger clause with natural phrasings users would say, e.g. "Use when the user wants to search Dixa conversations, send messages, or manage tickets and users".

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Dixa domain plus a couple of actions, but the verbs (manage, automate) are generic and coverage is not comprehensive, matching the 1-2 concrete actions anchor rather than the multi-action 5.	3 / 5
Completeness	It states a clear "what" (manage data, records, automate workflows) and an explicit "when" ("Use when the user wants to interact with Dixa data"), but the when-clause is a single phrase that could be more specific, fitting the 4 rather than the concrete-multi-trigger 5.	4 / 5
Trigger Term Quality	"Dixa", "data", "records", "workflows", and "interact with Dixa data" surface the core keyword, but common variations or synonyms are absent, landing at the some-relevant-keywords-but-missing-variations anchor.	3 / 5
Distinctiveness Conflict Risk	"Dixa integration" with the Dixa-named trigger carves a clear niche with minimal overlap risk against other skills, matching the distinct-triggers anchor.	5 / 5
	Total	15 / 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/dixa/SKILL.md
Commit: f484c82

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