persona-hr-coordinator
Handle HR workflows — onboarding, announcements, and employee comms.
61
52%
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, and the listed capabilities are too broad to clearly distinguish this skill from general writing or communication skills.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'new hire onboarding', 'welcome email', 'company announcement', 'internal memo', 'HR communication'.
Replace high-level categories with specific concrete actions, e.g., 'Draft onboarding welcome emails, write company-wide announcements, create new hire checklists, compose policy update notices'.
Include more natural keyword variations users might say, such as 'new employee', 'hiring', 'internal comms', 'team announcement', 'HR email'.
| 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 it does (handle HR workflows) but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2, and the 'what' itself is also fairly weak/vague, placing this at 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', 'internal communications', 'company announcement', 'HR letter', or 'employee handbook'. | 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 description doesn't clearly carve out a unique niche. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a concise, well-structured persona skill that effectively delegates to underlying utility skills and workflows. Its main weakness is the lack of concrete examples (e.g., a sample calendar event creation or email send command with parameters) and the absence of a sequenced onboarding workflow with validation steps. The skill reads more like a reference card than an executable guide.
Suggestions
Add a concrete example of a complete onboarding workflow as a numbered sequence (e.g., Step 1: Create orientation event → Step 2: Upload docs → Step 3: Announce → Step 4: Verify all steps completed).
Include at least one concrete example with actual parameters, e.g., a sample `gws calendar +insert` invocation with typical onboarding event details.
Add a validation/verification step after the onboarding sequence, such as confirming all docs are uploaded and calendar events are created before announcing the new hire.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what HR workflows are or how Google Workspace works — it assumes Claude's competence and every line provides actionable direction. | 3 / 3 |
Actionability | The skill references specific commands/workflows (e.g., `gws calendar +insert`, `gws drive +upload`) which is helpful, but lacks concrete examples of actual invocations with parameters, expected inputs, or outputs. The guidance is directional rather than copy-paste executable. | 2 / 3 |
Workflow Clarity | The instructions list individual actions for onboarding but don't sequence them into a clear step-by-step workflow with validation checkpoints. For a multi-step process like onboarding (create events → upload docs → announce → track tasks), explicit ordering and verification steps are missing. | 2 / 3 |
Progressive Disclosure | The skill appropriately serves as an overview, referencing prerequisite utility skills and specific workflows without inlining their details. References are one level deep and clearly signaled with backtick-formatted skill/workflow names. | 3 / 3 |
Total | 10 / 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
a3768d0
- 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.