CtrlK
BlogDocsLog inGet started
Tessl Logo

personio-recruiting

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

57

Quality

66%

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/personio-recruiting/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 body is a well-structured, command-rich guide to driving Personio Recruiting through the Membrane CLI, with a strong state-machine feedback loop for connection readiness. Its main weaknesses are a redundant repeated command, a lightly padded product intro, and a glitchy step-numbering scheme that keeps the workflow from being fully cohesive.

Suggestions

Remove the redundant `membrane action list` block in 'Popular actions' (it duplicates 'Searching for actions') or merge the two sections.

Trim or cut the opening paragraph describing what Personio Recruiting is, since Claude can infer the product's purpose from the API context.

Fix the step numbering (no 'Step 2' label, a '1b' with no '1a') and present install→auth→connect→search→run as a single coherent numbered sequence with the connection-state validation as an explicit checkpoint.

DimensionReasoningScore

Conciseness

The body is mostly efficient command-driven prose, but the intro paragraph explaining what Personio is ('cloud-based applicant tracking system designed to streamline the hiring process...') is over-explanation, and the `action list` command is repeated across 'Searching for actions' and 'Popular actions'; matching the 'mostly efficient but includes some unnecessary explanation or could be tightened' anchor; not a 4 because the redundancy and product-description padding are noticeable.

3 / 5

Actionability

It provides concrete, copy-paste-ready commands throughout (membrane login, connection ensure, action list, action run, request) plus a full proxy-flags table, matching 'mostly executable guidance; concrete code or commands with minor gaps'; not a 5 because examples rely on placeholders (CONNECTION_ID, actionId, QUERY) and never show a complete end-to-end run against a real recruiting action.

4 / 5

Workflow Clarity

The install→auth→connect→search→run sequence is clear, and the connection-readiness section has a genuine feedback loop (poll until READY, branch on CLIENT_ACTION_REQUIRED, re-poll after user action, handle CONFIGURATION_ERROR), matching 'clear sequence with most checkpoints present'; not a 5 because the steps are not unified into one numbered checklist and the numbering is glitchy ('skip to Step 2' with no Step 2, a '1b' with no '1a').

4 / 5

Progressive Disclosure

No bundle files exist, and the SKILL.md is organized into well-labeled sections (Overview, Working with, Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with content appropriate to a single CLI-usage file, matching 'good structure; most content is appropriately placed; minor organization gaps'; not a 5 because at ~140 lines a dedicated reference for the proxy flags or best practices could further trim the overview.

4 / 5

Total

15

/

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 correctly uses third person and answers both 'what' and 'when' with an explicit trigger tied to a distinct product name. Its weaknesses are generic capability verbs and limited trigger-term coverage that omits the natural recruiting vocabulary users would say.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete recruiting actions such as 'post job openings, track candidates, and manage requisitions'.

Broaden trigger terms to include natural user phrasing like 'candidates', 'job postings', 'applications', or 'hiring'.

Tighten the 'when' clause to name concrete trigger situations (e.g. 'Use when the user wants to list applicants, update candidate stages, or manage job postings in Personio').

DimensionReasoningScore

Specificity

Names the domain ('Personio Recruiting integration') and lists actions ('Manage data, records, and automate workflows'), but those actions are generic abstractions rather than concrete recruiting operations like 'post jobs' or 'track candidates', matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor; not a 4 because the actions lack specificity.

3 / 5

Completeness

Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Personio Recruiting data') are present, matching the 'has both what and when; when could be more explicit' anchor; not a 5 because the 'what' is generic and the trigger phrases are not concrete.

4 / 5

Trigger Term Quality

The only natural keyword is 'Personio Recruiting' and 'data'; it omits common variations users would actually say such as 'candidates', 'job postings', 'hiring', or 'applicants', matching the 'some relevant keywords but missing common variations' anchor; not a 4 because coverage is thin.

3 / 5

Distinctiveness Conflict Risk

'Personio Recruiting' is a specific named SaaS product with a clear niche and distinct triggers, giving minimal conflict risk with other skills; not below 5 because the product name alone disambiguates the skill.

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.