1msg
1msg integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1msg data.
52
58%
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/1msg/SKILL.mdQuality
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 follows a generic integration template pattern without providing meaningful specifics about what 1msg is or what concrete actions the skill enables. While it includes a 'Use when' clause and the product name as a trigger, the vague capability language ('manage data, records, and automate workflows') could apply to virtually any integration skill, making it difficult for Claude to confidently select this skill in the right context.
Suggestions
Replace generic terms like 'manage data, records, and automate workflows' with specific 1msg capabilities (e.g., 'send WhatsApp messages, manage contacts, configure chatbots, track message delivery').
Add context about what 1msg is (e.g., 'WhatsApp Business API platform') so Claude can match user requests about WhatsApp messaging or chat automation to this skill.
Expand trigger terms in the 'Use when' clause with natural phrases users might say, such as 'WhatsApp integration', 'messaging API', or specific 1msg features.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying any concrete actions. It doesn't explain what 1msg is or what specific operations can be performed (e.g., send messages, manage contacts, track conversations). | 1 / 3 |
Completeness | It has a 'Use when...' clause ('Use when the user wants to interact with 1msg data'), so it technically addresses both what and when. However, the 'when' is essentially a restatement of the 'what' and provides no additional trigger guidance beyond mentioning '1msg'. | 2 / 3 |
Trigger Term Quality | It includes '1msg' as a trigger term which is specific to the integration, but 'data', 'records', and 'workflows' are overly generic terms that users are unlikely to naturally associate with 1msg specifically. Missing natural terms users might say when needing this skill. | 2 / 3 |
Distinctiveness Conflict Risk | '1msg' as a product name provides some distinctiveness, but the generic terms 'manage data, records, and automate workflows' could easily overlap with dozens of other integration skills. Without specifying what 1msg actually does (e.g., WhatsApp messaging, chat automation), it's hard to distinguish from other CRM or messaging integrations. | 2 / 3 |
Total | 7 / 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 is a solid integration skill with excellent actionability and workflow clarity — every step has executable commands and the connection state machine is well-documented with explicit feedback loops. The main weaknesses are moderate verbosity (introductory fluff, empty table descriptions) and a monolithic structure that could benefit from trimming or splitting.
Suggestions
Remove the introductory paragraph explaining what 1msg is — Claude doesn't need this context to use the integration.
Either populate the Description column in the popular actions table or remove it entirely; empty cells waste tokens without adding value.
Trim the 'Conversation → Message' overview section which provides no actionable information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanations (e.g., 'It's designed for businesses and individuals who want to streamline their communication across multiple channels') and the popular actions table has empty description fields, wasting tokens. The Membrane CLI setup and auth flow are reasonably concise but could be tighter. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear parameter placeholders. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, etc.) and feedback loops (poll again after user action). The progression from install → authenticate → connect → discover actions → run actions is well-structured with validation at each stage. | 3 / 3 |
Progressive Disclosure | The content is reasonably organized with clear sections, but it's somewhat monolithic for its length. The popular actions table with empty descriptions adds bulk without value. No bundle files are referenced for advanced topics, though the external API docs link is provided. | 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.