Name: testmonitor
Rating: 62.4 (1 reviews)
Author: membranedev

testmonitor

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

Quality

74%

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

Quality

Content

82%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 copy-paste-ready Membrane CLI commands and a clear connection workflow with validation checkpoints. Its main weaknesses are minor: a dangling "Step 2" reference, disjoint section numbering, and a few non-essential framing sentences.

Suggestions

Resolve the dangling "Step 2" reference: either add a clearly numbered "Step 2" section or reword the "skip to Step 2" guidance so the next step is unambiguous.

Fix section numbering (the "#### 1b." heading has no "1a.") so the connection sequence reads as a coherent numbered flow.

Trim the introductory paragraph explaining who uses TestMonitor and the "focus on the integration logic rather than auth plumbing" commentary to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is efficient with concrete commands and a tidy connection-state table, with only minor over-explanation (the intro paragraph on who uses TestMonitor and "focus on the integration logic rather than auth plumbing"), fitting "efficient; minor instances of over-explanation that could be trimmed" above 3 but below a lean 5.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands covering the common cases (install, login, connection ensure with polling, action list/run with JSON input, proxy with a flag table), matching the "fully executable; copy-paste ready" top anchor.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with polling and feedback loops (interpret READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after user action), but the referenced "Step 2" is never defined and section numbering is disjoint ("#### 1b." with no 1a), minor validation/sequencing gaps that keep it below 5.	4 / 5
Progressive Disclosure	It is a single, self-contained integration guide organized into clear, well-labeled sections with easy navigation and no external bundle files; structure is good but it is somewhat dense with no signaled references, fitting "good structure; minor organization gaps" at 4 rather than the clearly-split 5.	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 clearly identifies its niche (TestMonitor) and answers both what and when, but the actions are generic and the trigger terms lack natural synonyms users would actually say. Tightening the action verbs and adding concrete trigger phrases (test cases, test runs, QA) would lift completeness and trigger quality.

Suggestions

Replace generic verbs like "Manage data, records" with concrete actions users perform in TestMonitor (e.g., "create and run test cases, log test results, track requirements").

Expand the "Use when" clause with concrete triggers users actually say, such as "Use when the user mentions test cases, test runs, QA testing, or test management in TestMonitor."

Add common synonyms/file-context terms (test plans, test results, QA) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the TestMonitor domain plus a few actions ("Manage data, records, and automate workflows"), but the actions are generic ("manage") rather than concrete, fitting the "1-2 concrete actions, not comprehensive" anchor and falling short of 4's "several specific actions."	3 / 5
Completeness	It states both a clear "what" ("TestMonitor integration. Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with TestMonitor data"), but the "when" is generic and lacks concrete trigger scenarios, so it does not reach 5.	4 / 5
Trigger Term Quality	"TestMonitor" and "data, records" provide some relevant keywords, but common natural variations a user would say (test cases, test runs, QA, testing) are missing, matching the "some relevant keywords but missing synonyms" anchor rather than 4's fuller coverage.	3 / 5
Distinctiveness Conflict Risk	Naming a specific niche product ("TestMonitor integration") gives it a clear niche with distinct triggers and minimal conflict risk with other skills, matching the top 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/testmonitor/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.