How to use the HR Coordinator agent skill

What an agent skill is and what this one does

An agent skill is a folder of instructions that an AI agent loads so it knows how to handle a particular kind of task. This skill is a persona: it tells the agent to act as an HR coordinator for onboarding, announcements and employee communications.

Once installed, the agent can create orientation sessions in Google Calendar, upload onboarding documents to a shared Drive folder, announce new hires in Google Chat spaces, turn emailed requests into tracked tasks, and send bulk announcements through Gmail.

• Schedule new-hire orientation events with gws calendar +insert
• Upload onboarding documents to a shared Drive folder with gws drive +upload
• Announce new hires in Chat spaces with gws workflow +file-announce to share their profile doc
• Convert email requests into tracked tasks with gws workflow +email-to-task
• Send bulk announcements with gws gmail +send

What you need before you install

The skill does not do the work itself. It calls the gws command-line tool (Google Workspace CLI), so gws must already be installed and authenticated on your machine. You also need a Google Workspace account with access to Gmail, Calendar, Drive and Chat.

The skill depends on four utility skills: gws-gmail, gws-calendar, gws-drive and gws-chat. Its instructions tell the agent to load these to operate as the persona.

• gws command-line tool installed and authenticated
• Google Workspace account with access to Gmail, Calendar, Drive and Chat
• Utility skills gws-gmail, gws-calendar, gws-drive and gws-chat

Install the HR Coordinator skill

Download the ZIP file for persona-hr-coordinator from our page. The package contains a single file, SKILL.md.

For a personal install, unzip the package into ~/.claude/skills/. To make the skill available only inside one project, unzip it into that project's .claude/skills/ folder instead.

If you use the Claude apps, you can upload the ZIP instead. Go to Settings, then Capabilities, then Skills, and upload the file there.

• Personal install: ~/.claude/skills/
• Project install: .claude/skills/ inside your project
• Claude apps: Settings → Capabilities → Skills

Ask for HR tasks in plain language

You do not need special syntax. Describe the outcome you want, and the agent should use the persona when the request involves onboarding, announcements or employee comms. Name the people, dates, folder or channel so the agent has what it needs.

Good requests name the object and the action, for example asking the agent to add an orientation session for a new starter on a given date, or to share the onboarding pack with a named Drive folder. Vague requests such as 'do HR stuff' give the agent less to work with.

• Example: Schedule orientation for Priya on Monday at 9am in the HR Onboarding calendar.
• Example: Upload the onboarding pack to the New Starters Drive folder.
• Example: Turn the email from Sam about the payroll form into a task.
• Example: Draft and send a bulk announcement about next week's new starters with a clear subject line.

Safety, permissions and what to review

The skill runs scripts and uses the network, because it works by calling gws. Its real behaviour depends on the gws tool and on the permissions granted to it. The skill file itself contains instructions and command names, not the implementation.

The skill sends emails, posts to Chat and uploads files, so a mistake can reach many people. The source's own tip is to use --sanitize for PII-sensitive operations. Check drafts before any bulk send, and do not rely on this skill for sensitive employee records without human review.

• Review every bulk email draft before it is sent
• Use --sanitize for PII-sensitive operations
• Test with a small group or a test Chat space first
• Confirm the gws account has only the access it needs

Tips for reliable use

Create a dedicated 'HR Onboarding' calendar so orientation schedules are easy to track and separate from other events.

Use clear subject lines on announcements, since bulk emails are hard to recall once sent.

• Keep onboarding documents in one shared Drive folder so the agent always uploads to the same place
• Give the agent names, dates and channel names rather than descriptions
• Read the agent's summary of what it did before moving to the next task