CtrlK
BlogDocsLog inGet started
Tessl Logo

personio

Personio integration. Manage Persons, Companies, Teams, CompensationChanges, PerformanceReviews. Use when the user wants to interact with Personio data.

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

75%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.

Highly actionable CLI commands with a well-sequenced connection workflow and feedback loop; the main drag is an unnecessary marketing intro and a broken step cross-reference.

Suggestions

Remove or heavily trim the opening paragraph describing what Personio is as a business — Claude doesn't need the HR-software context and it wastes tokens.

Fix the broken "skip to Step 2" reference: either label the subsequent sections as numbered steps or relabel the pointer to the actual section (Searching for actions).

Add a brief verification note for destructive actions (e.g., confirm the record ID, or list-before-delete) so update/delete/create calls have an explicit checkpoint.

DimensionReasoningScore

Conciseness

Mostly efficient command-driven content, but the opening marketing paragraph ("Personio is an all-in-one HR software designed to streamline HR processes...") explains business context Claude doesn't need and could be trimmed.

3 / 5

Actionability

Fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) covering the common workflow cases, plus concrete proxy flag tables.

5 / 5

Workflow Clarity

Clear sequenced connection workflow with a state-based checkpoint and a poll-retry feedback loop, but the "skip to Step 2" cross-reference points to a non-existent labeled step and destructive actions (delete/update/create) get no verification guidance.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and easy navigation, but the 20-row Popular actions table is bulk reference content inlined in a single file with no reference split; minor organization gap.

4 / 5

Total

16

/

20

Passed

Description

82%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.

A concise, third-person description with an explicit Use-when clause and a distinct named-app trigger; its main weakness is the generic verb "Manage" and entity names that don't match Personio's actual resources.

Suggestions

Replace the generic verb "Manage" with concrete action verbs (e.g., create, list, update, delete employees and absences) to lift specificity.

Align entity names with Personio's actual resources (Employees, Absences, Departments, Attendances) so trigger terms match what users naturally say.

Add common synonyms like "HR", "employees", "time off", or "attendance" to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Names the Personio domain and several concrete resource types ("Manage Persons, Companies, Teams, CompensationChanges, PerformanceReviews") but relies on the single generic verb "Manage" rather than naming concrete actions (create, list, update, delete).

3 / 5

Completeness

Explicitly answers both what ("Personio integration. Manage ...") and when ("Use when the user wants to interact with Personio data") with a concrete trigger phrase, matching the top anchor.

5 / 5

Trigger Term Quality

Good keyword coverage with the app name "Personio", the interaction phrasing "interact with Personio data", and multiple entity categories; a few natural synonyms users would say (employees, HR, attendance, time off) are missing.

4 / 5

Distinctiveness Conflict Risk

Naming a specific SaaS app (Personio) gives it a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

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.