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

Blog Docs Log in Get started

heartbeat

Heartbeat integration. Manage Organizations, Users. Use when the user wants to interact with Heartbeat data.

Quality

69%

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

Quality

Content

76%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 highly actionable with concrete, executable Membrane commands and a clear connection-state workflow. Its main weaknesses are a destructive-action validation gap (capping workflow clarity), an intro that conflates Elastic Heartbeat monitoring with the heartbeat.chat community platform, and a heavy inline actions table that could be offloaded.

Suggestions

Add an explicit validation/confirmation checkpoint before destructive actions (e.g., 'Confirm the user ID and re-fetch before running delete-user; verify the result'), which would unblock the workflow-clarity cap.

Reconcile the product framing: the intro and the 'Official docs' link describe Elastic's Heartbeat monitoring beats, while the integration actions target the heartbeat.chat community platform — clarify which product this skill serves.

Consider moving the full Popular actions table into a references/actions.md file and keeping a short representative subset inline, improving progressive disclosure and token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable command blocks and compact tables; minor over-explanation in the intro paragraph ("Heartbeat is a monitoring platform...") and a few prose asides could be trimmed, fitting the 'efficient with minor instances of over-explanation' anchor.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (`membrane login`, `membrane connection ensure`, `membrane action list/run`, `membrane request`) with a flag table and JSON parameter examples covering the common cases.	5 / 5
Workflow Clarity	The connection workflow is well-sequenced with state checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling, but destructive actions (Delete User, Update User) appear in the action table with no validation or confirmation guidance, capping workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	Clear, well-organized section headers structure a self-contained ~176-line skill with no bundle files; the large 'Popular actions' reference table is reasonable inline but keeps it just short of the 'ideally split' ideal, matching the 'good structure with minor organization gaps' anchor.	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 well-formed: third-person voice, names the domain and core entities, and includes an explicit 'Use when' trigger. It is held back by a thin action list and a generic trigger phrase that lacks concrete synonyms or scenario cues.

Suggestions

Expand 'Manage Organizations, Users' into several specific concrete actions (e.g., list/create/update/delete users and groups) to lift specificity.

Sharpen the trigger clause with concrete scenarios a user would say, e.g., 'Use when managing Heartbeat users, groups, channels, courses, or community data'.

Align entity names with the skill body — the description says 'Organizations' but the body exposes 'Company', 'Team', 'Group', 'Channel', 'Course', etc., which weakens distinctiveness and trigger matching.

Dimension	Reasoning	Score
Specificity	Names the domain ("Heartbeat integration") and 1-2 concrete actions ("Manage Organizations, Users"), but the action list is minimal and not comprehensive, matching the anchor for naming a domain with 1-2 concrete actions.	3 / 5
Completeness	Both 'what' ("Heartbeat integration. Manage Organizations, Users.") and 'when' ("Use when the user wants to interact with Heartbeat data.") are present; the 'when' clause is explicit but could be more specific, fitting the anchor where both exist with room for sharper triggers.	4 / 5
Trigger Term Quality	Includes relevant keywords ("Heartbeat", "Organizations", "Users") but lacks common variations or synonyms a user might naturally say; the only distinctive trigger is the product name plus a generic "interact with Heartbeat data" phrase.	3 / 5
Distinctiveness Conflict Risk	Tied to a named product ("Heartbeat") giving it a clear niche with mostly distinct triggers; the generic "Organizations, Users" entities create only minor overlap risk with closely related community/admin 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/heartbeat/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.