CtrlK
BlogDocsLog inGet started
Tessl Logo

jazzhr

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

62

Quality

74%

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/jazzhr/SKILL.md
SKILL.md
Quality
Evals
Security

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 highly actionable with executable CLI commands and a well-sequenced, state-validated connection workflow, remaining mostly concise with only minor padding. Organization is solid for a single-file skill, with slight room to factor out reference material.

DimensionReasoningScore

Conciseness

The body is mostly lean commands and flag tables, but includes minor over-explanation such as the introductory paragraph describing what JazzHR is and phrasing like "so you can focus on the integration logic rather than auth plumbing," fitting the efficient-with-minor-trim anchor.

4 / 5

Actionability

It provides copy-paste-ready, fully executable commands throughout (install, login, connection ensure, action list/run, request with flags) covering the common cases, matching the top anchor for fully executable guidance.

5 / 5

Workflow Clarity

The connection setup is a clear sequence with explicit state validation and a poll-after-action feedback loop, but the later "Searching for actions"/"Popular actions"/"Running actions" sections are loosely tied together with minor sequencing gaps, fitting the clear-sequence-with-minor-gaps anchor.

4 / 5

Progressive Disclosure

Content is organized into clear, well-labeled sections in a single file with no external bundle files referenced, which is appropriately placed though the proxy flag table and connection-state detail could arguably live in separate references, matching the good-structure-with-minor-gaps anchor.

4 / 5

Total

17

/

20

Passed

Description

66%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 a third-person statement that covers both what and when and is distinct due to the named product, but its action language is generic and it omits natural recruiting-domain synonyms that would strengthen trigger matching.

Suggestions

Replace generic verbs with concrete JazzHR operations, e.g. "Post jobs, track applicants, and manage candidates."

Add natural trigger terms users say, such as "applicants," "candidates," "job postings," "recruiting," or "ATS."

Sharpen the "when" clause to concrete triggers, e.g. "Use when the user wants to manage applicants, jobs, or hiring workflows in JazzHR."

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the JazzHR domain plus a few actions, but the actions are generic ("manage data," "automate workflows") rather than concrete operations like posting jobs or tracking candidates, matching the anchor for naming domain and 1-2 actions without comprehensive coverage.

3 / 5

Completeness

It states both what ("JazzHR integration. Manage data, records, and automate workflows") and when ("Use when the user wants to interact with JazzHR data"), but the trigger clause is generic and could be more specific, matching the anchor for both present with room to sharpen the "when."

4 / 5

Trigger Term Quality

The keyword "JazzHR" is present and specific, but common natural synonyms a user would say (applicants, candidates, jobs, recruiting, ATS) are absent, fitting the anchor for some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

Naming a specific branded product (JazzHR) gives it a clear niche with distinct triggers and minimal conflict risk with other skills, matching the top anchor.

5 / 5

Total

15

/

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.