Name: chatra
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

chatra

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

Quality

70%

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/chatra/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 well-structured, actionable guide with executable Membrane commands and a solid connection-state feedback loop. Its main weaknesses are a dangling 'Step 2' reference, no validation guidance for destructive action runs, and slight padding in the intro prose.

Suggestions

Fix the dangling 'skip to Step 2' reference by labeling the workflow steps (e.g. 'Step 1: Connect', 'Step 2: Search and run actions').

Add a validation/check step before running destructive actions such as delete-pushed-message or delete-agent-message (e.g. retrieve-then-confirm before delete).

Trim the opening product description and the 'so you can focus on the integration logic rather than auth plumbing' clause to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and tables, and most prose is Membrane/Chatra-specific rather than general knowledge; minor over-explanation such as 'so you can focus on the integration logic rather than auth plumbing' and the opening product pitch could be trimmed. Not a 5 because of those small padded passages.	4 / 5
Actionability	It provides copy-paste ready, executable commands for the common cases (install, login, connection ensure, action list, action run, request proxy) with flags and JSON examples. Not below 5 because the guidance is concrete and covers the typical workflow end-to-end.	5 / 5
Workflow Clarity	There is a clear install -> login -> connect -> search -> run sequence with an explicit feedback loop for connection state (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll). Not a 5 because the 'skip to Step 2' reference is dangling (no labeled Step 2) and destructive actions (delete message) are run without any validation checkpoint.	4 / 5
Progressive Disclosure	Content is well organized into clear sections (Overview, Working with Chatra, Install, Auth, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with the external docs link signaled. Not a 5 because no bundle files exist and the Popular actions table is inline reference material that, at ~165 lines, is not split out.	4 / 5
	Total	17 / 20 Passed

Description

57%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 includes an explicit 'Use when' trigger and a distinguishable brand name, but its capability list is generic and lacks concrete Chatra-specific actions. It reads as a templated Membrane integration description rather than a tailored skill summary.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Chatra actions such as 'send and edit agent messages, retrieve and update visitor/client profiles, and manage pushed messages'.

Add natural trigger synonyms users actually say, e.g. 'Use when the user wants to send live chat messages, look up visitor/client details, or automate Chatra outreach.'

Differentiate from sibling Membrane skills by leading with Chatra-specific capabilities instead of the shared 'Manage data, records, and automate workflows' boilerplate.

Dimension	Reasoning	Score
Specificity	It names the domain ('Chatra integration') but the actions ('Manage data, records, and automate workflows') are generic and not concrete Chatra capabilities such as sending messages or retrieving visitors; not a 3 because no specific concrete actions are listed.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Chatra data') are present; not a 5 because the 'what' is vague rather than concrete and the trigger phrase is somewhat circular.	4 / 5
Trigger Term Quality	It includes the relevant brand keyword 'Chatra' and 'data'/'records', but misses natural variations or synonyms a user might say (e.g. 'live chat', 'chat with visitors', 'email marketing'); not a 4 because keyword coverage is thin.	3 / 5
Distinctiveness Conflict Risk	The Chatra brand name gives a clear niche with minimal external conflict, but the templated phrasing overlaps with sibling Membrane integration skills that follow the same 'X integration ... interact with X data' pattern; not a 5 because of that template overlap risk.	4 / 5
	Total	13 / 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/chatra/SKILL.md
Commit: f484c82

Reviewed: 3 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.