Name: jobscore
Rating: 55.2 (1 reviews)
Author: membranedev

jobscore

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

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/jobscore/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 delivers concrete, executable membrane CLI commands and a clear connection-setup workflow with state-aware polling. It is slightly verbose in places and would benefit from real JobScore action examples and tighter prose.

Suggestions

Trim the introductory ATS explanation and filler phrases ('fastest way to get a connection', 'focus on the integration logic') to save tokens.

Show one or two concrete JobScore action examples (e.g. listing candidates or creating a job) instead of only generic membrane action-list/run patterns.

Clarify the 'Step 2' reference by labeling the action-search/run sections as the next step, and add a brief note on handling action-run errors.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command documentation, but the opening paragraph explaining what an ATS is, filler like 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection', and a 'Popular actions' section that repeats the action-list command could be tightened.	3 / 5
Actionability	It provides copy-pasteable membrane commands with realistic flags and a proxy options table, but relies on placeholders (CONNECTION_ID, QUERY) and shows no actual JobScore-specific action examples, fitting 'mostly executable guidance with minor gaps'.	4 / 5
Workflow Clarity	There is a clear install → authenticate → connect → search → run sequence with a connection-state feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED), though action-run error handling and the unlabeled 'Step 2' reference leave minor validation gaps.	4 / 5
Progressive Disclosure	The skill is well-organized into labeled sections with no nested references and all content appropriately inline for a self-contained skill of this size, fitting 'good structure; most content appropriately placed; minor organization gaps'.	4 / 5
	Total	15 / 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 names the target product and includes an explicit 'Use when' trigger, but its capability list is generic ('Manage data, records, and automate workflows') rather than concrete ATS actions. Adding specific JobScore verbs and richer trigger keywords would meaningfully raise it.

Suggestions

Replace the generic verbs with concrete JobScore capabilities, e.g. 'manage job postings, track candidates, and review submissions'.

Expand the 'Use when' clause with natural trigger terms users say: candidates, applicants, hiring, recruiting, or ATS.

Mention the record types users interact with (jobs, candidates, submissions) to sharpen distinctiveness and trigger matching.

Dimension	Reasoning	Score
Specificity	The description lists only generic actions ('Manage data, records, and automate workflows') rather than concrete JobScore-specific capabilities like candidate tracking or job-posting management, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states both what it does and when to use it ('Use when the user wants to interact with JobScore data'), satisfying the both-what-and-when bar, though the 'what' is generic and the 'when' could name more trigger scenarios.	4 / 5
Trigger Term Quality	It includes the 'JobScore' keyword and a 'Use when' trigger, but omits natural ATS terms users would actually say such as candidates, applicants, hiring, or recruiting, so it fits 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product JobScore gives it a clear niche with low conflict risk, but the generic action phrasing ('Manage data, records') leaves minor overlap with other data-management skills, fitting 'mostly distinct; minor overlap risk'.	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/jobscore/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.