Name: metricfire
Rating: 55.2 (1 reviews)
Author: membranedev

metricfire

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

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

63%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 delivers strong, executable CLI guidance with a clear connect-and-poll workflow, but it is somewhat verbose and inlines reference-style material that would benefit from separation into bundle files.

Suggestions

Trim the introductory paragraph defining MetricFire and its underlying stack, and de-duplicate the action-list command that appears in both 'Searching for actions' and 'Popular actions'.

Move the connection-state machine and the proxy flag table into reference files under ./references/ and link to them, improving progressive disclosure and token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but it includes unnecessary framing (the intro paragraph defining MetricFire/Graphite/Prometheus/Grafana and a repeated action-list command in 'Popular actions') that could be trimmed, matching the mostly-efficient-but-could-be-tighter anchor.	3 / 5
Actionability	Concrete, copy-paste-ready CLI commands cover install, login, connection, polling, action listing/running, and proxying, with only minor gaps (CONNECTION_ID placeholders and inconsistent membrane vs npx invocations), fitting the mostly-executable anchor.	4 / 5
Workflow Clarity	A clear sequence (install -> authenticate -> connect -> poll state -> search actions -> run/proxy) with explicit checkpoints and a feedback loop (poll until state leaves BUILDING, re-poll after user action) is present; it is not a 5 because some validation guidance for error/CONFIGURATION_ERROR recovery is only briefly sketched.	4 / 5
Progressive Disclosure	Sections are well-organized and there are no nested references, but all content (the connection state machine, proxy flag table, popular actions) is inlined in a ~145-line file rather than split into reference files, matching the some-structure-but-content-should-be-separate anchor.	3 / 5
	Total	14 / 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 correctly pairs a what and a when around a distinct MetricFire niche, but its action verbs are generic and its trigger vocabulary lacks synonyms or variations.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete MetricFire operations such as dashboards, graphs, alerts, data sources, and incidents.

Expand the 'Use when' clause with additional natural trigger phrases (e.g., monitoring metrics, Grafana dashboards, Prometheus data sources) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (MetricFire) and a few actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete specific operations, so it sits at the 1-2 concrete-actions anchor and not the comprehensive 4-5.	3 / 5
Completeness	It states both a what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with MetricFire data"), satisfying the both-present anchor; it falls short of 5 because the trigger phrasing is not concrete or multifaceted.	4 / 5
Trigger Term Quality	"MetricFire" and "interact with MetricFire data" are relevant keywords, but there are no synonyms, variations, or related natural phrases users might say, matching the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	The MetricFire niche is a clear, distinct trigger with minimal overlap risk, but the generic "Manage data, records, and automate workflows" clause could overlap with other data-management skills, keeping it just below a 5.	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/metricfire/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.