3dcart
3dcart integration. Manage data, records, and automate workflows. Use when the user wants to interact with 3dcart data.
68
61%
Does it follow best practices?
Impact
Pending
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 the capabilities described are extremely generic and could apply to virtually any integration. It lacks concrete actions specific to 3dcart's e-commerce domain (e.g., managing products, processing orders, updating inventory) and misses natural trigger terms users would associate with an e-commerce platform.
Suggestions
Replace vague actions with specific 3dcart capabilities, e.g., 'Manage products, process orders, update inventory, and handle customer records in 3dcart stores.'
Add natural trigger terms users would say, such as 'e-commerce', 'online store', 'orders', 'products', 'shopping cart', or 'Shift4Shop' (3dcart's rebranded name).
Expand the 'Use when' clause with specific scenarios, e.g., 'Use when the user mentions 3dcart, Shift4Shop, or needs to manage e-commerce store data like products, orders, or customers.'
| 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 variations or related terms (e.g., 'e-commerce', 'online store', 'orders', 'products', 'shopping cart') that users might naturally use when needing this skill. | 2 / 3 |
Distinctiveness Conflict Risk | The '3dcart' name provides some distinctiveness, but 'manage data, records, and automate workflows' is so generic it could overlap with any integration or data management skill. Only the platform name prevents major conflicts. | 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 interacting with 3dcart via Membrane, with good coverage of the full workflow from installation to running actions. Its main weaknesses are unnecessary introductory context about what 3dcart is, and missing validation/verification steps in the workflow. The resource overview section lists entities without actionable guidance on how to use them.
Suggestions
Remove the introductory paragraph explaining what 3dcart is — Claude already knows this, and the skill description covers it.
Add explicit validation steps after key operations (e.g., verify connection was created successfully before proceeding to action discovery, verify action output after running).
Make the resource overview actionable by showing example action queries for common entities (e.g., 'membrane action list --intent "list customers" --connectionId=CONNECTION_ID') or remove it entirely.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what 3dcart is (e-commerce platform for entrepreneurs) is unnecessary context Claude already knows. The overview section listing resources without actionable detail adds little value. However, the CLI commands and workflow sections are reasonably efficient. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, polling, and running actions with input parameters. Each command includes concrete flags and placeholders. | 3 / 3 |
Workflow Clarity | The multi-step workflows (install → authenticate → connect → discover → run) are present and sequenced, but there are no explicit validation checkpoints or error recovery loops. The action creation flow has state checking (BUILDING → READY/ERROR) which is good, but the overall workflow lacks verification steps after running actions or connecting. | 2 / 3 |
Progressive Disclosure | The content is structured with clear headers and sections, but it's somewhat monolithic — the resource overview list (Customer, Order, Product, etc.) provides no links or references to deeper documentation. The official docs link is mentioned but no specific sub-references are provided for advanced topics. | 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.