Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Hr Case Log

ASecurity

Sets up an employee relations case log with stage, owner, next date and documents per case, the rules for what to record and what not to, and a monthly aggregate count for reporting. Use for "run hr-case-log", "employee relations case log", "ER case tracker", "how do I keep notes on HR cases", "what should I write down about a complaint", "track open grievances", "case management log for HR", part of the AI for HR Pack by Polar Bear.

2 stars
0 votes
0 copies
0 views
Added 10/4/2026
ai-agentsgo

Works with

cli

Security Analysis

A100/100

Scanned 10/4/2026

$npx -y skills add polar-bear-org/claude-skills --skill hr-case-log --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Hr Case Log?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Hr Case Log
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/polar-bear-org-hr-case-log/badge)](https://www.skillsdirectory.com/skills/polar-bear-org-hr-case-log)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: hr-case-log
description: Sets up an employee relations case log with stage, owner, next date and documents per case, the rules for what to record and what not to, and a monthly aggregate count for reporting. Use for "run hr-case-log", "employee relations case log", "ER case tracker", "how do I keep notes on HR cases", "what should I write down about a complaint", "track open grievances", "case management log for HR", part of the AI for HR Pack by Polar Bear.
---

# Employee Relations Case Log

## When To Use
You are pulled into an investigation or a claim and cannot find what was said, when. The notes are in three inboxes and a notebook, and nobody wrote down who made the call. This answers: where is every open case, who owns the next step, and will our records hold up when someone reads them.

## When Not To Use
For a one-off review of all your files and policies, use HR Audit. For leadership reporting, send the monthly count from this log to HR Dashboard rather than sharing the log.

## Inputs
- Where your people work (country, and state or province where it matters)
- Your open and recent cases, in any form (a list, a spreadsheet, notes)
- The case types you handle (for example grievance, conduct, absence, accommodation)
If you have none of this, I start from your case types and an empty log and mark the output as a first draft.

## Approach
The log follows the ICO employment practices guidance on keeping employment records (ico.org.uk). Records should be accurate, kept only as long as needed, and written knowing the employee can ask to see them. The failure it prevents: a note that says "clearly a troublemaker", written in a hurry and read out later by the person it describes.

## Workflow
1. Ask three questions: where do your people work; what case types do you handle; what minimum group size you want before a count is shown in reporting (you set it; I do not build the count until you do).
2. Set one row per case: a case reference, never a name; type; date opened; stage; owner by role; next action and its date; documents and where they are held; date closed.
3. Write the recording rules. Record at the time: dates, what was said and by whom, actions taken, decisions and who made them. Do not record: opinions about people, guesses, health details beyond what the case needs; health information is held separately.
4. Set the accuracy rule: every entry dated and attributed; corrections added as new dated entries, never overwritten.
5. Set retention per case type with your adviser. The ICO says retention follows legal requirement and business need, so I leave the period as a blank for you and your adviser to fill.
6. Build the monthly count by type and stage only. Any cell below your minimum shows "fewer than [n], not shown".

## Output Format
```markdown
# Employee Relations Case Log
## Open cases
| Case ref | Type | Opened | Stage | Owner (role) | Next action | Next date | Documents held at | Closed |
|---|---|---|---|---|---|---|---|---|
| [ER-001] | [grievance] | [date] | [intake / investigation / hearing / appeal / closed] | [role] | [action] | [date] | [location] | [date] |
## Recording rules
- Record: [dates, who said what, actions, decisions and who made them]
- Do not record: [opinions about people, guesses, health details beyond need]
## Retention
| Case type | Retention period | Confirmed by adviser on |
|---|---|---|
| [type] | [set with adviser] | [blank until confirmed] |
## Monthly count
| Type | Opened | Closed | Open at month end |
|---|---|---|---|
| [type] | [n or "fewer than [n], not shown"] | [n] | [n] |
## Decision
[Named HR owner] adopts the log and the recording rules by [date] and sets the date of the first monthly count.
```

## Done When
- Every case has a reference, an owner by role and a next date
- There are no names in the monthly count and no opinion fields anywhere
- Retention periods are blank or marked as confirmed by an adviser
- Small cells are suppressed at the minimum you set

## Quality Bar
- Every entry is written as if the person it describes will read it, because they may
- Decisions are recorded with who made them; Claude never records a decision it was not told
- Corrections sit beside the original entry, dated
- Health information lives in a separate record, referenced, not copied
- Claude writes the process, never the verdict: a named person decides, and every legal point goes to a qualified adviser for the country it concerns.

## Next
Run hr-dashboard (HR Dashboard) to report the monthly count to leaders.

## About the makers

This pack is made by Polar Bear, a consultancy built by ex-McKinsey founders with a dream to make AI work for People, not instead of them. We help our clients build people systems and AI-first ways of working, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).

Attribution

polar-bear-orgpolar-bear-org
View sourceSee grades on GitHubMore from polar-bear-org →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →