Name: insperity-premier
Rating: 59.2 (1 reviews)
Author: membranedev

insperity-premier

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

Quality

68%

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/insperity-premier/SKILL.md

Quality

Content

71%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 highly actionable with executable commands and a well-sequenced, validated connection workflow. Its weaknesses are minor over-explanation and the absence of any progressive disclosure split for a >150-line skill.

Suggestions

Trim editorial padding such as "so you can focus on the integration logic rather than auth plumbing" to keep the body lean.

Define the unlabeled "Step 2" referenced after READY, or restructure the connection steps as an explicit numbered list so the flow has no dangling reference.

Move the proxy flag table and action schema field list into a references/ file (e.g. REFERENCE.md) and link to it from the body to add one-level-deep progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but includes a few unnecessary editorial explanations ("so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection") that could be trimmed, fitting the mostly-efficient-with-some-over-explanation anchor.	3 / 5
Actionability	It provides copy-paste-ready commands across the full workflow (install, login, connection ensure, polling, action list/run, proxy flags table) with concrete parameter examples covering the common cases, matching the fully-executable anchor.	5 / 5
Workflow Clarity	The connection lifecycle is clearly sequenced with explicit polling/validation checkpoints and a retry-after-user-action feedback loop, but the referenced "Step 2" is never labeled, leaving a minor navigation gap that keeps it below the fully-checkpointed anchor.	4 / 5
Progressive Disclosure	The skill has clear section headers but is a single monolithic file with no external references and no bundle files; content that could live separately (the proxy flags table, action schema fields) is inlined, fitting the some-structure-but-could-be-better-organized anchor rather than the simple-skill 5 since it exceeds 50 lines.	3 / 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 is functional and clearly tied to a specific named platform, with an explicit "Use when" trigger clause that anchors distinctiveness. It is held back by generic capability language and limited trigger-term variety.

Suggestions

Replace generic verbs ("Manage data, records") with concrete Insperity Premier actions such as employee, paycheck, time-off, or benefits operations.

Add natural trigger synonyms users would say, e.g. "Use when the user asks about payroll, employee records, time-off requests, or benefits in Insperity Premier."

Dimension	Reasoning	Score
Specificity	Names the domain ("Insperity Premier") and a couple of actions ("Manage data, records, and automate workflows"), but the actions are generic and not comprehensive, fitting the domain-plus-1-2-actions anchor rather than the vague-only or fully-specific anchors.	3 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Insperity Premier data"), but the "what" is generic and the "when" could be more specific, placing it above the missing-when anchor but below the fully-explicit anchor.	4 / 5
Trigger Term Quality	The phrase "Use when the user wants to interact with Insperity Premier data" is a natural trigger using the product name, but it lacks synonyms, common variations, or file extensions, so keyword coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	The named platform "Insperity Premier" carves a clear niche with distinct triggers tied to a specific product, giving minimal overlap risk with other skills.	5 / 5
	Total	15 / 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/insperity-premier/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.