1s2u
1S2U integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1S2U data.
53
60%
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/1s2u/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 referencing a specific product name (1S2U) and includes an explicit 'Use when' clause, which provides structural completeness. However, the capabilities described are extremely vague—'manage data, records, and automate workflows' could apply to virtually any integration tool. The description would be significantly improved by listing concrete actions specific to the 1S2U platform.
Suggestions
Replace vague terms like 'manage data, records, and automate workflows' with specific 1S2U actions (e.g., 'send SMS messages, check delivery status, manage contact lists, configure auto-replies').
Expand trigger terms in the 'Use when' clause to include natural user phrases and specific 1S2U features (e.g., 'Use when the user mentions 1S2U, SMS gateway, bulk messaging, or delivery reports').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying any concrete actions. There are no specific capabilities listed—what kind of data? What records? What workflows? This is essentially abstract language. | 1 / 3 |
Completeness | The description does answer both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with 1S2U data), with an explicit 'Use when...' clause. While the content is vague, the structural completeness requirement is met. | 3 / 3 |
Trigger Term Quality | The term '1S2U' is a specific product/service name that would naturally appear in user requests, which is helpful. However, the remaining terms ('data', 'records', 'workflows') are extremely generic and wouldn't help distinguish this skill from dozens of others. | 2 / 3 |
Distinctiveness Conflict Risk | The '1S2U' brand name provides some distinctiveness, but 'manage data, records, and automate workflows' is so generic it could overlap with many integration or data management skills. The specificity of the product name helps but the vague capability description weakens distinctiveness. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides strong, actionable CLI commands and a well-structured connection workflow with proper state handling and error recovery. However, it is significantly undermined by the useless portal overview section (generic website navigation), the 'I don't have enough information' disclaimer, and other filler content that wastes tokens without adding value. Removing the noise would make this a solid skill.
Suggestions
Remove the 'I'm sorry, but I don't have enough information' paragraph entirely — it provides no value and wastes tokens.
Remove or drastically reduce the '1S2U Overview' portal navigation section — listing generic website sections like News, Events, Careers, Login/Logout is not actionable and Claude doesn't need this information.
Tighten the 'Working with 1S2U' intro paragraph — 'Membrane handles authentication and credentials refresh automatically' is sufficient without 'so you can focus on the integration logic rather than auth plumbing'.
Consider extracting the detailed connection state handling (CLIENT_ACTION_REQUIRED sub-types, error states) into a referenced file to keep the main skill leaner.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes a self-deprecating 'I don't have enough information' paragraph, a portal overview section that lists generic website navigation (News, Events, Tenders, Careers, Login, Logout) with no actionable value, and explains concepts like authentication flows in excessive detail. The portal overview is entirely useless filler. | 1 / 3 |
Actionability | The skill provides fully executable CLI commands for installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear parameter placeholders and JSON output flags. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, error states), polling instructions with --wait flag, and clear branching logic for each state. The discover-then-run workflow is also well-structured. | 3 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's somewhat monolithic — the proxy request options table, connection state handling details, and the useless portal overview could be better organized or split out. No bundle files are referenced despite the content length warranting it. | 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
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.