1s2u
1S2U integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1S2U data.
73
67%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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 having a clear structure with both a 'what' and 'when' clause, and the specific product name '1S2U' provides some distinctiveness. However, the actual capabilities described are extremely vague—'manage data, records, and automate workflows' could apply to almost any integration skill. The description would be significantly improved by listing specific actions and data types unique to 1S2U.
Suggestions
Replace vague terms like 'manage data, records, and automate workflows' with specific concrete actions (e.g., 'create contacts, send SMS messages, query billing records, set up automated campaigns').
Add domain-specific trigger terms that reflect what 1S2U actually does (e.g., if it's an SMS platform: 'SMS, text messages, bulk messaging, 1S2U API').
Expand the 'Use when...' clause with more specific trigger scenarios (e.g., 'Use when the user mentions 1S2U, needs to send bulk SMS, or wants to query messaging logs').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying any concrete actions. What kind of data? What records? What workflows? These are abstract terms that don't describe specific capabilities. | 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 what is vague, the structure is complete. | 3 / 3 |
Trigger Term Quality | The term '1S2U' is a specific product/service name that would naturally appear in user requests, which is good. However, the remaining terms ('data', 'records', 'workflows') are extremely generic and wouldn't help distinguish this skill. No domain-specific keywords or common variations are provided. | 2 / 3 |
Distinctiveness Conflict Risk | The '1S2U' brand name provides some distinctiveness, but 'manage data, records, and automate workflows' is extremely generic and could overlap with many other integration or data management skills. The distinctiveness relies entirely on the product name. | 2 / 3 |
Total | 8 / 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.
The skill provides strong actionable guidance with clear, executable CLI commands and a well-sequenced workflow including validation checkpoints for action creation. However, it wastes tokens with an apologetic non-description and a portal structure overview that doesn't help Claude perform tasks. The content could benefit from trimming unnecessary sections and better progressive disclosure.
Suggestions
Remove the 'I'm sorry, but I don't have enough information' paragraph — it wastes tokens and provides no value.
Remove or drastically condense the '1S2U Overview' portal hierarchy section, as it doesn't map to actionable CLI commands and adds no operational guidance.
Consider linking to a separate reference file for advanced topics like action creation polling patterns or error handling details to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes unnecessary filler like 'I'm sorry, but I don't have enough information about the app to provide a description' which wastes tokens. The overview section with portal structure (News, Events, Tenders, etc.) adds little actionable value. However, the CLI commands and workflow sections are reasonably efficient. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, and running actions. Parameter placeholders are clear and the popular actions table gives concrete starting points. | 3 / 3 |
Workflow Clarity | The multi-step workflow is clearly sequenced: install CLI → authenticate → connect → search/create actions → run actions. The action creation flow includes explicit validation via polling with state checks (READY vs CONFIGURATION_ERROR/SETUP_FAILED), and the headless auth flow has a clear two-step process with error recovery guidance. | 3 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's somewhat monolithic — the overview section with the portal hierarchy could be removed or linked externally. There are no references to separate files for advanced topics. The official docs link is provided but not leveraged for progressive disclosure of detailed API reference. | 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
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.