Name: rippling-hr
Rating: 61.6 (1 reviews)
Author: membranedev

rippling-hr

Rippling HR integration. Manage Employees, Companies, PayrollRuns, Reports. Use when the user wants to interact with Rippling HR data.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/rippling-hr/SKILL.md

Quality

Content

72%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 skill body is highly actionable with copy-paste CLI commands and a well-structured connection workflow, but it inlines a large action catalog that belongs in a reference file and lacks validation guidance for destructive operations.

Suggestions

Add a validation/confirmation step before destructive actions (e.g. 'Before running delete-group or update-group, confirm the target ID with the user and re-list to verify the result').

Move the 'Popular actions' table into a references/ file (e.g. ACTIONS.md) and keep SKILL.md as an overview with a one-level-deep pointer.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, executable commands and tables with only minor over-explanation (e.g. 'so you can focus on the integration logic rather than auth plumbing') that could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, proxy) with concrete flags and JSON parameter examples covering the common cases.	5 / 5
Workflow Clarity	The connection flow has explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but destructive actions like delete-group are run via the generic action-run command with no validation or confirmation step, so the rubric cap of 3 for destructive/batch operations without validation applies.	3 / 5
Progressive Disclosure	Sections are reasonably organized, but no bundle/reference files exist and the large 20-row 'Popular actions' table is inlined rather than split into a separate reference, leaving structure that could be better organized.	3 / 5
	Total	15 / 20 Passed

Description

73%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 the Rippling HR niche and answers both what and when, using clean third-person voice. Its main weakness is the generic 'Manage' verb, which leaves the specific capabilities underspecified.

Suggestions

Replace the generic 'Manage' with concrete verbs, e.g. 'List, create, and update Employees, Companies, PayrollRuns, and Reports'.

Expand the trigger clause with concrete phrases users actually say, e.g. 'Use when the user wants to query employees, run payroll, or pull HR reports from Rippling'.

Dimension	Reasoning	Score
Specificity	Names four concrete entities ('Employees, Companies, PayrollRuns, Reports') but the single verb 'Manage' is generic rather than enumerating concrete actions like create/list/update, so it sits at the domain-plus-actions-but-not-comprehensive level.	3 / 5
Completeness	Both 'what' (manage the listed HR entities) and 'when' ('Use when the user wants to interact with Rippling HR data') are present, but the trigger clause is generic rather than enumerating concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes natural terms a user would say ('Rippling HR', 'Employees', 'Companies', 'PayrollRuns', 'Reports') with good coverage, though common synonyms/extensions like 'payroll', 'leave', or 'HR data' phrasing variations are partly missing.	4 / 5
Distinctiveness Conflict Risk	'Rippling HR' is a clearly named niche with distinct triggers, making overlap with other skills minimal.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/rippling-hr/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.