adversus
Adversus integration. Manage data, records, and automate workflows. Use when the user wants to interact with Adversus data.
42
42%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/adversus/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 naming the specific platform (Adversus) and including an explicit 'Use when' clause, which helps with completeness and some distinctiveness. However, it is severely lacking in specificity — the actions described are generic enough to apply to virtually any data platform integration. Without concrete Adversus-specific capabilities or natural user trigger terms, Claude would struggle to confidently select this skill over other integration skills.
Suggestions
Replace vague terms like 'manage data, records, and automate workflows' with specific Adversus actions such as 'create and update leads, manage call campaigns, sync contact lists, configure automated dialer workflows'.
Add natural trigger terms users would say, such as 'Adversus CRM', 'call center', 'leads', 'campaigns', 'dialer', or 'outbound calls'.
Expand the 'Use when' clause with more specific scenarios, e.g., 'Use when the user mentions Adversus, outbound calling campaigns, lead management in Adversus, or CRM dialer integrations'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying concrete actions. It doesn't explain what kind of data, what records, or what workflows — these are generic terms that could apply to almost any integration. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (when the user wants to interact with Adversus data) with an explicit 'Use when' clause, even though both parts are vague in substance. | 3 / 3 |
Trigger Term Quality | It includes 'Adversus' as a key trigger term which is specific to the platform, and 'data' and 'workflows' are somewhat relevant. However, it lacks natural terms users might say like specific Adversus features (e.g., leads, campaigns, call lists, contacts, CRM, dialer). | 2 / 3 |
Distinctiveness Conflict Risk | 'Adversus' as a product 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. Only the brand name prevents a score of 1. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill suffers severely from a massive, likely hallucinated entity list (~150 items) that appears to be from a legal practice management platform rather than Adversus (a dialer/CRM for outbound sales). The Membrane CLI integration instructions are reasonably clear but generic across all Membrane-connected apps. The skill would benefit enormously from removing the entity list, adding Adversus-specific examples with real parameters, and restructuring for conciseness.
Suggestions
Remove the entire 150+ entity bullet list which appears hallucinated/incorrect for Adversus and wastes massive token budget — replace with a brief description of Adversus's actual data model (leads, campaigns, activities, etc.)
Add concrete, executable examples for the popular actions table, e.g., show a complete `membrane action run create-lead --input '{"name": "John Doe", "phone": "+1234567890"}'` with expected output
Fix the product description — Adversus is an outbound dialer/CRM platform, not a 'competitive intelligence platform' — this fundamental error undermines the skill's credibility
Extract reference material (proxy request flags table, connection state handling details) into separate bundle files and keep SKILL.md as a concise overview with links
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The massive bullet-point list of 150+ entity types (Case, Contact, Task, etc.) is overwhelmingly verbose and provides no actionable value. Many of these entities (e.g., Pet, Vehicle, Will, Trust, Power of Attorney, Healthcare Directive) appear to be from a legal practice management platform, not a competitive intelligence tool like Adversus. This is clearly boilerplate/hallucinated content that wastes enormous token budget. | 1 / 3 |
Actionability | The Membrane CLI commands are concrete and executable (install, login, connection ensure, action run, proxy requests), but the Adversus-specific guidance is weak. The 'Popular actions' table provides useful action names but no executable examples with real parameters or expected outputs. The entity list provides zero actionable guidance. | 2 / 3 |
Workflow Clarity | The connection setup workflow is reasonably well-sequenced with state handling (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), but there are no validation checkpoints for the actual Adversus operations. The workflow for discovering and running actions is present but lacks error handling or verification steps after running actions. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files. The enormous entity list should either be removed entirely or placed in a separate reference file. There is no bundle structure to support progressive disclosure, and the inline content is poorly organized with the massive list dominating the document. | 1 / 3 |
Total | 6 / 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.