2chat
2Chat integration. Manage data, records, and automate workflows. Use when the user wants to interact with 2Chat data.
72
66%
Does it follow best practices?
Impact
Pending
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
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description adequately identifies the 2Chat integration and includes an explicit 'Use when' clause, which is good. However, it lacks specific concrete actions (what exactly can be managed or automated?) and misses natural trigger terms users might use when needing this skill. The generic verbs 'manage' and 'automate' don't help Claude understand the actual capabilities.
Suggestions
Replace vague verbs with specific actions like 'send WhatsApp messages, manage contacts, view conversation history, create broadcast lists'
Add natural trigger terms users might say: 'WhatsApp', 'messaging', 'chat', 'contacts', 'broadcasts', or specific 2Chat feature names
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (2Chat) and mentions general actions ('Manage data, records, and automate workflows'), but these are not concrete specific actions - 'manage' and 'automate' are vague verbs without specifics like 'send messages', 'create contacts', or 'schedule broadcasts'. | 2 / 3 |
Completeness | Has both 'what' (manage data, records, automate workflows) and 'when' (explicit 'Use when the user wants to interact with 2Chat data'), meeting the requirement for explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes '2Chat' as a key trigger term and 'data', 'records', 'workflows', but lacks natural variations users might say like 'WhatsApp', 'messaging', 'chat automation', or specific 2Chat features. | 2 / 3 |
Distinctiveness Conflict Risk | '2Chat' is a specific product name which helps distinctiveness, but 'manage data, records, and automate workflows' is generic enough to potentially conflict with other CRM or automation skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
64%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 2Chat integration via Membrane, with good executable examples and a useful options table. However, it lacks validation checkpoints in workflows, has an incomplete overview section that adds no value, and could be more concise by removing explanatory text about what Membrane does.
Suggestions
Remove or complete the '2Chat Overview' section - currently it lists entities without any actionable information
Add error handling guidance and validation steps (e.g., 'If connection fails, check X' or 'Verify connection with membrane connection list')
Trim explanatory text like 'Membrane handles authentication and credentials refresh automatically' - Claude knows what auth handling means
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary explanation (e.g., 'This skill uses the Membrane CLI to interact with 2Chat. Membrane handles authentication...' could be trimmed). The 2Chat overview section is too sparse to be useful yet takes up space. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with clear syntax examples. Commands are copy-paste ready with proper flags and JSON output options documented in a useful table format. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack explicit validation checkpoints. No feedback loops for error recovery - e.g., what to do if 'membrane connect' fails or if action run returns an error. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but the '2Chat Overview' section is incomplete (just lists Conversation/Message/User with no explanation). Links to official docs but no internal file references for advanced topics. | 2 / 3 |
Total | 9 / 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
d19a82b
- 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.