1msg
1msg integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1msg data.
61
52%
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/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 is too vague and generic to be effective for skill selection. While it names the integration (1msg), it fails to describe what 1msg actually is or what specific capabilities the skill provides. The 'Use when' clause is circular and doesn't add meaningful trigger information beyond the skill name.
Suggestions
Add specific concrete actions that describe what 1msg does (e.g., 'Send WhatsApp messages, manage contacts, track message delivery status' if that's what 1msg handles).
Expand the 'Use when...' clause with natural trigger terms users would actually say, such as the specific platform or service 1msg connects to (e.g., 'Use when the user mentions 1msg, WhatsApp API, messaging automation, or bulk messaging').
Replace generic phrases like 'manage data, records, and automate workflows' with domain-specific capabilities that distinguish this from other integration skills.
| 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 kind of data, what records, or what workflows are involved. | 1 / 3 |
Completeness | It has a weak 'what' (manage data, records, automate workflows) and a 'when' clause ('Use when the user wants to interact with 1msg data'), but the 'when' is essentially circular—it just restates the skill name without providing meaningful trigger guidance. | 2 / 3 |
Trigger Term Quality | It includes the term '1msg' which is the specific integration name and would be a natural keyword. However, it lacks any other natural terms users might say (e.g., messaging, WhatsApp, chat, SMS) that would help identify when this skill is relevant. | 2 / 3 |
Distinctiveness Conflict Risk | The '1msg' brand name provides some distinctiveness, but 'manage data, records, and automate workflows' is extremely generic and could overlap with dozens of other integration skills. Without specifying what 1msg actually does (e.g., WhatsApp messaging), it's hard to distinguish from other data management integrations. | 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 is a functional integration skill with strong actionability — all CLI commands are concrete and executable. However, it suffers from some verbosity (introductory fluff, empty table descriptions) and could benefit from a clearer end-to-end workflow summary. The progressive disclosure is adequate for the content volume but the popular actions table with blank descriptions wastes tokens without adding value.
Suggestions
Remove the introductory paragraph explaining what 1msg is — Claude doesn't need this context, and the user already knows what they want to do.
Either add descriptions to the popular actions table or remove it entirely — empty description columns waste tokens and provide no actionable guidance.
Add a brief numbered workflow overview at the top (e.g., 1. Install CLI → 2. Authenticate → 3. Connect → 4. Discover actions → 5. Run) to improve workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'It's designed for businesses and individuals who want to streamline their communication across multiple channels' is fluff Claude doesn't need). The popular actions table has empty description fields, wasting tokens. The Membrane CLI boilerplate is reasonably efficient but could be tighter. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, running actions with parameters. Each command is specific and executable. | 3 / 3 |
Workflow Clarity | The workflow for creating and polling actions includes state checking and error states, which is good. However, the overall flow (install → auth → connect → discover → run) is spread across sections without a clear sequential overview or validation checkpoints between steps. The action creation polling loop is well-documented but the broader workflow lacks explicit verification steps. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's somewhat monolithic — all content is inline in one file. The popular actions table with empty descriptions adds bulk without value. References to external docs (1msg API) are present but there's no splitting of advanced content into separate files. | 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
56d7336
- 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.