2chat
2Chat integration. Manage data, records, and automate workflows. Use when the user wants to interact with 2Chat data.
58
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/2chat/SKILL.mdQuality
Discovery
57%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 benefits from having an explicit 'Use when' clause and naming the specific product (2Chat), but it is severely lacking in specificity about what 2Chat actually does and what concrete actions the skill enables. The generic terms 'data', 'records', and 'workflows' provide almost no discriminating information for skill selection among many possible integrations.
Suggestions
Replace generic terms like 'manage data, records, and automate workflows' with specific 2Chat capabilities (e.g., 'send WhatsApp messages, manage chat contacts, retrieve conversation history').
Add natural trigger terms users would actually say, such as 'WhatsApp', 'messaging', 'chat automation', or other 2Chat-specific features to improve keyword matching.
Expand the 'Use when' clause with more specific trigger scenarios, e.g., 'Use when the user mentions 2Chat, WhatsApp messaging, or chat-based customer communication.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying concrete actions. It doesn't explain what kind of data, what records, or what workflows — these are generic terms that could apply to almost any integration. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (when the user wants to interact with 2Chat data) with an explicit 'Use when' clause, even though both parts are vague in substance. | 3 / 3 |
Trigger Term Quality | It includes '2Chat' as a specific product name which is a useful trigger term, but 'data', 'records', and 'workflows' are overly generic. It lacks natural terms users might say when needing this skill, such as messaging, WhatsApp, chat automation, or other 2Chat-specific features. | 2 / 3 |
Distinctiveness Conflict Risk | The '2Chat' product name provides some distinctiveness, but 'manage data, records, and automate workflows' is so generic it could overlap with many other integration skills. Without specifying what makes 2Chat unique (e.g., messaging platform, WhatsApp integration), it risks conflicting with other CRM or workflow tools. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable CLI commands for integrating with 2Chat via Membrane, with a well-structured connection workflow including state handling and feedback loops. However, it includes some unnecessary introductory explanation, has a cryptically unhelpful overview section, and could benefit from better structural organization or splitting into supporting files for a skill of this length.
Suggestions
Remove the introductory paragraph explaining what 2Chat is — Claude already knows this and it wastes tokens.
Expand or remove the '2Chat Overview' section (Conversation → Message → User) — it's too sparse to be useful and doesn't provide actionable guidance.
Consider splitting the proxy requests reference table and best practices into a separate reference file to improve progressive disclosure for this longer skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes some unnecessary explanation (e.g., ' 2Chat is a live chat and chatbot platform for websites. It allows businesses to engage with their website visitors in real-time and automate customer support.' is something Claude already knows or can infer). The overview section with 'Conversation → Message → User' is cryptically brief yet unhelpful. The proxy request table and best practices are reasonably concise, but overall there's room to tighten. | 2 / 3 |
Actionability | The skill provides concrete, executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear flag descriptions and JSON output options. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, error states) and feedback loops (poll until ready, handle client actions, re-check). The progression from connection setup → action discovery → action execution → proxy fallback is well-structured with validation at each stage. | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to supporting files, despite being fairly long (~120 lines of content). The overview section ('Conversation → Message → User') is too sparse to be useful as a structural overview. The proxy request section and best practices could potentially be separated, but more importantly, the overview section fails to provide meaningful navigation or structure. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- membranedev/application-skills
- Commit
f484c82
- 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.