abyssale
Abyssale integration. Manage data, records, and automate workflows. Use when the user wants to interact with Abyssale data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill abyssale57
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
32%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 fails to explain what Abyssale actually is or does, relying entirely on the product name for distinctiveness. The generic phrases 'manage data, records, and automate workflows' could apply to virtually any integration tool, and the circular trigger guidance provides no useful selection criteria for Claude.
Suggestions
Add specific capabilities that describe what Abyssale does (e.g., 'Generate personalized banners, create image variations at scale, automate creative asset production').
Include natural trigger terms users would say without knowing the tool name (e.g., 'banner generation, image templates, creative automation, bulk image creation').
Replace the circular 'Use when' clause with concrete scenarios (e.g., 'Use when the user needs to generate marketing banners, create personalized images, or automate visual content production').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Manage data, records, and automate workflows' without specifying what Abyssale actually does or what concrete actions are available. No specific capabilities are listed. | 1 / 3 |
Completeness | Has a weak 'what' (generic data/workflow management) and includes a 'Use when' clause, but the trigger is circular ('interact with Abyssale data') rather than describing scenarios where users would need this skill. | 2 / 3 |
Trigger Term Quality | Includes the product name 'Abyssale' which users would say, but lacks any natural keywords describing what Abyssale is (e.g., banner generation, image automation, creative assets) that users might mention without knowing the tool name. | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is extremely generic and would conflict with dozens of other integration skills. Only 'Abyssale' provides distinctiveness, but users unfamiliar with the tool wouldn't know to mention it. | 1 / 3 |
Total | 6 / 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 CLI commands for Abyssale integration via Membrane, with good examples and a useful actions table. However, it includes unnecessary platform description, lacks validation checkpoints in workflows, and the 'Overview' section with vague guidance ('Use action names and parameters as needed') adds no value.
Suggestions
Remove the introductory paragraph explaining what Abyssale is and the vague Overview section - Claude doesn't need this context
Add validation steps after key operations (e.g., 'Verify connection succeeded by running `membrane connection list`' after connecting)
Replace 'When to use which actions: Use action names and parameters as needed' with either concrete guidance or remove entirely
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'Abyssale is a creative automation platform that helps businesses...') that Claude doesn't need. The overview section with Template/Preset/Generation hierarchy adds little value. However, the CLI commands and action tables are reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with clear syntax examples. The action table with keys and descriptions, plus concrete examples for running actions with JSON input, makes this copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps for setup and connection are listed but lack validation checkpoints. No explicit verification that login succeeded, connection was established, or actions completed successfully. The 'When to use which actions' section is vague and unhelpful. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The popular actions table could be a separate reference file. No external file references for advanced usage or complete action catalog. | 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.