Name: workday
Rating: 62.4 (1 reviews)
Author: membranedev

workday

Workday integration. Manage Organizations, Deals, Leads, Projects, Pipelines, Goals and more. Use when the user wants to interact with Workday data.

Quality

74%

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/workday/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.

A highly actionable, well-structured integration guide with strong executable commands and a clear connection workflow. The main drag is conciseness (marketing-style padding and a restated product definition) plus a couple of minor workflow/organization gaps.

Suggestions

Trim editorial padding ("so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection") and the restated definition of what Workday is, since Claude already knows the product.

Replace the undefined "Step 2" references with explicitly numbered workflow steps (1. Install, 2. Authenticate, 3. Ensure connection, 4. Search/run actions) so the sequence is self-contained.

Add a brief verification cue after running an action (e.g., check the `output` field and handle non-READY/error states) to close the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but it includes unnecessary padding Claude does not need ("so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection", and a restated definition of what Workday is), matching the mostly-efficient-but-could-be-tightened anchor rather than the lean/efficient one.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) with real flags and JSON output, plus a concrete popular-actions table covering the common cases, fitting the fully-executable anchor.	5 / 5
Workflow Clarity	The connection lifecycle is a clear sequenced flow with explicit state checkpoints and a feedback loop (poll BUILDING, handle CLIENT_ACTION_REQUIRED, re-poll until READY, inspect error on CONFIGURATION_ERROR); it falls short of 5 because the doc references a "Step 2" that is never defined as a numbered step and the action-running section lacks result verification.	4 / 5
Progressive Disclosure	No bundle files are provided, so the single SKILL.md carries everything; it is well-organized into clearly headed sections with no nested references, though the 14-row popular-actions table is reference-style material inlined into the overview, which is a minor organization gap keeping it off the top anchor.	4 / 5
	Total	16 / 20 Passed

Description

73%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.

A solid, third-person description with an explicit trigger clause and a distinct Workday niche. Its main weakness is the generic "Manage" verb and "and more" hedge, which keep capability specificity from the top anchor.

Suggestions

Replace the generic "Manage" with 2-3 concrete verbs (e.g., "query, create, and update Workers, Organizations, and Deals") to lift specificity.

Drop or quantify "and more" so coverage reads as comprehensive rather than open-ended.

Sharpen the "when" clause with concrete scenarios (e.g., "Use when the user wants to look up a worker, list organizations, or pull a Workday report").

Dimension	Reasoning	Score
Specificity	Names the Workday domain and lists concrete entities ("Organizations, Deals, Leads, Projects, Pipelines, Goals"), but the governing verb is the generic "Manage" and the trailing "and more" signals non-comprehensive coverage, so it sits at the domain-plus-actions-but-not-comprehensive anchor rather than the several-specific-actions anchor.	3 / 5
Completeness	It states a clear "what" (Workday integration managing the listed entities) and an explicit "when" ("Use when the user wants to interact with Workday data"), satisfying both halves; the "when" is present but could be more scenario-specific, matching the both-present-but-when-could-be-sharper anchor rather than the fully concrete trigger-phrases anchor.	4 / 5
Trigger Term Quality	"Workday" plus the enumerated entity names (Organizations, Deals, Leads, Projects, Pipelines, Goals) give good natural keyword coverage a user would say; it stops short of a 5 because no synonyms or scenario phrasings beyond "interact with Workday data" are included.	4 / 5
Distinctiveness Conflict Risk	"Workday integration" is a clear, product-specific niche with distinct triggers ("Workday", the named entities) and minimal realistic overlap with other skills, fitting the clear-niche-minimal-conflict anchor.	5 / 5
	Total	16 / 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/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.