ADP Workforce Now integration. Manage Persons, Organizations, Jobs, Payrolls, Benefitses, Talents. Use when the user wants to interact with ADP Workforce Now data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill adp-workforce75
Quality
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/adp-workforce/SKILL.mdDiscovery
75%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 effectively identifies a specific integration (ADP Workforce Now) and includes an explicit 'Use when' clause, making it complete and distinctive. However, it lacks specificity in the actions beyond 'Manage' and could benefit from more natural trigger terms users might say. Note: 'Benefitses' appears to be a typo for 'Benefits'.
Suggestions
Replace vague 'Manage' with specific actions like 'Create, update, query, and delete' to improve specificity
Add common trigger term variations such as 'ADP', 'HR system', 'employee records', 'payroll processing', 'workforce management'
Fix typo 'Benefitses' to 'Benefits'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (ADP Workforce Now) and lists entity types (Persons, Organizations, Jobs, Payrolls, Benefitses, Talents), but 'Manage' is vague and doesn't specify concrete actions like 'create', 'update', 'query', or 'delete'. | 2 / 3 |
Completeness | Clearly answers both what (manage various ADP entities) and when ('Use when the user wants to interact with ADP Workforce Now data') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'ADP Workforce Now' which users would say, and entity names like 'Payrolls' and 'Jobs'. However, missing common variations like 'ADP', 'workforce management', 'HR system', 'employee data', or 'payroll processing'. | 2 / 3 |
Distinctiveness Conflict Risk | ADP Workforce Now is a specific product name that creates a clear niche. The explicit mention of this platform makes it highly unlikely to conflict with other HR or payroll skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable CLI commands for ADP Workforce Now integration with good documentation of flags and options. However, it includes unnecessary introductory content about what ADP is, lacks validation/error handling guidance in workflows, and the popular actions table could be better organized or externalized.
Suggestions
Remove the introductory paragraph explaining what ADP Workforce Now is - Claude already knows this
Add validation steps after connection creation (e.g., 'Verify connection: membrane connection list --json | grep CONNECTION_ID')
Include error handling guidance for common failure scenarios (auth failures, invalid connection IDs)
Consider moving the popular actions table to a separate ACTIONS.md file and referencing it
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'ADP Workforce Now is a human capital management (HCM) platform that helps businesses manage their employees...') that Claude already knows. The overview section listing features without actionable content adds little value. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, including installation, authentication, connection setup, action discovery, and proxy requests. Commands are copy-paste ready with proper flags and options documented. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack explicit validation checkpoints. No feedback loops for error recovery (e.g., what to do if connection fails, how to verify a connection succeeded before proceeding). | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with sections, but the popular actions table is quite long and could be referenced externally. The overview section with bullet points adds little value and could be removed or condensed. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Table of Contents
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.