Name: jobsoid
Rating: 64 (1 reviews)
Author: membranedev

jobsoid

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

Quality

76%

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/jobsoid/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 tight, executable guide to driving Jobsoid through the Membrane CLI, with concrete commands and a well-structured connection workflow including state-driven feedback loops. Its main weaknesses are minor chatty prose and inline reference material (entity list, flag table) that could be split out.

Suggestions

Replace the 'skip to Step 2' phrasing with an explicit, labeled step anchor so the install/auth/connect/run sequence is unambiguous.

Move the 23-item Jobsoid entity list and the proxy flag table into a references/ file and link to them from the body to improve progressive disclosure.

Trim explanatory asides ('so you can focus on the integration logic rather than auth plumbing') to keep the body token-lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands with light prose and avoids explaining concepts Claude already knows, though a few chatty sentences ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') could be trimmed. It does not reach 5 because of those minor padded asides.	4 / 5
Actionability	It provides copy-paste-ready commands throughout — install, login (incl. headless completion), connection ensure/get with --wait, action list/run with --input, and a proxy command with a full flag table — covering the common cases. Not below 5: examples are concrete and executable with realistic placeholders.	5 / 5
Workflow Clarity	There is a clear install → authenticate → connect → search → run sequence with explicit state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop after user action. Held at 4 because the prose references 'skip to Step 2' and a '1b' subsection without a clearly labeled Step 2, leaving a minor sequencing gap.	4 / 5
Progressive Disclosure	The single-file body is well organized into headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references. It is not a 5 because the inlined 23-item entity list and the proxy flag table are reference material that could live in a separate reference file, and no external references are signaled.	4 / 5
	Total	17 / 20 Passed

Description

70%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 with a clear 'Use when' trigger and a specific app name, but its capability language is generic ('manage data, records, automate workflows') rather than naming concrete Jobsoid operations. It is solid but could be sharper.

Suggestions

Replace generic actions with concrete Jobsoid operations, e.g. 'list jobs, search candidates, update application stages, and trigger workflows'.

Expand the trigger clause with natural synonyms, e.g. 'Use when the user wants to query Jobsoid, manage candidates/applications, or automate hiring workflows'.

Keep the third-person voice but ensure the 'what' lists measurable capabilities rather than 'manage data' abstractions.

Dimension	Reasoning	Score
Specificity	Names the Jobsoid domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete API-level capabilities. It is above score 2 (which expects only minimal/generic actions) but lacks the specific actions needed for a 4.	3 / 5
Completeness	It states both what ('Jobsoid integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Jobsoid data'). Not a 5 because the 'what' actions are generic and the 'when' trigger is a single phrase rather than multiple concrete trigger phrases.	4 / 5
Trigger Term Quality	The 'Use when the user wants to interact with Jobsoid data' clause plus the proper-noun 'Jobsoid' and 'data'/'workflows' give good natural keyword coverage users would actually say. It falls short of 5 because there are no synonyms or variations beyond the single 'interact with Jobsoid data' phrasing.	4 / 5
Distinctiveness Conflict Risk	Jobsoid is a specific named ATS, giving it a clear niche and low conflict risk with other skills. Held at 4 rather than 5 because the supporting action language is generic, so the distinctiveness rests almost entirely on the proper noun.	4 / 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/jobsoid/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.