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

Blog Docs Log in Get started

herald

Herald integration. Manage data, records, and automate workflows. Use when the user wants to interact with Herald 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

80%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 executable Membrane CLI commands and a well-structured connection state machine, but it slightly over-explains concepts and inlines API reference material that progressive disclosure would split out. It lacks validation checkpoints around destructive proxy requests.

Suggestions

Add an explicit validation/confirm checkpoint before destructive proxy requests (e.g. `-X DELETE`) to lift the workflow_clarity cap.

Trim prose explaining auth and credential refresh that the CLI commands already imply, to improve conciseness.

Move the full action-discovery and proxy-options reference into a separate reference file and link to it, improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and tables, though it over-explains Membrane's auth handling in prose that Claude could infer from the commands.	4 / 5
Actionability	It provides copy-paste-ready CLI commands with flags, JSON output guidance, and a clear options table covering the common proxy and action cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED) and polling guidance, but destructive actions like `request` DELETE lack explicit validation or confirm-checkpoints.	4 / 5
Progressive Disclosure	Content is organized into sections but there are no bundle files and no external references; API/action detail that could live in a separate file is inlined, and navigation is section-only.	3 / 5
	Total	16 / 20 Passed

Description

40%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 has an explicit 'Use when' trigger, satisfying the completeness floor, but its capability language is generic and not Herald-specific. Trigger terms lack the natural phrasing users would actually say. It is functional but under-specified.

Suggestions

Replace generic verbs with Herald-specific actions, e.g. 'Configure notification rules, manage alert subscriptions, and review incident event logs'.

Add natural trigger terms users would say, such as 'notifications', 'alerts', 'incident monitoring', or 'alert rules'.

Tighten the 'when' clause to concrete scenarios, e.g. 'Use when the user wants to set up Herald alert rules or query incident history'.

Dimension	Reasoning	Score
Specificity	The description names the domain (Herald data) but its actions are minimal and generic ('Manage data, records, and automate workflows') with no concrete Herald-specific capabilities.	2 / 5
Completeness	It states a vague 'what' ('Manage data, records, and automate workflows') plus an explicit 'when' clause ('Use when the user wants to interact with Herald data'), but the 'what' is imprecise.	3 / 5
Trigger Term Quality	It offers only one generic trigger ('interact with Herald data'); natural user phrases like notifications, alerts, or incident monitoring are absent.	2 / 5
Distinctiveness Conflict Risk	The Herald name gives it a niche, but 'manage data, records, and automate workflows' is broad and could overlap with many integration skills.	3 / 5
	Total	10 / 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/herald/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.