Name: vwork
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

vwork

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

Quality

72%

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/vwork/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 body is a lean, highly actionable guide with concrete CLI commands and a clear connection-readiness workflow including validation checkpoints; only minor conciseness and section-navigation gaps hold it back.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with copy-paste commands and a tight flags table, though the opening 'VWork is a field service management software...' sentence and the entity overview list explain context Claude could infer or look up.	4 / 5
Actionability	Fully executable, copy-paste ready CLI commands throughout (install, login, connection ensure/get, action list/run, request) plus a complete flags table covering the common proxy cases.	5 / 5
Workflow Clarity	Clear install→authenticate→connect→search→run sequence with explicit state-checking checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED polling loop); the 'skip to Step 2' reference has no matching Step 2 header, a minor navigation gap.	4 / 5
Progressive Disclosure	Well-organized single-file skill with clear section headers and no broken or nested references (no bundle files present); the inline proxy flags table and clientAction detail are slightly dense but appropriately placed given no external references.	4 / 5
	Total	17 / 20 Passed

Description

62%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 is third-person, has an explicit 'Use when' trigger, and names a distinct product, but its action verbs are generic and it omits the concrete field-service capabilities that would make triggers and specificity stronger.

Suggestions

Replace generic verbs with concrete VWork capabilities, e.g. 'Schedule jobs, dispatch technicians, and track job progress in VWork'.

Expand the trigger clause with natural user phrases, e.g. 'Use when the user wants to schedule jobs, dispatch field workers, or query VWork records'.

Add the API surface or core entity types (jobs, workers, customers) to sharpen what the skill actually does.

Dimension	Reasoning	Score
Specificity	Names the domain (VWork) and a few actions ('Manage data, records, and automate workflows'), but the actions are generic and abstract rather than concrete operations like 'schedule jobs' or 'dispatch technicians'.	3 / 5
Completeness	States both what ('Manage data, records, and automate workflows') and an explicit when ('Use when the user wants to interact with VWork data'); the when clause is present but could be more specific about the triggering scenarios.	4 / 5
Trigger Term Quality	Includes relevant keywords ('VWork', 'data', 'records', 'interact with VWork data') but lacks natural synonyms or the concrete field-service terms a user would actually say (jobs, technicians, dispatch, scheduling).	3 / 5
Distinctiveness Conflict Risk	VWork is a specific named product giving it a clear niche and distinct trigger, though the generic 'manage data, records, and automate workflows' verbs create minor overlap risk with general data skills.	4 / 5
	Total	14 / 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/vwork/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.