persona-hr-coordinator
Handle HR workflows — onboarding, announcements, and employee comms.
56
46%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/persona-hr-coordinator/SKILL.mdQuality
Discovery
32%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 identifies the HR domain and lists a few sub-areas but remains at a high level without concrete actions or explicit trigger guidance. It lacks a 'Use when...' clause, which significantly hurts completeness. The trigger terms are reasonable but incomplete, missing many natural phrases users would employ when requesting HR-related help.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'new hire onboarding', 'welcome email', 'internal announcement', 'employee newsletter', 'HR communication'.
Replace high-level categories with specific concrete actions, e.g., 'Draft onboarding checklists, write new hire welcome emails, compose company-wide announcements, create policy update notices'.
Include more natural keyword variations users might say, such as 'new employee', 'team announcement', 'HR email', 'internal memo', 'offboarding', 'employee handbook'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (HR workflows) and lists some actions (onboarding, announcements, employee comms), but these are still fairly high-level categories rather than concrete specific actions like 'draft offer letters' or 'create onboarding checklists'. | 2 / 3 |
Completeness | Describes what the skill does (handle HR workflows) but has no explicit 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' portion is also fairly weak, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'onboarding', 'announcements', and 'employee comms', but misses many natural variations users might say such as 'new hire', 'welcome email', 'policy update', 'internal memo', 'offboarding', 'employee handbook', etc. | 2 / 3 |
Distinctiveness Conflict Risk | The HR domain provides some distinctiveness, but 'announcements' and 'employee comms' are broad enough to overlap with general writing/communication skills. The lack of specific file types, tools, or precise use cases increases conflict risk. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
60%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is concise and well-organized as a high-level orchestration guide, with clear references to underlying utility skills. However, it lacks concrete examples of command invocations and, critically, does not sequence the multi-step onboarding workflow with explicit ordering or validation checkpoints, which is important for a process involving multiple systems and PII-sensitive operations.
Suggestions
Add a numbered, sequenced onboarding workflow (e.g., 1. Upload docs → 2. Create calendar events → 3. Announce in Chat) with explicit validation steps between stages.
Include at least one concrete example invocation with parameters for a key command like `gws calendar +insert` or `gws gmail +send` to make guidance copy-paste actionable.
Add a verification/validation step after bulk operations (e.g., confirm email delivery, verify file upload) to ensure error recovery in multi-step HR processes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows what HR workflows are and doesn't explain basic concepts. Every line provides actionable direction without padding. | 3 / 3 |
Actionability | The skill references specific commands and workflows (e.g., `gws calendar +insert`, `gws drive +upload`) but provides no concrete examples of actual invocations, parameters, or expected outputs. It describes what to do at a high level but lacks copy-paste ready commands or example payloads. | 2 / 3 |
Workflow Clarity | While individual steps are mentioned, there is no clear sequenced workflow for onboarding or other multi-step processes. Steps are listed as independent bullet points without ordering, dependencies, or validation checkpoints. For an onboarding workflow involving multiple systems, the lack of sequencing and verification steps is a significant gap. | 1 / 3 |
Progressive Disclosure | The skill is appropriately structured as a concise overview that delegates to prerequisite utility skills and named workflows. References are one level deep and clearly signaled with backtick-formatted skill/workflow names. | 3 / 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 |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- googleworkspace/cli
- Commit
c7c6646
- Reviewed
Table of Contents
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.