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

Blog Docs Log in Get started

jobber

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

Quality

68%

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

Quality

Content

78%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 delivers highly actionable, executable CLI guidance with a clear connection workflow and validation through state polling, but it is a monolithic file with no progressive disclosure into reference materials.

Suggestions

Move the long flat list of Jobber entities into a separate references file and keep SKILL.md focused on the integration workflow.

Add an explicit validate-fix-retry note for CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR paths to strengthen the feedback loop.

Trim the entity-name block to the core object model used in common actions, deferring the full list to a reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with executable CLI commands and a compact flag table, though the long flat list of Jobber entity names and a few explanatory sentences could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands (install, login, connection ensure/get, action list/run, request proxy) with concrete flags and a complete options table covering the common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-driven branching (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and explicit polling, though not every error path has a validate-fix-retry loop.	4 / 5
Progressive Disclosure	It is a single well-sectioned SKILL.md with no bundle files to split into, but the long inline entity list and connection-state reference could arguably live in separate reference files, leaving organization only modestly split.	3 / 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 clearly identifies the Jobber domain and includes an explicit trigger clause, but the capabilities are described generically rather than naming Jobber-specific operations.

Suggestions

Replace generic verbs with concrete Jobber actions, e.g. "Manage jobs, clients, quotes, invoices, and scheduling in Jobber."

Expand the trigger to concrete phrases users would say, e.g. "Use when the user wants to manage Jobber jobs, clients, quotes, invoices, or schedules."

Avoid over-broad terms like "Manage data, records" that overlap with generic data-management skills.

Dimension	Reasoning	Score
Specificity	Names the domain ("Jobber") but the actions ("Manage data, records, and automate workflows") are generic and minimal rather than concrete Jobber-specific capabilities like scheduling, invoicing, or client management.	2 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Jobber data"), but the "when" clause is generic rather than enumerating concrete trigger phrases.	4 / 5
Trigger Term Quality	The natural keyword "Jobber" appears and the trigger "interact with Jobber data" is reasonable, but common variations or synonyms a user might say are absent.	3 / 5
Distinctiveness Conflict Risk	The Jobber niche is distinct and unlikely to fire for unrelated skills, though the generic "Manage data, records" phrasing creates minor overlap risk with broad CRM/data 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/jobber/SKILL.md
Commit: f484c82

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