CtrlK
BlogDocsLog inGet started
Tessl Logo

peoplehr

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

56

Quality

64%

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/peoplehr/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.

The content is a well-structured, actionable guide to driving PeopleHR through the Membrane CLI, with a strong connection-state workflow and executable commands. Its main weaknesses are minor verbosity and the absence of explicit validation for destructive action runs.

Suggestions

Trim conceptual padding such as the opening 'PeopleHR is an HR management system...' paragraph and the auth-plumbing commentary to assume Claude's competence.

Add an explicit validation/checkpoint step for destructive or batch action runs (e.g. inspect output, confirm affected record count before applying broad changes).

Resolve the repeated discovery guidance between 'Searching for actions' and 'Popular actions' into a single clear section to avoid duplication.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete CLI commands, though a few sections pad with unnecessary explanation ('PeopleHR is an HR management system designed to streamline HR processes', 'so you can focus on the integration logic rather than auth plumbing').

4 / 5

Actionability

It provides concrete, executable membrane CLI commands with explained flags throughout, with only minor gaps such as repeated discovery guidance and unresolved CONNECTION_ID placeholders.

4 / 5

Workflow Clarity

The connection flow is a clearly sequenced poll-and-branch loop with recovery guidance for CLIENT_ACTION_REQUIRED and CONFIGURATION_ERROR states, though destructive action execution lacks an explicit verify step.

4 / 5

Progressive Disclosure

With no bundle files present, the single self-contained file is well organized into clear sections (Overview, Working with PeopleHR, Best practices) with no nested references, though some inline detail like the proxy flag table could warrant a separate reference.

4 / 5

Total

16

/

20

Passed

Description

53%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 identifies a distinct niche (PeopleHR) and includes an explicit use-when clause, but its capabilities are stated too generically and its trigger vocabulary is thin. It reads as a named-integration stub rather than a richly specified skill description.

Suggestions

Replace generic verbs with concrete PeopleHR actions, e.g. 'Manage employee records, track absence, assign training courses, and handle benefits'.

Add natural trigger terms users would say, such as 'employee records', 'absence management', 'HR data', or 'PeopleHR API'.

Tighten the 'when' clause to name concrete scenarios, e.g. 'Use when the user wants to query or update PeopleHR employee, absence, training, or benefit records.'

DimensionReasoningScore

Specificity

It names the PeopleHR domain but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete HR actions like tracking absence or managing employees.

2 / 5

Completeness

It states both a 'what' (PeopleHR integration managing data, records, workflows) and an explicit 'when' ('Use when the user wants to interact with PeopleHR data'), though the 'what' is somewhat generic.

4 / 5

Trigger Term Quality

Only 'PeopleHR data' serves as a natural keyword; it lacks common synonyms and natural phrases a user would actually say such as 'employee records', 'absence', or 'HR'.

2 / 5

Distinctiveness Conflict Risk

'PeopleHR' names a distinct niche application with clear triggers, making it unlikely to fire for the wrong skill.

5 / 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.