Name: datamolino
Rating: 59.2 (1 reviews)
Author: membranedev

datamolino

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

Quality

68%

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/datamolino/SKILL.md

Quality

Content

75%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 solid, action-oriented CLI integration guide with executable commands and a well-handled connection state machine. Its main weaknesses are a small amount of redundancy and an inconsistent step-numbering scheme that leaves a dangling 'Step 2' reference.

Suggestions

Fix the dangling cross-reference: either label the 'Searching for actions' section as 'Step 2' or reword 'skip to Step 2' to point to the actual section name.

Remove the redundant 'Popular actions' section or fold it into 'Searching for actions' to avoid repeating the action-list command.

Tighten the 'Agent Types' line into a concise inline note rather than an awkward sentence about harness tooling.

Dimension	Reasoning	Score
Conciseness	Mostly lean and command-driven with brief, relevant context about what Datamolino is; minor redundancy ('Popular actions' repeats the action-list command from 'Searching for actions') and an awkward filler line about agent types could be trimmed.	4 / 5
Actionability	Provides concrete, copy-paste-ready commands for every stage (install, login, connection ensure/get, action list, action run, request with a full flag table); placeholders like CONNECTION_ID and <actionId> are expected, with only minor gaps such as no worked end-to-end example with real values.	4 / 5
Workflow Clarity	Clear install→auth→connect→search→run sequence with a state-machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling feedback loop; however 'skip to Step 2' references a missing Step 2 header and the section numbering (1b) is inconsistent.	4 / 5
Progressive Disclosure	Well-organized into clear, navigable sections in a single self-contained file with no bundle files present; at ~163 lines it exceeds the 50-line simple-skill exception, but the sectioning keeps it usable with only minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

62%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 is competent — it states what the skill does and gives an explicit use-when trigger tied to a named product. Its main weakness is generic action language that hides the skill's concrete invoice/receipt extraction purpose.

Suggestions

Replace generic verbs with the skill's real capabilities, e.g. 'Extract data from invoices and receipts, manage vendors and documents, and automate bookkeeping workflows.'

Broaden the trigger phrase to cover natural user terms: 'Use when the user wants to extract invoice/receipt data, manage Datamolino documents, or automate bookkeeping tasks.'

Mention key entity nouns (invoices, receipts, vendors, clients) so the description is distinguishable from other membrane app skills that share the same template.

Dimension	Reasoning	Score
Specificity	Names the domain (Datamolino) and lists a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete — it never mentions invoice/receipt extraction, which is the skill's actual capability.	3 / 5
Completeness	Both 'what' (Datamolino integration, manage data/records/workflows) and 'when' ('Use when the user wants to interact with Datamolino data') are present, but the 'when' is narrow and could be more specific about invoice/receipt use cases.	4 / 5
Trigger Term Quality	Contains relevant keywords ('Datamolino', 'data', 'records', 'workflows') and an explicit trigger, but misses common natural variations and synonyms a user might say (invoices, receipts, bookkeeping, document capture).	3 / 5
Distinctiveness Conflict Risk	Tied to a named app gives it a clear niche with distinct triggers, but the generic templated phrasing ('Manage data, records, and automate workflows') overlaps with sibling membrane integration skills.	4 / 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/datamolino/SKILL.md
Commit: f484c82

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