Name: ukg-pro
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

ukg-pro

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

Quality

61%

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

Quality

Content

57%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 strongly actionable CLI integration guide with good connection-state feedback loops, but it is padded with product/marketing explanation, lacks validation before destructive data operations, and keeps all detail inline with no external references. Trimming exposition, adding a pre-write verification step, and a worked example would most improve it.

Suggestions

Add a validation checkpoint before destructive operations: before running write actions or proxy POST/PUT/DELETE, confirm the target with the user and verify the response output/record afterward, so workflow clarity clears the destructive-operations cap.

Trim concept explanation Claude already knows — drop the HCM/product intro paragraph and softening phrases like "auth plumbing" / "fastest way to get a connection" — to lift conciseness.

Add one worked end-to-end example with real-looking values (e.g. a concrete connection id and a sample QUERY intent) to move actionability from mostly-executable to fully copy-paste-ready.

Dimension	Reasoning	Score
Conciseness	Mostly command-driven and efficient, but it opens by explaining what UKG Pro is ("comprehensive human capital management (HCM) solution… entire employee lifecycle") and includes padding like "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection," so it matches anchor 3 rather than the leaner anchor 4.	3 / 5
Actionability	Abundant copy-paste-ready commands (install, login, connection ensure, action list/run, request) plus a flags table give mostly executable guidance; it stops short of anchor 5 because every example uses unresolved placeholders (CONNECTION_ID, QUERY, <actionId>) with no worked end-to-end example using real values.	4 / 5
Workflow Clarity	The connection setup has clear state-based feedback loops (poll until READY, retry after CLIENT_ACTION_REQUIRED, inspect error on CONFIGURATION_ERROR/SETUP_FAILED), but the destructive write paths — running actions and proxy POST/PUT/DELETE against employee data — have no validation/verification or confirmation checkpoint, which caps workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	The body has reasonable section headers in a single ~150-line file with no external references and no nested reference chains, but it exceeds the 50-line simple-skill exception and inlines detail (the clientAction state reference, the proxy flags table) that could live in separate files, matching anchor 3.	3 / 5
	Total	13 / 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 correctly pairs a "what" with an explicit "Use when…" trigger and leverages a distinctive named-product trigger, but its capability language ("Manage data, records, and automate workflows") is generic and lacks synonym coverage. Strengthening the action list and trigger synonyms would raise specificity and trigger-term quality.

Suggestions

Replace generic verbs with concrete capabilities, e.g. "Query employee records, submit time-off requests, and run payroll/workflow actions against UKG Pro" to lift specificity.

Add natural trigger synonyms so activation matches more user phrasings, e.g. "Use when the user wants to interact with UKG Pro data — employee records, time off, payroll, HR, or UltiPro."

Tighten the "when" clause to name the concrete objects users mention (employees, time-off, payroll) rather than only "UKG Pro data".

Dimension	Reasoning	Score
Specificity	Names the domain (UKG Pro) and lists a few actions — "Manage data, records, and automate workflows" — but "Manage data, records" is generic rather than concrete, so it sits at the anchor-3 level and does not reach the specific multi-action coverage of anchor 4.	3 / 5
Completeness	Both "what" (UKG Pro integration; manage data, records, automate workflows) and an explicit "Use when the user wants to interact with UKG Pro data" "when" clause are present, so it clears the 3-cap; it is not a 5 because the "what" is generic and only one trigger phrase is given.	4 / 5
Trigger Term Quality	"UKG Pro" is a strong, natural named-product trigger and "interact with UKG Pro data" gives a usable phrase, but common synonyms/variations a user might say (UltiPro, payroll, HR, time off, employee records) are missing, matching anchor 3.	3 / 5
Distinctiveness Conflict Risk	Targeting a specific named product ("UKG Pro") with a product-name trigger gives a clear niche with minimal conflict risk against other skills, matching anchor 5.	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/ukg-pro/SKILL.md
Commit: f484c82

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