Name: moltin
Rating: 53.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

moltin

Moltin integration. Manage data, records, and automate workflows. Use when the user wants to interact with Moltin data.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/moltin/SKILL.md

Quality

Content

60%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a mostly executable, well-structured guide to driving Moltin through the Membrane CLI, with a genuine state-machine feedback loop for connection setup. Its main weakness is the large, low-value entity bullet list that inflates the token budget without proportionate guidance.

Suggestions

Replace the 75-line entity bullet dump with a compact one-line summary (e.g. 'Moltin exposes ~40 core resources — Product, Category, Order, Cart, Customer, Promotion, Inventory, etc. — each with Relationship variants') and point to the official docs for the full list.

Add one fully-worked action example with real input and output parsing (e.g. creating a product and reading the returned id) so the run/proxy guidance is copy-paste-complete.

Number the connection steps consistently (1, 2, 3) so the 'Step 2' and '1b' references resolve to actual headings.

Dimension	Reasoning	Score
Conciseness	The ~75-line Moltin Overview bullet list of entity names (including mechanically derived 'Product Relationship', 'Category Brand Relationship' variants) is a large padded section that adds little Claude cannot derive, fitting 'noticeably verbose; several unnecessary explanations or padded sections' despite the otherwise efficient CLI instructions.	2 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, action list/run, and proxy with a concrete flags table, but templates like CONNECTION_ID and --input '{"key": "value"}' leave minor gaps versus the fully-worked score-5 example.	4 / 5
Workflow Clarity	The connection flow has a clear state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with a poll-and-retry feedback loop, but step references like 'Step 2' and '1b' are unnumbered, leaving minor sequencing gaps short of the score-5 checklist anchor.	4 / 5
Progressive Disclosure	Content is well-organized under clear headers (Overview, Working with Moltin, Authentication, Connecting, Searching, Popular actions, Best practices) with no nested references, though the inline entity catalog is the one piece that could live in a separate reference file.	4 / 5
	Total	14 / 20 Passed

Description

61%Weight 40%Scale 1-5

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 cleanly answers what and when around a distinctive named platform, but its action verbs are generic and its trigger coverage is thin (just 'Moltin' / 'Moltin data'). It is functional but would benefit from concrete capabilities and more trigger phrasings.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Moltin capabilities such as 'create and update products, manage orders and carts, handle inventory and promotions'.

Expand the trigger clause with multiple natural phrasings, e.g. 'Use when the user wants to interact with Moltin data — managing products, orders, customers, carts, or promotions via the Moltin API'.

Tighten 'Moltin integration' into an active third-person lead that states the primary outcome (e.g. 'Interacts with the Moltin eCommerce API to manage catalog, orders, and customers').

Dimension	Reasoning	Score
Specificity	It names the domain ('Moltin integration') but the actions ('Manage data, records, and automate workflows') are generic rather than concrete, matching the 'minimal or generic actions' anchor better than the score-3 example which lists concrete verbs like 'extracts content'.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Moltin data') are present and explicit, though the 'when' clause is a single trigger rather than multiple concrete phrases, so it does not reach the score-5 anchor.	4 / 5
Trigger Term Quality	The keyword 'Moltin' / 'Moltin data' is the natural term a user would say, but no synonyms or variations are offered, fitting 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	'Moltin' is a specific named eCommerce platform, giving the skill a clear niche with a distinctive proper-noun trigger and minimal overlap risk with other skills.	5 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/moltin/SKILL.md
Commit: f484c82

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.