Name: better-stack
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

better-stack

Better Stack integration. Manage Incidents, Users, Teams. Use when the user wants to interact with Better Stack data.

Quality

73%

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

Quality

Content

81%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 copy-paste commands and a well-sequenced, validated connection workflow. Its main weaknesses are minor padding in the intro/best-practices prose and a large inlined actions table that would benefit from being split into a separate reference.

Suggestions

Trim the overview paragraph's background on who uses Better Stack and the "so you can focus on the integration logic" aside to reduce token overhead.

Move the 15-row "Popular actions" table into a referenced file (e.g. ACTIONS.md) and keep only a short representative subset inline, adding a one-level-deep pointer.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes background Claude already knows ("It's used by DevOps engineers and SREs to monitor their applications...") and mild fluff ("so you can focus on the integration logic rather than auth plumbing"). Not a 4 because these padded passages could be trimmed without losing clarity.	3 / 5
Actionability	Every section gives copy-paste-ready commands (npm install, membrane login, connection ensure, action list/run, request with full flag tables) and concrete state-handling examples. This matches the fully-executable, common-cases-covered anchor.	5 / 5
Workflow Clarity	The connection flow is a clear multi-step sequence with an explicit poll loop, enumerated state outcomes (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), and a feedback loop (re-poll after the user completes the action). This matches the explicit-checkpoints, error-recovery anchor.	5 / 5
Progressive Disclosure	Sections are well-organized and the skill is a single self-contained file with no need for external references, but at ~155 lines it exceeds the under-50-line simple-skill exception, and the 15-row actions table is bulk content inlined that could live in a separate reference. Not a 5 because the inlined action catalog prevents a clean one-level-deep split.	4 / 5
	Total	17 / 20 Passed

Description

66%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 clear and distinct, correctly pairing a concrete "what" with an explicit "Use when..." trigger. It is held back by a generic action verb and limited trigger-term variation rather than listing the specific monitoring operations the skill supports.

Suggestions

Replace the generic "Manage" with concrete verbs matching the actions table, e.g. "Manage incidents, monitors, and heartbeats — create, resolve, acknowledge, list, and delete them."

Broaden trigger terms to natural monitoring phrases users say, e.g. "Use when the user wants to query or manage Better Stack incidents, on-call schedules, monitors, or heartbeats."

Dimension	Reasoning	Score
Specificity	"Manage Incidents, Users, Teams" names the domain and three concrete entity types, but the only action verb is the generic "Manage", so coverage is not comprehensive. It is not a 4 because no specific concrete operations (create, resolve, acknowledge) are listed in the description.	3 / 5
Completeness	Both "what" ("Manage Incidents, Users, Teams") and "when" ("Use when the user wants to interact with Better Stack data") are present. Not a 5 because the "when" trigger is generic and lacks concrete, varied trigger phrases.	4 / 5
Trigger Term Quality	It includes relevant keywords ("Better Stack", "Incidents", "Users", "Teams") but lacks common synonyms or variations users might say (e.g. "monitoring", "on-call", "alerts", "logs"). Not a 4 because the natural-term coverage is limited to the brand and entity names.	3 / 5
Distinctiveness Conflict Risk	"Better Stack" names a specific niche product with distinct triggers ("Better Stack"), making conflict with other skills minimal. This matches the clear-niche, minimal-conflict-risk anchor.	5 / 5
	Total	15 / 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/better-stack/SKILL.md
Commit: f484c82

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