Name: mackerel
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

mackerel

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

Quality

64%

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

Quality

Content

71%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 executable CLI commands and a clear, well-checkpointed connection workflow, but it is slightly padded with context Claude already knows and keeps everything inline with no progressive disclosure via separate files. It is a strong, practical skill body with room to tighten prose and split out reference material.

Suggestions

Trim the introductory paragraph and auth-plumbing commentary that restate concepts Claude already knows about SaaS monitoring and credential refresh.

Move the proxy flag table and the action-discovery catalog into separate reference files (e.g. references/proxy.md) and link to them from SKILL.md to improve progressive disclosure.

Fix the "Skip to Step 2" reference by explicitly labeling Step 2 (searching/running actions) so the workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands and short explanations, but the opening paragraph ("Mackerel is a SaaS platform... used by DevOps engineers and SREs to visualize server metrics") and lines like "so you can focus on the integration logic rather than auth plumbing" explain context Claude already knows and could be tightened.	3 / 5
Actionability	It provides copy-paste ready commands for every stage — install, login, connection ensure, action list/run, and request — with a documented flag table for the proxy, fully covering the common cases.	5 / 5
Workflow Clarity	There is a clear install → authenticate → connect → poll-for-ready → search → run sequence, and the connection polling with state branching (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) is an explicit feedback loop, but "Step 2" is referenced without being labeled, a minor sequencing gap.	4 / 5
Progressive Disclosure	The body has good section headers but no bundle files exist and all content (~146 lines) is inlined, including an action-catalog section and a full proxy flag table that could live in separate reference files; this is above the simple-skill threshold so the inline structure is only adequate.	3 / 5
	Total	15 / 20 Passed

Description

57%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 correctly includes both a capability statement and an explicit "Use when" trigger in third person, but the listed actions are generic abstractions rather than concrete Mackerel operations, limiting specificity. It is a competent but somewhat vague description for a named integration.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Mackerel actions such as "view host metrics, acknowledge alerts, and post service metrics".

Sharpen the trigger clause with natural phrasings a user would say, e.g. "Use when the user mentions Mackerel, host metrics, monitoring alerts, or check reports".

Mention key Mackerel entities (hosts, services, alerts, dashboards) to improve distinctiveness and trigger-term coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ("Mackerel integration") but the actions — "Manage data, records, and automate workflows" — are generic abstractions rather than concrete Mackerel actions like viewing hosts or acknowledging alerts, matching the anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Mackerel data") are present; the "when" clause exists but could be more specific, matching the anchor for both present with room for sharper triggers.	4 / 5
Trigger Term Quality	The brand keyword "Mackerel" appears, but the trigger phrasing "interact with Mackerel data" is generic and lacks natural synonyms or variations a user might say, fitting the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	Mackerel is a specific named monitoring platform with a niche trigger, making it mostly distinct from other skills with only minor overlap risk against closely related monitoring integrations.	4 / 5
	Total	13 / 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/mackerel/SKILL.md
Commit: f484c82

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