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

jobadder

Jobadder integration. Manage data, records, and automate workflows. Use when the user wants to interact with Jobadder 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/jobadder/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 body is a well-structured, actionable CLI integration guide with concrete commands and a useful connection-state feedback loop. Its main weaknesses are mild prose padding and the absence of any bundle files to offload the proxy flag reference or action discovery details.

Suggestions

Trim promotional/padded phrasing like 'so you can focus on the integration logic' and 'This is the fastest way to get a connection' to improve token efficiency.

Add an output-verification checkpoint after `membrane action run` (e.g. check the `output` field and error handling) to strengthen the workflow feedback loop.

Move the proxy flag table and action-discovery details into a reference file (e.g. references/proxy.md) and link to it from the body to deepen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands with brief context, but includes some unnecessary prose such as 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection' that could be trimmed.	3 / 5
Actionability	It provides concrete, copy-pasteable commands throughout (login, connection ensure, action list/run, request) plus a flag table, but placeholders like CONNECTION_ID and 'QUERY' require substitution, leaving minor gaps versus fully ready examples.	4 / 5
Workflow Clarity	The install -> login -> ensure connection -> poll for READY -> search actions -> run sequence is clear, and the BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR state branching acts as a feedback loop, though output verification after running actions is not addressed.	4 / 5
Progressive Disclosure	Content is organized into clear, navigable sections (Overview, Auth, Connecting, Searching, Running, Proxy, Best practices) with no nested references, but everything is inlined in one ~140-line file with no separation of the proxy flag reference or action catalog into bundle files.	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 is functional and includes an explicit trigger clause, but its capability wording ('manage data, records, and automate workflows') is generic and could name more concrete Jobadder-specific operations. It is distinct thanks to the product name yet light on specific actions and trigger variations.

Suggestions

Replace generic verbs with concrete Jobadder capabilities, e.g. 'Manage candidates, jobs, applications, placements, and companies in Jobadder'.

Expand the trigger with natural variations users would say, e.g. 'Use when the user wants to manage Jobadder candidates, jobs, applications, or placements'.

Tie the 'when' clause to specific CRM/ATS tasks (post a job, review applications, log placements) to sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	Phrases like 'Manage data, records, and automate workflows' name the Jobadder domain plus a couple of actions, but 'manage data, records' is generic rather than concrete, landing between the minimal-actions (2) and 1-2-concrete-actions (3) anchors.	3 / 5
Completeness	It states what it does ('Manage data, records, and automate workflows') and includes an explicit 'Use when the user wants to interact with Jobadder data' trigger, satisfying both what and when, though the 'when' is somewhat generic.	4 / 5
Trigger Term Quality	The product name 'Jobadder' appears as the primary natural keyword and 'interact with Jobadder data' is a usable phrase, but common variations or synonyms are missing, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Jobadder is a specific recruitment CRM giving it a clear niche with low conflict risk, but the generic action wording ('manage data, records') leaves minor overlap with adjacent CRM/recruitment 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/jobadder/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.