Name: servicem8
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

servicem8

ServiceM8 integration. Manage Organizations, Users, Goals, Filters. Use when the user wants to interact with ServiceM8 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/servicem8/SKILL.md

Quality

Content

66%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 with copy-paste CLI commands and a clear connection workflow, but it is held back by moderate verbosity, a monolithic single-file structure with no progressive disclosure, and minor validation gaps in the run/proxy workflow.

Suggestions

Add an explicit validation checkpoint after running actions or proxy requests (e.g., check the response `output`/error field and retry or surface clientAction before proceeding) to close the workflow feedback loop.

Split detailed reference material (the proxy flag table, action schema descriptions, clientAction state handling) into separate reference files linked from a concise overview to improve progressive disclosure.

Tighten redundant sections (e.g., the duplicated action-listing commands in 'Searching for actions' and 'Popular actions') and trim the introductory paragraph explaining what ServiceM8 is, which Claude can infer.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and a focused flag table, but it includes introductory explanation of what ServiceM8 is and re-states similar action-listing commands in both 'Searching for actions' and 'Popular actions' sections, which could be tightened; matches 'mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	It provides copy-paste ready, fully executable CLI commands for install, login, connection, action listing/running, and proxy requests, plus a concrete options table, covering the common cases; matches the anchor for fully executable copy-paste ready commands covering common cases.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with state polling and a 'skip to Step 2' checkpoint plus remediation guidance for CLIENT_ACTION_REQUIRED, but there is no explicit validate-after-run feedback loop and the 'Step 2' target is not clearly defined, leaving minor validation gaps; matches 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	There are no bundle files and the SKILL.md is a single monolithic document with overview, setup, auth, connection, actions, proxy, and best practices all inlined; it has section structure but content that could live in separate references is inline, matching 'some structure but could be better organized; content that should be separate is inline'.	3 / 5
	Total	15 / 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 the ServiceM8 niche and provides an explicit use-when clause, making it distinct and complete. It is held back by a single generic verb ('Manage') over a noun list and limited natural trigger-term variation.

Suggestions

Replace the single generic verb 'Manage' with several distinct concrete actions (e.g., 'Create and update jobs, schedule staff, send quotes and invoices, manage clients') to raise specificity.

Add natural trigger synonyms users would say, such as 'jobs', 'scheduling', 'invoicing', 'field service', or 'quotes', beyond just 'ServiceM8'.

Make the 'when' clause more specific (e.g., 'Use when the user wants to query or update ServiceM8 jobs, clients, quotes, or invoices') to sharpen the trigger.

Dimension	Reasoning	Score
Specificity	Names the domain (ServiceM8) and lists concrete action objects (Manage Organizations, Users, Goals, Filters), but the actions are a single generic verb ('Manage') applied to a noun list rather than several distinct concrete actions, matching the anchor that names the domain with 1-2 concrete actions but is not comprehensive.	3 / 5
Completeness	It has both a 'what' (Manage Organizations, Users, Goals, Filters) and an explicit 'when' ('Use when the user wants to interact with ServiceM8 data'), with the 'when' being explicit but fairly generic, matching the anchor for both present with the when being reasonably explicit.	4 / 5
Trigger Term Quality	It includes 'ServiceM8' and 'interact with ServiceM8 data' as relevant keywords, but lacks common variations, synonyms, or file extensions and uses a generic trigger phrase, fitting 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	It names a specific niche product (ServiceM8) with distinct triggers tied to that product, so it is unlikely to fire for an unrelated skill, matching the anchor for a clear niche with minimal conflict risk.	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/servicem8/SKILL.md
Commit: f484c82

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