Name: intellihr
Rating: 53.6 (1 reviews)
Author: membranedev

intellihr

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

Quality

60%

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

Quality

Content

66%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 strong, executable CLI integration guide with a clear connection workflow and state-based branching. Its main weaknesses are a low-value bare-noun entity list that dilutes conciseness and the absence of validation guidance for destructive proxy/action operations.

Suggestions

Trim or repurpose the 35-item entity list: either explain when to use each object or move it to a references/ file, since bare nouns add tokens without actionable guidance.

Add an explicit validation step for proxy and action operations that can mutate data (POST/PUT/PATCH/DELETE), e.g. re-fetch the affected record to confirm the change.

Remove the generic 'cloud-based HR software platform' intro line, which restates knowledge Claude already has.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete CLI commands, but the 35-item bare-noun entity list and the 'cloud-based HR software platform' intro add content that earns little per token, matching the 'mostly efficient with some unnecessary explanation' anchor.	3 / 5
Actionability	It provides copy-paste-ready commands for install, auth, connection, action search/run, and proxy with a flags table, but the bare entity list offers no concrete guidance on mapping intents to those entities, leaving a minor gap below the fully-executable anchor.	4 / 5
Workflow Clarity	The install-auth-connect-search-run sequence is clear with explicit state branching (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) as a feedback loop, but proxy POST/PUT/PATCH/DELETE and action runs lack an explicit verify step, matching the 'clear sequence with minor validation gaps' anchor.	4 / 5
Progressive Disclosure	No bundle files exist or are referenced, but the single-file body is well-sectioned into overview, install, auth, connecting, actions, and best practices; the entity list and flag options could be split out, matching the 'good structure with minor organization gaps' anchor.	4 / 5
	Total	15 / 20 Passed

Description

55%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 includes an explicit 'Use when...' trigger and names the IntelliHR niche, giving it solid completeness and distinctiveness. Its weakness is generic verb-based actions and thin trigger-term coverage, which keep specificity and trigger quality in the mid range.

Suggestions

Replace abstract verbs ('Manage data, records, and automate workflows') with concrete operations users would request, e.g. 'Look up employee records, submit and approve leave, run payroll, and trigger onboarding workflows'.

Expand trigger terms with natural entity keywords and synonyms users say, such as 'employees, leave/absence, timesheets, performance reviews, onboarding'.

Tighten the 'Use when' clause to reference concrete IntelliHR objects so it activates on the right requests.

Dimension	Reasoning	Score
Specificity	It names the IntelliHR domain and gestures at 'Manage data, records, and automate workflows', but the actions are abstract verbs rather than concrete operations, matching the anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	Both a 'what' (IntelliHR integration; manage data, records, automate workflows) and an explicit 'Use when...' clause are present, though the trigger could be more specific, matching the anchor for both present with a slightly vague 'when'.	4 / 5
Trigger Term Quality	It includes the natural trigger 'Use when the user wants to interact with IntelliHR data' and the brand term, but lacks synonyms and the concrete entity terms (employees, leave, timesheets) users would actually say.	3 / 5
Distinctiveness Conflict Risk	The named IntelliHR niche and app-specific trigger make it mostly distinct with only minor overlap risk against generic HR tools, matching the 'mostly distinct' anchor rather than the fully comprehensive niche anchor.	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/intellihr/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.