CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chatra

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

Quality

69%

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/chatra/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

A well-structured, executable skill body: concrete CLI commands, a useful action table, and a clear connection lifecycle with state polling. The main weaknesses are missing verification steps for destructive operations, a broken "Step 2" cross-reference, and interleaved generic Membrane boilerplate that dilutes Chatra-specific guidance.

Suggestions

Add a validation step for destructive and batch operations, e.g. "Before running delete-* actions, run the corresponding get-* action to confirm the target ID, and verify the result in the output field afterward".

Fix the cross-references: define or remove the "skip to **Step 2**" pointer and give the connection section consistent step numbering (1a/1b or Step 1/Step 2).

Standardize on the "membrane" invocation (explaining the one "npx @membranehq/cli" usage) and trim the generic Membrane setup boilerplate to tighten conciseness.

DimensionReasoningScore

Conciseness

The body is dominated by concrete commands and tables with only minor over-explanation ("This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps...") and a grammar slip ("This will burn less tokens"). Every token mostly earns its place, but several boilerplate sentences could be trimmed to reach anchor 5.

4 / 5

Actionability

Commands are copy-paste ready throughout ("membrane connection ensure \"https://chatra.io\" --json", "membrane action run <actionId> --connectionId=CONNECTION_ID --input '{\"key\": \"value\"}'") with a 10-action table and a proxy flag table. Minor gaps keep it below 5: it says "skip to **Step 2**" but no Step 2 is defined, and it alternates between "membrane" and "npx @membranehq/cli" without explanation.

4 / 5

Workflow Clarity

The install → login → connect → poll → search → run sequence is present with state-polling checkpoints, but destructive actions (delete-pushed-message, delete-agent-message) ship with no validation or verification guidance, capping this dimension per the rubric. The dangling "Step 2" reference and an unnumbered "1b" section further blur the sequence.

3 / 5

Progressive Disclosure

As a single-file skill with no bundle files, content is organized into clear one-level sections (install, auth, connect, search, actions, proxy, best practices) with no nested references. Minor gaps: the generic Membrane CLI setup could live in a shared reference, and the inconsistent step numbering ("1b" with no "1a", undefined "Step 2") slightly hinders navigation.

4 / 5

Total

15

/

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 correctly follows the what/when pattern and anchors on the distinctive Chatra brand, but its capability statement is generic boilerplate. Replacing "Manage data, records, and automate workflows" with concrete Chatra actions and natural trigger phrases would lift it substantially.

Suggestions

Replace the generic phrase "Manage data, records, and automate workflows" with concrete Chatra actions, e.g. "Send and manage live chat messages to website visitors, retrieve and update client records, and edit or delete agent and pushed messages."

Expand the trigger clause with natural user phrases: "Use when the user mentions Chatra, live chat visitors, chat transcripts, or wants to message/look up Chatra clients."

Mention the operation categories users actually ask for (messages, clients, agents) so the description distinguishes itself from generic data-integration skills.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Chatra domain but the actions are generic with no concrete Chatra capabilities (no mention of chats, messages, visitors, or agents). It does not list 1-2 domain-specific concrete actions that would reach anchor 3.

2 / 5

Completeness

Both parts are present: a "what" ("Chatra integration. Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Chatra data"). Not 5 because the "what" is vague rather than a concrete capability listing, and the trigger clause could name more specific use cases.

4 / 5

Trigger Term Quality

"Chatra" is a relevant natural brand keyword, but the remaining terms ("data", "records", "workflows") are generic; common user phrases like "live chat", "chat messages", "visitors", or "help desk" are missing.

3 / 5

Distinctiveness Conflict Risk

The Chatra brand gives it a clear niche with minimal conflict risk, but the generic middle sentence ("Manage data, records, and automate workflows") overlaps with many other data-integration skills if read without the brand name. Not 3 since the explicit Chatra trigger keeps it mostly distinct.

4 / 5

Total

13

/

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.

Validation — 15 / 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

Path

skills/chatra/SKILL.md

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.