1s2u
1S2U integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1S2U data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill 1s2u72
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
67%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 has a proper structure with explicit 'Use when' guidance, but relies heavily on the product name '1S2U' for distinctiveness. The capabilities listed are generic verbs that don't convey specific actions, and the trigger terms beyond the product name are too broad to be useful for skill selection.
Suggestions
Add specific concrete actions like 'create/update records', 'run queries', 'configure automation rules' instead of generic 'manage data'
Include natural trigger variations users might say, such as specific 1S2U features, API operations, or common use cases
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (1S2U) and mentions some actions ('Manage data, records, and automate workflows'), but these are generic verbs without concrete specifics like 'create records', 'query tables', or 'trigger automations'. | 2 / 3 |
Completeness | Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with 1S2U data') with a clear trigger clause. | 3 / 3 |
Trigger Term Quality | Includes '1S2U' as a trigger term which users would say, but lacks variations or related natural keywords. Terms like 'data', 'records', and 'workflows' are too generic to serve as effective triggers. | 2 / 3 |
Distinctiveness Conflict Risk | The '1S2U' brand name provides some distinctiveness, but 'manage data, records, and automate workflows' could overlap with many other integration or database skills. Only the product name prevents conflicts. | 2 / 3 |
Total | 9 / 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 guidance for using the Membrane CLI to interact with 1S2U, with executable commands and clear examples. However, it's weakened by unnecessary content (the apologetic description and generic portal overview), and lacks validation checkpoints or error handling guidance for the multi-step connection workflow.
Suggestions
Remove the apologetic description paragraph and the generic '1S2U Overview' portal structure - they add no actionable value
Add validation steps after key operations (e.g., 'Verify connection succeeded by running `membrane connection list --json` and confirming the connection appears')
Include error handling guidance - what to do if connection fails, if action run returns an error, or if credentials expire
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary content like the apologetic description at the top and the generic portal overview structure that doesn't add actionable value. The Membrane CLI instructions are reasonably efficient but could be tighter. | 2 / 3 |
Actionability | Provides fully executable bash commands for all operations including installation, login, connection setup, action discovery, and running actions. The proxy request section includes concrete flag examples and the popular actions table gives specific action keys. | 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 a connection succeeded, or how to handle action run failures. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the portal overview section is a wall of bullet points that adds no value. The skill is self-contained without external references, which is appropriate for its length, but the structure could be cleaner. | 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.