advantage-csp
Advantage CSP integration. Manage data, records, and automate workflows. Use when the user wants to interact with Advantage CSP data.
68
61%
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/advantage-csp/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 correctly identifies the target system (Advantage CSP) and includes an explicit 'Use when' clause, which are positives. However, it is severely lacking in specificity—the actions described are generic and could apply to almost any data platform. Users searching for Advantage CSP help would benefit from more concrete capability descriptions and additional trigger terms.
Suggestions
Add specific concrete actions such as 'create and update records, query contacts, trigger approval workflows, sync inventory data' to replace the vague 'manage data, records, and automate workflows'.
Expand trigger terms with natural variations users might say, such as specific Advantage CSP entity names, common task descriptions, or abbreviations (e.g., 'ACSP', specific module names).
Clarify what types of data and records are supported to improve distinctiveness and help Claude differentiate this skill from other data management or CRM integration skills.
| 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 kinds of data, what record operations (create, update, delete?), or what workflow automations are available. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows in Advantage CSP) and 'when' (Use when the user wants to interact with Advantage CSP data), with an explicit 'Use when...' clause. However, the 'what' and 'when' are both quite thin. | 3 / 3 |
Trigger Term Quality | It includes the product name 'Advantage CSP' which is a useful trigger term, and mentions 'data', 'records', and 'workflows'. However, it lacks natural variations or specific terms users might say (e.g., specific entity types, API operations, or common task names within Advantage CSP). | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Advantage CSP' provides a distinct product-specific niche, but the generic terms 'manage data, records, and automate workflows' 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
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides solid, actionable CLI commands for integrating with Advantage CSP via Membrane, covering the full lifecycle from installation to running actions. Its main weaknesses are unnecessary introductory context about what Advantage CSP is, an underdeveloped entity overview that doesn't connect to actionable guidance, and a lack of explicit validation/error-recovery steps in the workflow. The command examples are the strongest aspect.
Suggestions
Remove or drastically shorten the opening paragraph explaining what Advantage CSP is — Claude doesn't need this context, and the skill description already covers it.
Either flesh out the 'Overview' entity hierarchy with actionable details (e.g., common actions per entity) or remove it entirely, as it currently adds no value.
Add explicit error handling guidance: what to do if `membrane connect` fails, if action search returns no results, or if `action run` returns an error — this would improve workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Advantage CSP is and who uses it is unnecessary context for Claude. The 'Overview' section with the entity hierarchy is vague and adds little value. However, the command examples themselves are reasonably lean. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, polling, and running actions with input parameters. Commands are copy-paste ready with clear placeholder conventions. | 3 / 3 |
Workflow Clarity | The workflow follows a logical sequence (install → auth → connect → discover → create → run), and the action creation flow includes polling with state checking. However, there are no explicit validation checkpoints or error recovery feedback loops for the overall workflow, and the headless auth flow could be more clearly sequenced. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear headers, but it's somewhat monolithic — all content is inline in a single file. The entity overview section is underdeveloped and doesn't link to anything useful. For a skill of this length, the organization is adequate but the overview section wastes space without providing navigation value. | 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 | |
- 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.