Name: apimetrics
Rating: 64.8 (1 reviews)
Author: membranedev

apimetrics

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

Quality

77%

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

Quality

Content

88%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 and well-sequenced, with concrete commands, a clear connect-to-run workflow, and explicit state/error checkpoints. The only real weakness is mild over-explanation of context Claude already knows and some inline reference material that could be split out.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands, tables, and flags, but retains some context Claude already knows (the introductory paragraph about what APImetrics is and who uses it) and a somewhat padded clientAction state enumeration, fitting the score-4 anchor of efficient content with minor trimmable over-explanation.	4 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (`membrane connection ensure`, `membrane action run`, `membrane request`) with real flags and a flag table, covering the common cases, matching the score-5 anchor.	5 / 5
Workflow Clarity	The install -> authenticate -> connect -> poll-for-state -> search-actions -> run/proxy sequence is clearly laid out with explicit polling checkpoints, state-transition handling (READY/BUILDING/CLIENT_ACTION_REQUIRED), and error feedback (CONFIGURATION_ERROR/SETUP_FAILED), matching the score-5 anchor of a clear sequence with explicit validation steps and error-recovery feedback loops.	5 / 5
Progressive Disclosure	The file is well-organized with clear section headers and is self-contained with no external references, but it is over 50 lines and inlines reference-style content (the clientAction enumeration, the proxy flag table) that could live in separate files, fitting the score-4 anchor of good structure with minor organization gaps.	4 / 5
	Total	18 / 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 covers both what the skill does and when to use it, and the APImetrics niche is distinct. Its main weakness is generic action language ("Manage data, records") and a thin trigger clause that repeats the product name rather than listing concrete natural triggers.

Suggestions

Replace generic verbs with concrete actions, e.g. "Run API tests and monitors, view check results, manage schedules and alerts, and read dashboards."

Expand the "Use when" clause with natural trigger phrases users would say, such as "Use when the user wants to run APImetrics checks, monitor an API, inspect test results, or schedule alerts."

Keep the third-person voice but tighten "Manage data, records, and automate workflows" to specific APImetrics operations to lift specificity from 3 to 4-5.

Dimension	Reasoning	Score
Specificity	The phrase "Manage data, records, and automate workflows" names the domain and a few actions, but those actions are generic rather than concrete, matching the score-3 anchor of naming the domain with 1-2 actions that are not comprehensive.	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 APImetrics data"), but the "when" is generic rather than tied to concrete trigger phrases, fitting the score-4 anchor where the "when" could be more explicit.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with APImetrics data" relies on repeating the product name and lacks the natural synonyms or variations a user might actually say, matching the score-3 anchor of relevant but incomplete keyword coverage.	3 / 5
Distinctiveness Conflict Risk	"APImetrics" is a specific named platform with a distinct trigger, so it is clearly distinguishable from other skills with minimal conflict risk, matching the score-5 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/apimetrics/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.