Name: hotmart
Rating: 47.2 (1 reviews)
Author: membranedev

hotmart

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

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

42%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 CLI workflow sections are concrete and executable, but the document is dominated by a large padded overview list of generic verbs that adds no Hotmart-specific value and wastes context. Validation checkpoints for destructive proxy/action operations are missing.

Suggestions

Delete or move the ~260-entry 'Hotmart Overview' bullet list into a reference file; it is generic, duplicated, and not Hotmart-specific, so it fails to earn its tokens.

Add an explicit validation/verification step for destructive or batch operations, e.g. confirm a connection is READY and dry-run or check an action's outputSchema before running mutating proxy requests (POST/PUT/DELETE).

Split the long CLI reference (connection states, proxy flag table) into a one-level-deep reference file with clear links from SKILL.md to improve navigation.

Dimension	Reasoning	Score
Conciseness	The 'Hotmart Overview' section is ~260 bullet entries of generic English verbs and nouns (e.g. 'Create, Read, Update, Delete, Like, Unlike, Block, Unblock') with extensive duplication, none of it Hotmart-specific — heavily padded content Claude already knows; this matches 'severely verbose; heavily padded' despite the efficient CLI sections elsewhere.	1 / 5
Actionability	Concrete copy-paste commands are provided throughout: 'npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://hotmart.com/" --json', 'membrane action run <actionId> --connectionId=CONNECTION_ID --json', and a full proxy flag table; matches 'mostly executable guidance with minor gaps'; not a 5 because examples rely on placeholders and lack a fully parameterized end-to-end run.	4 / 5
Workflow Clarity	The install→login→connect→poll→search→run sequence is present with state-based branching (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but destructive or batch-capable operations (action run, proxy POST/PUT/DELETE) have no validation or verification steps, capping the score at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	There is section structure and no nested references, but the ~260-line overview list is inlined content that belongs in a separate reference file (or should be removed), and no bundle/reference files exist; matches 'some structure but content that should be separate is inline'.	3 / 5
	Total	11 / 20 Passed

Description

57%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 correctly targets a specific platform and includes an explicit 'Use when' trigger, satisfying both what and when. Its main weakness is generic, non-concrete action language and thin trigger-term coverage.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Hotmart operations, e.g. 'List transactions, manage subscriptions, query affiliates, and automate sales workflows'.

Expand trigger terms to include entity-specific phrases users actually say, such as 'Hotmart sales, subscriptions, affiliates, courses, or payouts'.

Dimension	Reasoning	Score
Specificity	Quotes 'Manage data, records, and automate workflows' name the Hotmart domain but the actions are generic (manage data, records) rather than concrete platform-specific operations, matching the 'names the domain but actions are minimal or generic' anchor; not a 3 because no genuinely concrete actions are listed.	2 / 5
Completeness	It explicitly states both what ('Hotmart integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Hotmart data'), matching 'has both what and when; when could be more explicit or specific'; not a 5 because the what is vague rather than concrete.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with Hotmart data' provides the natural keyword 'Hotmart' but misses common synonyms or entity-level terms (courses, subscriptions, affiliates), fitting 'some relevant keywords but missing common variations'; not a 4 due to thin keyword coverage.	3 / 5
Distinctiveness Conflict Risk	'Hotmart integration' and 'interact with Hotmart data' target a specific named platform, making it mostly distinct with only minor overlap risk against generic integration skills; not a 5 because 'manage data, records, automate workflows' is generic phrasing that could lightly overlap.	4 / 5
	Total	13 / 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/hotmart/SKILL.md
Commit: f484c82

Reviewed: 5 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.