adversus
Adversus integration. Manage data, records, and automate workflows. Use when the user wants to interact with Adversus data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill adversus60
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.
The description correctly follows the structure with a 'Use when...' clause and identifies the specific integration (Adversus). However, it lacks concrete action specificity - the verbs 'manage' and 'automate' are too vague to help Claude understand what this skill actually does. The trigger terms rely heavily on users knowing and saying 'Adversus' without providing alternative natural language triggers.
Suggestions
Replace vague verbs with specific actions: instead of 'Manage data, records', specify 'Create and update contacts, manage leads, track call outcomes, configure campaigns'
Add natural trigger terms users might say: 'dialer', 'outbound calls', 'lead management', 'call center CRM', or specific Adversus features
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Adversus) and mentions general actions ('Manage data, records, and automate workflows'), but these are not concrete specific actions - 'manage' and 'automate' are vague verbs without specifics like 'create contacts', 'update lead status', or 'trigger campaigns'. | 2 / 3 |
Completeness | Has both 'what' (manage data, records, automate workflows) and 'when' (explicit 'Use when the user wants to interact with Adversus data'). The 'Use when...' clause is present and provides clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes 'Adversus' as a key trigger term which users would say, but lacks common variations or related terms users might use (e.g., 'CRM', 'dialer', 'call center', 'leads', 'campaigns'). Missing natural language variations. | 2 / 3 |
Distinctiveness Conflict Risk | 'Adversus' is a specific product name which helps distinctiveness, but 'manage data, records, and automate workflows' is generic enough to potentially conflict with other CRM or data management skills. The trigger 'Adversus data' is specific but the capabilities overlap with generic data management. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has a fundamental content accuracy problem - the 'Adversus Overview' section lists 150+ entities from what appears to be legal practice management software, not a competitive intelligence platform. The Membrane CLI integration guidance is reasonably actionable but the bloated, incorrect entity list severely undermines the skill's utility and wastes significant token budget.
Suggestions
Remove or replace the incorrect 150+ entity list with actual Adversus API resources (leads, campaigns, activities, etc.) that match the competitive intelligence platform
Add input schema examples for the popular actions table, showing required vs optional parameters
Include a concrete end-to-end example showing a complete workflow (e.g., create lead → add activity → change status) with validation steps
Add error handling guidance for common failure scenarios (auth expired, invalid input, rate limits)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains a massive list of 150+ entity types that appears to be copy-pasted from a different system (looks like legal practice management software, not a competitive intelligence platform). This bloated list wastes tokens and provides no actionable value. | 1 / 3 |
Actionability | The Membrane CLI commands are concrete and executable, with clear examples for connecting, listing actions, and running them. However, the action table lacks input schemas, and the proxy request section could use a complete example with actual Adversus endpoints. | 2 / 3 |
Workflow Clarity | The setup flow (install → login → connect → run actions) is reasonably clear, but there's no validation or error handling guidance. Missing checkpoints for verifying connection success or handling failed API calls. | 2 / 3 |
Progressive Disclosure | Content is organized into sections but the massive entity list dominates the file. No references to external documentation for advanced topics. The structure would benefit from moving detailed content to separate files. | 2 / 3 |
Total | 7 / 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.