3dcart
3dcart integration. Manage data, records, and automate workflows. Use when the user wants to interact with 3dcart 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/3dcart/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 a specific platform (3dcart) and including an explicit 'Use when' clause, but it is severely lacking in specificity of capabilities. The actions described are boilerplate phrases that could apply to virtually any integration skill, making it hard for Claude to understand what this skill actually does with 3dcart.
Suggestions
Replace generic actions with 3dcart-specific capabilities such as 'manage products, process orders, update inventory, handle customer records'.
Add natural trigger terms users might say, such as 'ecommerce', 'online store', 'shopping cart', 'product catalog', or 'order management'.
Expand the 'Use when' clause with specific scenarios like 'Use when the user mentions 3dcart, needs to manage an online store, or wants to sync ecommerce data'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The actions described ('manage data, records, and automate workflows') are extremely vague and generic. There are no concrete actions specific to 3dcart such as managing products, orders, customers, or inventory. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with 3dcart data), with an explicit 'Use when' clause. However, both parts are quite shallow in detail. | 3 / 3 |
Trigger Term Quality | The term '3dcart' is a specific and natural keyword users would say, but there are no additional trigger terms like 'ecommerce', 'online store', 'products', 'orders', or 'shopping cart' that users might naturally use when needing this skill. | 2 / 3 |
Distinctiveness Conflict Risk | '3dcart' is a distinctive platform name that helps differentiate it, but the generic phrasing 'manage data, records, and automate workflows' could easily overlap with any other integration or data management skill. | 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 integration skill with excellent actionability and workflow clarity—every step has concrete, executable CLI commands and the connection flow handles multiple states with clear guidance. The main weaknesses are moderate verbosity (introductory explanation, some redundant phrasing) and a monolithic structure that could benefit from splitting detailed reference material into separate files.
Suggestions
Remove the introductory paragraph explaining what 3dcart is—Claude already knows this and it wastes tokens.
Consider extracting the proxy request flags table and detailed CLIENT_ACTION_REQUIRED handling into a separate reference file to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'an e-commerce platform that provides businesses with the tools to build and manage online stores') and the overview section listing resources without actionable detail adds little value. The Membrane CLI instructions are reasonably efficient but could be tighter. | 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 are copy-paste ready with clear parameter placeholders. | 3 / 3 |
Workflow Clarity | The connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors), polling instructions, and conditional branching. The overall flow from install → authenticate → connect → discover → run is well-structured with validation at each stage. | 3 / 3 |
Progressive Disclosure | The content is reasonably organized with clear sections, but it's a monolithic file with no references to supporting documents. The resource overview (Customer, Order, Product, etc.) is listed without links or further detail, and the proxy request reference table could be in a separate file for complex use cases. | 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.