Name: jobvite
Rating: 56.8 (1 reviews)
Author: membranedev

jobvite

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

Quality

65%

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

Quality

Content

67%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 Membrane CLI commands and a well-sequenced connection workflow, but it is held back by a padded intro, redundant sections, incoherent step numbering, and the absence of result-verification. Fixing the numbering and trimming the explanatory opening would meaningfully raise the score.

Suggestions

Fix the incoherent step numbering: replace the lone '1b' heading and the undefined 'Step 2' references with a clean numbered sequence (1. Install, 2. Authenticate, 3. Connect, 4. Discover, 5. Run).

Trim the opening paragraph describing what Jobvite is and remove the redundant 'Popular actions' section that restates the discovery command, since Claude already understands the domain from the description.

Add an explicit verification step after running actions or proxy requests (e.g., check the `output`/response status and confirm the expected record was created or updated) to close the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands, but the opening paragraph explaining what Jobvite is and redundancies (the 'Popular actions' section restates the discovery command) add padding Claude does not need, fitting the 'mostly efficient but includes unnecessary explanation' anchor.	3 / 5
Actionability	It provides concrete, copy-paste-ready membrane commands plus a proxy-flags table covering common cases, but examples rely on placeholders (CONNECTION_ID, actionId) with no fully concrete end-to-end example, so it is mostly executable rather than fully copy-paste ready.	4 / 5
Workflow Clarity	The install→auth→connect→search→run sequence is clear with state-checkpoint feedback loops (BUILDING/READY/CLIENT_ACTION_REQUIRED), but the numbering is incoherent ('1b' with no clear 1a, references to an undefined 'Step 2') and there is no verification step for action-run results.	4 / 5
Progressive Disclosure	The single file is well-organized into clear sections with no broken or deeply nested references (no bundle files exist), but at ~140 lines with no external split and some thin sections ('Jobvite Overview' lists entities then 'Use action names and parameters as needed'), it has minor organization gaps rather than ideal one-level-deep disclosure.	4 / 5
	Total	15 / 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 answers both what and when and is anchored to a distinct brand, but its action language is generic and its trigger phrases lack concrete variations. Tightening the verbs and adding concrete trigger terms would lift it toward the top anchors.

Suggestions

Replace generic verbs with concrete capabilities (e.g., 'Search candidates, manage applications and jobs, and trigger recruiting workflows') to improve specificity.

Add concrete trigger phrases beyond the brand name, such as 'Use when the user mentions candidates, applications, job postings, or hiring workflows in Jobvite'.

Avoid the generic 'Manage data, records' phrasing, which overlaps with other CRM/HR integration skills and weakens distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain (Jobvite) and a few actions ('Manage data, records, and automate workflows'), but the actions are generic verbs applied to vague nouns rather than concrete capabilities, matching the anchor for naming a domain with 1-2 non-comprehensive actions.	3 / 5
Completeness	Both 'what' ('Jobvite integration. Manage data, records, and automate workflows.') and 'when' ('Use when the user wants to interact with Jobvite data.') are present, but it is not a 5 because the 'when' trigger phrase is generic rather than enumerating concrete trigger phrases.	4 / 5
Trigger Term Quality	'Jobvite' is the natural brand term a user would say and appears in the trigger clause ('interact with Jobvite data'), but there are no synonyms or variations beyond the brand name, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Jobvite is a specific platform giving the skill a clear niche with distinct triggers, but the generic 'manage data, records, workflows' language creates minor overlap risk with other HR/CRM integration skills, so it is mostly distinct rather than minimal-conflict.	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/jobvite/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.