Name: workday-soap
Rating: 51.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

workday-soap

Workday SOAP integration. Manage Organizations. Use when the user wants to interact with Workday SOAP data.

Quality

56%

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

Quality

Content

53%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 Membrane CLI commands and a clear connection workflow, but it is weighed down by a padded 70-item domain list and explanatory filler Claude already knows, with no progressive disclosure into reference files.

Suggestions

Cut the 70-item Workday domain bullet list and the 'Think of it as an enterprise-level HR and finance platform' explanation; keep only domains the skill actually exposes as actions.

Move the Popular actions table and verbose client-action state handling into a separate reference file linked from a concise overview.

Add an explicit validate/verify step (e.g. checking the action run output schema or confirming state=READY) before treating results as final.

Dimension	Reasoning	Score
Conciseness	The 70-item Workday domain bullet list and concepts Claude already knows (e.g. 'Workday SOAP is a cloud-based HCM system... Think of it as an enterprise-level HR and finance platform') are padded and consume tokens without adding actionable guidance.	2 / 5
Actionability	It provides copy-paste-ready CLI commands for install, login, connection ensure, action list/run, and proxy requests with concrete flags and JSON examples, with only minor gaps (no example of parsing the output or passing a real input payload).	4 / 5
Workflow Clarity	The connection lifecycle is clearly sequenced (ensure -> wait for READY -> CLIENT_ACTION_REQUIRED handling -> search actions -> run) with polling checkpoints, though validation of results before acting on output is only implicit.	4 / 5
Progressive Disclosure	No bundle files are provided and the document is a single monolithic SKILL.md; the long domain bullet list and Popular actions table would be better moved to reference files rather than inlined.	3 / 5
	Total	13 / 20 Passed

Description

60%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 specific to the Workday SOAP niche and includes an explicit 'Use when' clause, but the 'what' is thin (only 'Manage Organizations') and trigger-term coverage omits common Workday synonyms like HR, HCM, payroll, and workers.

Suggestions

Expand the 'what' beyond 'Manage Organizations' to name the concrete capabilities the skill exposes (e.g. query workers, organizations, compensation, time-off balances).

Add natural trigger synonyms users say, such as HR, HCM, payroll, or time off, so the skill matches a wider range of phrasings.

Keep the explicit 'Use when' clause but make the trigger phrase more concrete than 'interact with Workday SOAP data'.

Dimension	Reasoning	Score
Specificity	It names the domain (Workday SOAP) and one concrete action (Manage Organizations), but the action set is minimal and generic given how broad Workday SOAP is.	3 / 5
Completeness	It states the 'what' (Workday SOAP integration, manage Organizations) and an explicit 'when' ('Use when the user wants to interact with Workday SOAP data'), so both halves are present, though the trigger is somewhat generic.	4 / 5
Trigger Term Quality	It uses the natural term 'Workday SOAP' and 'Organizations', but lacks common synonyms a user might say such as 'HR', 'HCM', 'payroll', or 'workers', leaving keyword coverage partial.	3 / 5
Distinctiveness Conflict Risk	'Workday SOAP' is a specific niche unlikely to collide with unrelated skills; only minor overlap risk with a generic Workday REST skill.	4 / 5
	Total	14 / 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/workday-soap/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.