Name: heartland
Rating: 60 (1 reviews)
Author: membranedev

heartland

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

Quality

70%

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

Quality

Content

77%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 content is highly actionable with ready-to-run CLI commands and a clear connection-state workflow, but it shows some redundancy and lacks progressive-disclosure structure or reference files to offload detail. Workflow clarity is strong on connection setup but lighter on validating action outcomes.

Suggestions

Add an explicit validation/verification checkpoint after running actions (e.g. inspect the `output` field and confirm expected fields) to raise workflow clarity for batch or destructive operations.

Remove the duplicated action-list command in "Popular actions" or consolidate it with the "Searching for actions" section to reduce redundancy.

Consider moving the long entity tree into a short reference file and linking to it from the overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and minimal padding, though the long indented entity tree and some explanatory prose (e.g. agent types) could be trimmed slightly.	4 / 5
Actionability	It provides copy-paste ready commands for install, login, connection ensure, polling, action list/run, and proxy requests, with concrete flags and a full options table covering the common cases.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with state checks and a polling feedback loop (BUILDING -> READY/CLIENT_ACTION_REQUIRED/ERROR), though the run-action path and proxy path lack explicit validation checkpoints for batch/destructive calls.	4 / 5
Progressive Disclosure	There is reasonable section structure, but the entity overview is inlined, there are no one-level-deep reference files (none exist in the bundle), and the popular-actions section duplicates the earlier searching-for-actions command.	3 / 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 includes a clear Use-when trigger and a third-person statement of capabilities, but the actions are generic rather than concrete Heartland operations. It is functional but could be more specific about what Heartland work it covers.

Suggestions

Replace generic actions ("Manage data, records, and automate workflows") with concrete Heartland capabilities such as payments, invoices, vendors, and expense reports.

Add natural user trigger terms beyond the brand name, e.g. "when the user mentions Heartland payments, invoices, or POS data."

Tighten the Use-when clause to reference specific Heartland entities rather than just "Heartland data."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain and a couple of generic actions, but the actions are broad (data, records, workflows) rather than concrete Heartland-specific operations.	3 / 5
Completeness	It states what the skill does ("Manage data, records, and automate workflows") and gives a "Use when the user wants to interact with Heartland data" clause, so both what and when are present, though the when is fairly generic.	4 / 5
Trigger Term Quality	"interact with Heartland data" is a relevant keyword, but the description lacks common natural synonyms a user would say (e.g. payments, invoices, POS) beyond the brand name.	3 / 5
Distinctiveness Conflict Risk	The Heartland brand anchor makes it mostly distinct from other skills, though the generic "data, records, workflows" framing leaves minor overlap risk with other 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/heartland/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.