advantage-csp
Advantage CSP integration. Manage data, records, and automate workflows. Use when the user wants to interact with Advantage CSP data.
58
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 the 'when' clause with more specific scenarios, e.g., 'Use when the user mentions Advantage CSP, ACSP, or needs to query/update CRM records, manage content workflows, or pull reports from Advantage.'
| 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
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with clear CLI commands and a well-structured connection workflow with proper state handling and error recovery. Its main weaknesses are some unnecessary introductory context (explaining what Advantage CSP is) and a monolithic structure that could benefit from progressive disclosure via supplementary files. The entity hierarchy section feels incomplete—it lists entities but doesn't connect them to discoverable actions or provide examples.
Suggestions
Remove the introductory paragraph explaining what Advantage CSP is and who uses it—Claude doesn't need this context to execute the skill.
Flesh out the entity hierarchy section with example action names or queries for each entity (e.g., 'To list invoices: membrane action list --intent "list invoices"'), or remove it if it doesn't add actionable value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Advantage CSP is and who uses it is unnecessary context for Claude. The entity hierarchy overview is sparse but fine. Some sections like the proxy request table are useful, but the overall content could be tightened—e.g., the best practices section restates things already implied by the workflow. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands include concrete flags, JSON output options, and parameter passing examples. This is copy-paste ready. | 3 / 3 |
Workflow Clarity | The connection workflow is clearly sequenced with explicit state-based branching (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR, SETUP_FAILED). It includes polling/retry loops for the BUILDING state and clear instructions for each possible outcome. The headless auth flow also has a clear two-step process. | 3 / 3 |
Progressive Disclosure | The content is entirely inline in a single file with no bundle files or references to supplementary materials. While the structure uses headers and sections reasonably well, the entity hierarchy section is underdeveloped (just a bullet list with no explanation of how these relate to actions), and the content could benefit from splitting detailed reference material (like proxy options) into separate files. | 2 / 3 |
Total | 10 / 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.