Name: workiz
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

workiz

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

Quality

67%

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

Quality

Content

68%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 concrete CLI commands and a well-structured connection workflow including state checkpoints and feedback loops. Its weaknesses are a low-value entity list that hurts token efficiency and a lack of validation guidance around destructive proxy/method operations.

Suggestions

Trim the bare entity list and the 'Workiz is a field service management software...' intro paragraph, or replace the list with a brief pointer to discover entities via `membrane action list`.

Add a validation/verification checkpoint before destructive proxy calls, e.g. 'For -X POST/PUT/PATCH/DELETE, confirm the target id with the user and re-fetch the resource to verify the change before proceeding.'

Consider moving the proxy flag table and action-search details into a short referenced file (e.g. REFERENCE.md) to enable true one-level-deep progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and procedural guidance, but includes an unnecessary intro paragraph explaining what Workiz is and a ~30-item bare entity list ("Client / Job / Lead / ...") that adds tokens without actionable value; fits 'mostly efficient but includes some unnecessary explanation'; not a 4 because the entity list is more than minor padding.	3 / 5
Actionability	Throughout the body are copy-paste-ready executable commands — `npm install -g @membranehq/cli@latest`, `membrane connection ensure ... --json`, `membrane action run ... --input '{...}'`, `membrane request ...` with a full flag table — covering install, auth, connection, action search/run, and proxy; fits 'fully executable; copy-paste ready; covers common cases'.	5 / 5
Workflow Clarity	The connection setup is well sequenced with state-based checkpoints and a poll→fix→re-poll feedback loop, but the proxy section explicitly enables destructive HTTP methods (POST/PUT/PATCH/DELETE) with no validation or verify-before-execute guidance; per the rubric's destructive-operation cap, workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	The body is a single file with clear, well-organized sections and no nested references, and the content stays overview-level by pointing to dynamic action discovery rather than inlining every action; not a 5 because everything is inline with no one-level-deep reference structure and the file exceeds the 50-line simple-skill threshold, not a 3 because structure and navigation are genuinely good.	4 / 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 cleanly identifies a distinct named-app niche and includes an explicit 'Use when...' trigger, satisfying both what and when. Its main weakness is generic action language ('manage data, records, automate workflows') that lacks concrete capability specificity.

Suggestions

Replace generic verbs with concrete Workiz capabilities, e.g. 'Create and manage jobs, invoices, estimates, and schedules; send messages and process payments' to lift specificity.

Add a couple of natural trigger variations, e.g. 'Use when the user wants to manage Workiz jobs, invoices, scheduling, or customer records.'

Dimension	Reasoning	Score
Specificity	Names the domain (Workiz) and lists several actions — "Manage data, records, and automate workflows" — but the actions are generic rather than concrete, matching the 'names domain and 1-2 actions but not comprehensive' anchor; not a 4 because the actions lack concrete specificity, not a 2 because multiple actions are named.	3 / 5
Completeness	Both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Workiz data") are present, with the 'when' explicit; not a 5 because the 'what' actions are generic rather than concrete trigger phrases, not a 3 because 'when' is explicitly stated.	4 / 5
Trigger Term Quality	The description captures the core natural term "Workiz" and the phrase "interact with Workiz data", but offers no synonyms, variations, or file extensions, fitting 'some relevant keywords but missing common variations'; not a 4 because coverage is thin beyond the app name.	3 / 5
Distinctiveness Conflict Risk	"Workiz integration" targets a specific named application, giving it a clear niche with minimal conflict risk against other skills; fits the 'clear niche with distinct triggers' 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/workiz/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.