CtrlK
BlogDocsLog inGet started
Tessl Logo

hibob

HiBob integration. Manage Persons, Jobs, Goals, Tasks, Surveys, Polls and more. Use when the user wants to interact with HiBob data.

56

Quality

63%

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

Quality

Content

61%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 guide to driving HiBob through the Membrane CLI with strong command coverage. Its weaknesses are modest verbosity, unfilled placeholders in examples, and the absence of validation steps for destructive actions.

Suggestions

Add a validation/confirmation checkpoint before destructive actions (e.g., confirm employee identity and re-check before running terminate-employee or delete-time-off-request).

Trim explanatory filler such as the HiBob company overview and promotional phrasing about auth plumbing to improve token efficiency.

Include at least one fully filled action-run example (real connection id and a concrete action key) so the workflow is copy-paste ready end to end.

DimensionReasoningScore

Conciseness

The body is mostly efficient command examples and tables, but includes unnecessary filler such as the HiBob company description ('aims to modernize HR processes...') and padded phrasing like 'so you can focus on the integration logic rather than auth plumbing'.

3 / 5

Actionability

Provides concrete, copy-paste-ready commands for install, auth, connection, action search/run, and proxy, with a useful popular-actions table; minor gaps remain since examples use unfilled placeholders (CONNECTION_ID, <actionId>).

4 / 5

Workflow Clarity

The connection flow is well sequenced with state checkpoints and a poll-after-action feedback loop, but the skill exposes destructive operations (Terminate Employee, Delete Time Off Request) with no validation/confirmation step, which caps workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

The single SKILL.md is organized into clearly headed sections (install, auth, connect, search, run, proxy, best practices) with content appropriately inline for a CLI-integration skill; no bundle files exist and none are strongly needed, though the popular-actions table and proxy flags could optionally be split out.

4 / 5

Total

14

/

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 clearly identifies a distinct niche (HiBob) and provides both a what and a when clause. Its main weakness is generic action language ('Manage') and narrow trigger keyword coverage limited to the product name.

Suggestions

Replace the generic verb 'Manage' with concrete actions (e.g., 'create, update, search, and terminate employees; submit and cancel time-off requests').

Broaden the trigger phrase with natural variations users might say, such as 'HR data', 'employee records', 'time-off requests', or 'payroll'.

Drop 'and more' or replace it with the remaining specific capabilities to avoid vagueness.

DimensionReasoningScore

Specificity

Names the domain and many concrete resources ('Persons, Jobs, Goals, Tasks, Surveys, Polls') but the only action verb is the generic 'Manage ... and more', so concrete actions are not comprehensive.

3 / 5

Completeness

Both 'what' (HiBob integration managing listed resources) and 'when' ('Use when the user wants to interact with HiBob data') are present; the 'when' is explicit but could be more specific, matching the anchor 4 example.

4 / 5

Trigger Term Quality

The trigger 'Use when the user wants to interact with HiBob data' surfaces the natural keyword 'HiBob', but coverage is narrow (just the product name) with no synonyms or common variations.

3 / 5

Distinctiveness Conflict Risk

'HiBob' is a specific named HRIS platform giving a clear niche with distinct triggers and minimal conflict risk with other skills.

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.