Name: watchman-monitoring
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

watchman-monitoring

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

Quality

66%

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

Quality

Content

75%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, anchored in executable Membrane CLI commands and a robust connection-state workflow. Its main weaknesses are mild verbosity in the intro/overview and inconsistent workflow numbering rather than any lack of concrete guidance.

Suggestions

Trim the opening paragraph that explains what Watchman Monitoring is and who uses it; assume that context or move it to one line.

Fix the workflow numbering so steps read as a coherent 1→2→3 sequence, and label the referenced "Step 2" section explicitly.

Merge or differentiate the redundant "Searching for actions" and "Popular actions" sections to remove repeated guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete CLI commands, but it opens by explaining what Watchman Monitoring is and who uses it, includes a sparse "Overview" list, and filler like "Use action names and parameters as needed." that could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready, executable commands for the full workflow (install, login, connection ensure, action list/run, request proxy) plus a clear flag table, covering the common cases.	5 / 5
Workflow Clarity	The connection-readiness flow has an explicit polling feedback loop with state-based error recovery (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but step numbering is inconsistent (a "1b" with no "1a" and a referenced "Step 2" that is never labeled).	4 / 5
Progressive Disclosure	The single-file skill is well-organized into clearly headed sections with no nested references, which is appropriate for its length; the "Popular actions" section redundantly overlaps "Searching for actions", a minor organization gap.	4 / 5
	Total	16 / 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 has an explicit "Use when" trigger and names a distinct product, but its action language is generic and its trigger-term coverage is narrow. It clears the bar for activation guidance while leaving the capability statement vague.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Watchman Monitoring actions such as "view check results, list devices and services, and run monitoring actions".

Add natural trigger synonyms and feature terms users would say, e.g. "checks", "devices", "services", "alerts", or "monitoring data".

Keep the explicit "Use when" clause but pair it with concrete capability phrases so both "what" and "when" are specific.

Dimension	Reasoning	Score
Specificity	The description names the Watchman Monitoring domain and a few action categories ("Manage data, records, and automate workflows"), but those actions are generic rather than concrete, matching the anchor for naming the domain with minimal or generic actions.	2 / 5
Completeness	It explicitly answers both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with Watchman Monitoring data"), but the "what" is vague rather than concrete, so it falls short of a 5.	4 / 5
Trigger Term Quality	It includes the core natural term "Watchman Monitoring" plus "data" and "records", but misses common variations, synonyms, and specific feature names (e.g. checks, devices, alerts) that appear in the body.	3 / 5
Distinctiveness Conflict Risk	Tying the trigger to the specific named product "Watchman Monitoring" makes it mostly distinct with minimal conflict risk, though the generic "manage data, records, and automate workflows" phrasing creates minor overlap with other data-management skills.	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/watchman-monitoring/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.