CtrlK
BlogDocsLog inGet started
Tessl Logo

jobdiva

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

55

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/jobdiva/SKILL.md
SKILL.md
Quality
Evals
Security

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 a well-structured, command-rich integration guide with a sensible connect-and-poll workflow and a clear proxy escape hatch. Its main weaknesses are mild verbosity and a broken 'Step 2' cross-reference that slightly muddies the workflow.

Suggestions

Trim the opening JobDiva description and informal asides ('burn less tokens', 'used best with your harness') to tighten token efficiency.

Fix the broken cross-reference: either label a 'Step 2: Search and run actions' heading or remove the 'skip to Step 2' pointer.

Consider moving the detailed connection-state handling and proxy flag table into a short reference section or file to keep the main flow scannable.

DimensionReasoningScore

Conciseness

The body is mostly command-focused and useful, but the opening ATS description, the headless-auth prose, and padded phrasing ('burn less tokens', 'used best with your harness') could be trimmed, fitting 'mostly efficient but includes some unnecessary explanation.'

3 / 5

Actionability

It provides concrete, copy-paste-ready commands throughout (login, connection ensure, action run, proxy with a flags table), with only minor placeholders like CONNECTION_ID keeping it from fully executable across all cases.

4 / 5

Workflow Clarity

A clear install→authenticate→connect→poll→search→run sequence exists with a feedback loop (poll until READY, re-poll after client action); the dangling 'skip to Step 2' reference with no labeled Step 2 is a minor validation/navigation gap.

4 / 5

Progressive Disclosure

The skill is a single self-contained file with well-organized section headers and no nested references; no bundle files are present to verify, so it scores as good single-level structure with 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 correctly pairs a what/when structure and leverages a distinctive proper-noun trigger, but its capability language is generic rather than concrete. Tightening the action list with specific JobDiva operations would lift specificity and completeness.

Suggestions

Replace generic verbs with concrete JobDiva actions, e.g. 'Search candidates, manage job submissions, and pull reports from JobDiva.'

Add natural synonyms/trigger terms such as 'ATS', 'recruiting', 'candidates', or 'job orders' so users phrase the need in varied ways.

Tighten the 'when' clause to name specific intents, e.g. 'Use when the user wants to query JobDiva candidates, jobs, or submissions.'

DimensionReasoningScore

Specificity

It names the JobDiva domain but the actions ('Manage data, records, and automate workflows') are generic and lack concrete verbs like the anchor-3 example, so it fits 'names domain but actions minimal or generic.'

2 / 5

Completeness

Both 'what' (JobDiva integration, manage data/records/workflows) and 'when' ('Use when the user wants to interact with JobDiva data') are present with an explicit trigger, but the 'what' is generic rather than concrete, so it falls short of anchor 5.

4 / 5

Trigger Term Quality

'JobDiva' is a natural keyword a user would say, but the description offers no synonyms or variations (e.g. 'ATS', 'recruiting', 'candidates'), matching 'some relevant keywords but missing common variations.'

3 / 5

Distinctiveness Conflict Risk

The 'JobDiva' proper noun carves a clear niche with minimal conflict risk, though the surrounding generic data/records language leaves minor overlap risk with general data-management skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.