Name: trinet
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

trinet

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

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/trinet/SKILL.md

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 body is a well-structured, highly actionable CLI integration guide with strong executable command coverage and a clear connection workflow. Its main weaknesses are minor verbosity (an unnecessary platform intro and some command repetition) and a couple of sequencing gaps.

Suggestions

Trim the opening 'TriNet is a human resources platform...' paragraph, which restates domain knowledge Claude already has.

Remove the redundant `membrane action list` command in 'Popular actions' since the same command with full flags already appears under 'Searching for actions'.

Resolve the dangling 'Step 2' reference by explicitly labeling the searching/running sections as Step 2, and add a brief validation cue (e.g., check the `output`/`state` field) after action-run or proxy requests.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-focused and lean, but includes unnecessary explanation Claude already knows (the TriNet-is-an-HR-platform intro) and redundancy where the 'Popular actions' section re-states the search command already shown under 'Searching for actions'.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands across every common case — install, login (interactive and headless), connection ensure/wait, action list, action run with JSON params, and proxy requests with a concrete flags table — matching the 'fully executable, covers common cases' anchor.	5 / 5
Workflow Clarity	The connection workflow has explicit state checks and poll/retry feedback loops (BUILDING → poll, CLIENT_ACTION_REQUIRED → user acts → re-poll), but it references an unlabeled 'Step 2' and offers no validation checkpoint after running actions or proxy requests.	4 / 5
Progressive Disclosure	The skill is a self-contained single file organized into clear, logically ordered sections with no external references (none exist), placing content appropriately with only minor redundancy between the search and popular-actions sections.	4 / 5
	Total	16 / 20 Passed

Description

57%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 covers both what and when in third person, but leans on generic verbs ('manage data, records, automate workflows') rather than concrete TriNet-specific actions. It would benefit from named HR-domain trigger terms.

Suggestions

Replace generic verbs with concrete TriNet capabilities (e.g., 'manage employee records, run payroll, submit time-off requests, review benefits').

Add natural user trigger terms beyond 'TriNet data' — payroll, benefits, employee records, time off — so the skill surfaces when users phrase requests in HR language.

Make the 'when' clause more specific, e.g. 'Use when the user wants to query or update employee, payroll, benefits, or time-off data in TriNet.'

Dimension	Reasoning	Score
Specificity	The description names the TriNet domain but its actions ('Manage data, records, and automate workflows') are minimal and generic, matching the 'names the domain but actions are minimal or generic' anchor rather than the 1-2 concrete actions needed for a 3.	2 / 5
Completeness	It answers both what ('TriNet integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with TriNet data'), but the when clause is somewhat generic, fitting the 4 anchor rather than the explicit concrete triggers of a 5.	4 / 5
Trigger Term Quality	'TriNet' and 'TriNet data' are relevant keywords, but it omits the natural HR-domain synonyms users would actually say (payroll, benefits, employee, time off), so it falls short of the 4's 'good keyword coverage'.	3 / 5
Distinctiveness Conflict Risk	TriNet is a specific named platform giving it a clear niche with low conflict risk, but the generic action verbs ('manage data, records') create minor overlap with other data-management skills, keeping it below a 5.	4 / 5
	Total	13 / 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/trinet/SKILL.md
Commit: f484c82

Reviewed: 4 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.