persona-hr-coordinator
Handle HR workflows — onboarding, announcements, and employee comms.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill persona-hr-coordinator59
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 broad capability areas but lacks the specificity and explicit trigger guidance needed for reliable skill selection. The absence of a 'Use when...' clause is a significant gap, and the listed capabilities are categories rather than concrete actions.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions HR, human resources, new hire onboarding, employee announcements, or internal communications'.
Replace high-level categories with specific concrete actions such as 'draft offer letters, create onboarding checklists, write company-wide announcements, compose welcome emails'.
Include common keyword variations users might say: 'human resources', 'new hire', 'internal memo', 'team announcement', 'employee handbook'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the HR domain and lists some actions (onboarding, announcements, employee comms), but these are high-level categories rather than concrete specific actions like 'draft offer letters' or 'create onboarding checklists'. | 2 / 3 |
Completeness | Describes what the skill does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'HR', 'onboarding', 'announcements', and 'employee comms' that users might say, but missing common variations like 'human resources', 'new hire', 'internal communications', 'welcome email', or 'company memo'. | 2 / 3 |
Distinctiveness Conflict Risk | 'HR workflows' provides some domain specificity, but 'announcements' and 'employee comms' could overlap with general writing or communication skills without clearer boundaries. | 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 skill is concise and well-organized, effectively pointing to relevant tools and workflows without over-explaining. However, it lacks concrete examples showing actual command usage with parameters, and the onboarding workflow would benefit from explicit sequencing and validation steps to guide Claude through the multi-step process.
Suggestions
Add a concrete example showing a complete onboarding workflow sequence (e.g., 1. Create calendar event → 2. Upload docs → 3. Announce in Chat) with actual command parameters
Include at least one executable example with sample parameters for a common operation like `gws calendar +insert --title 'New Hire Orientation' --attendees ...`
Add validation checkpoints for the onboarding workflow (e.g., verify calendar event created before proceeding to document upload)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, with no unnecessary explanations. It assumes Claude knows what HR workflows, onboarding, and the referenced tools are, and every line provides actionable guidance. | 3 / 3 |
Actionability | Provides specific tool references and commands (e.g., `gws calendar +insert`, `gws drive +upload`) but lacks concrete examples of actual usage, parameters, or expected outputs. The guidance is directive but not copy-paste ready. | 2 / 3 |
Workflow Clarity | Lists relevant actions for HR workflows but doesn't provide a clear sequence or validation checkpoints. For onboarding (a multi-step process), there's no explicit ordering or verification steps between actions. | 2 / 3 |
Progressive Disclosure | Appropriately structured with clear sections. References to prerequisite skills and workflows are one level deep and clearly signaled. The content is well-organized for a skill of this size. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- 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.