1msg
1msg integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1msg data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill 1msg61
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
40%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 relies heavily on the '1msg' product name for identification but fails to explain what 1msg actually does or what specific capabilities the skill provides. The vague terms 'data', 'records', and 'workflows' offer no meaningful differentiation and don't help Claude understand when this skill is appropriate versus other data management or automation skills.
Suggestions
Replace vague terms with specific actions: instead of 'manage data, records', specify what 1msg does (e.g., 'Send WhatsApp messages, manage contact lists, track message delivery status').
Add natural trigger terms users would actually say, such as 'WhatsApp API', 'messaging automation', 'chat campaigns', or whatever 1msg's actual domain is.
Expand the 'Use when' clause with specific scenarios: 'Use when the user mentions WhatsApp business messaging, bulk SMS, or chat automation' rather than the circular '1msg data'.
| 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 abstract terms that could apply to almost any integration. | 1 / 3 |
Completeness | Has a 'Use when' clause which addresses the 'when' question, but the 'what' is extremely vague. The trigger condition 'interact with 1msg data' is circular and doesn't provide meaningful guidance on specific use cases. | 2 / 3 |
Trigger Term Quality | Includes '1msg' as a specific product name which is a relevant trigger, but lacks natural variations users might say (e.g., messaging, WhatsApp API, chat automation). The generic terms 'data', 'records', 'workflows' are too broad to serve as effective triggers. | 2 / 3 |
Distinctiveness Conflict Risk | The '1msg' product name provides some distinctiveness, but 'manage data, records, and automate workflows' is generic enough to overlap with many other integration or automation skills. Only the product name prevents a score of 1. | 2 / 3 |
Total | 7 / 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 1msg integration via Membrane, with good coverage of common operations. However, it suffers from some unnecessary introductory text, an unhelpful overview section, and a popular actions table with empty descriptions. The workflow lacks validation checkpoints and error recovery guidance.
Suggestions
Remove the introductory paragraph explaining what 1msg is (Claude can infer this) and the cryptic 'Conversation > Message' overview
Either populate the descriptions in the popular actions table or remove actions without descriptions to reduce noise
Add validation steps after key operations (e.g., 'Verify connection succeeded: membrane connection list --json | grep CONNECTION_ID')
Include error handling guidance: what to do if authentication fails, connection times out, or actions return errors
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'designed for businesses and individuals who want to streamline their communication') and the overview section is sparse yet the overall document could be tighter. The popular actions table has empty descriptions which adds bulk without value. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, including examples for authentication, connection setup, action discovery, and proxy requests. Commands are copy-paste ready with proper flags documented. | 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 connection fails, how to verify successful authentication). The workflow assumes success without verification steps. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the popular actions table with empty descriptions adds clutter. Could benefit from linking to external references for detailed API documentation rather than inline content. The overview section ('Conversation > Message') is cryptic and unhelpful. | 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 | |
- 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.