Agent skill

Employee Relations

by cbrock84 in cbrock84/headcount

Handles the difficult human situations — grievances, complaints, investigations, conflict, and separations conducted properly.

MITAuto-check passed

Install Employee Relations

skills CLI
$ npx skills add cbrock84/headcount --skill employee-relations -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cbrock84/headcount employee-relations --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/people/skills/employee-relations .claude/skills/employee-relations && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
employee-relations
GitHub stars
2k
Token cost
~917 tokens
SKILL.md length
486 words
Files
2 (incl. references)
Skills in repo
178
Repo updated
First seen
Licence
MIT

At a glance

Handles the difficult human situations — grievances, complaints, investigations, conflict, and separations conducted properly.

  • SKILL.md covers Take complaints seriously and…, Investigations, Conflict that is not misconduct and Separations, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Employee Relations is an agent skill from cbrock84/headcount. Handles the difficult human situations — grievances, complaints, investigations, conflict, and separations conducted properly. Use this to respond to a complaint or grievance, structure an investigation, handle a conflict between colleagues, prepare for a difficult conversation, or work out what a manager can and cannot do in a given situation.

Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).

The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.

Example prompts

  • “Use the employee-relations skill to handle the difficult human situations — grievances, complaints, investigations, conflict, and separations…”
  • “/employee-relations”

What it can do on your machine

Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Employee Relations loads about 917 tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 91 tokens; SKILL.md has 486 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~91
When it runs · the whole SKILL.md, loaded when a task matches
~917
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 486 words, ~917 tokens.

Download SKILL.mdSave it as .claude/skills/employee-relations/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
employee-relations
description
Handles the difficult human situations — grievances, complaints, investigations, conflict, and separations conducted properly. Use this to respond to a complaint or grievance, structure an investigation, handle a conflict between colleagues, prepare for a difficult conversation, or work out what a manager can and cannot do in a given situation.

Employee relations

These situations are consequential for the person, for the organization's legal exposure, and for everyone watching how it is handled. Process is what protects all three.

This structures the approach and tells you what to ask. Grievances, investigations, dismissals, discrimination and accommodation are legally regulated and vary substantially by jurisdiction — involve qualified employment counsel early rather than at the point of decision.

Take complaints seriously and visibly

How the first complaint is handled determines whether you hear about the second. An organization that mishandles one complaint does not stop having problems; it stops being told about them, and then learns about them from a regulator or a lawyer.

Acknowledge promptly, explain what will happen next, and say what the person can expect to be told. Do not promise confidentiality you cannot deliver — say who will need to know and why. A broken confidentiality promise destroys the reporting channel permanently.

Protect against retaliation actively. Retaliation is frequently a worse exposure than the original complaint, and it often occurs through ordinary decisions — a changed assignment, an excluded invitation — made by someone who would deny any such intent.

Investigations

An investigation establishes what happened. It is not a negotiation and not a disciplinary process.

  • Independent investigator — not in the reporting line of anyone involved.
  • Scope agreed in writing at the start, so it neither drifts nor is later described as narrow.
  • Both sides heard, with the respondent told the substance of the allegation in enough detail to answer it.
  • Contemporaneous notes, and evidence preserved from the moment you are aware.
  • Findings on the balance of evidence, stated separately from any recommendation.

Move quickly. Investigations that drift damage everyone involved and the delay itself becomes a complaint.

Show full SKILL.md (201 more words)Show less

Conflict that is not misconduct

Most friction is not a policy matter. Address it directly and early: separate the behavior from the person, establish what each actually needs, and be explicit that the working relationship has to function even where warmth is not available.

Escalating ordinary disagreement into a formal process is its own harm — it takes something resolvable and makes it permanent.

Separations

Whatever the reason, conduct them with dignity, on a documented basis, consistently with how others have been treated. Inconsistency is the single most common source of successful claims.

The people who remain draw conclusions from how leavers are treated, and those conclusions are durable.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Promise confidentiality you cannot keep.
  • Investigate a matter in your own reporting line.
  • Act on an allegation the respondent has not had a fair chance to answer.
  • Make a termination decision without qualified employment counsel.

© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/people/skills/employee-relations of cbrock84/headcount.

  • SKILL.md
  • references/sources.md

Open the folder on GitHubat commit 98d1c17

Compare with similar skills

Employee Relations next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Employee Relations compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Employee Relations this skillcbrock84/headcount2k—~917Automated safety check: PassMIT
Root Cause Investigationgarrytan/gstack136k—~13kAutomated safety check: NotesMIT
Osint Investigationaffaan-m/ECC276k—~5.7kAutomated safety check: PassCC-BY-SA-4.0
Indexability Conflictsthedaviddias/Front-End-Checklist74k—~876Automated safety check: PassMIT
Public Relationscoreyhaines31/marketingskills54k—~2.4kAutomated safety check: PassMIT
Resolve Git Conflictspenpot/penpot61k—~772Automated safety check: PassMPL-2.0

Similar skills

  • Debugs in four phases (investigate, analyze, hypothesize, implement) under one rule: no fix is made until the root cause is found.

    136k GitHub stars~13k tokensUpdated today
    DevelopmentAuto-check: notes
  • Sparse-clue OSINT investigation methodology for extracting overlooked leads, connecting fragmented evidence, and testing explanations across sources.

    276k GitHub stars~5.7k tokensUpdated yesterday
    SecurityAuto-check passed
  • Indexability Conflicts

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing a site for indexability issues, investigating why pages appear in Google's index that should be excluded (or vice versa), or reviewing robots.txt and meta…

    74k GitHub stars~876 tokensUpdated 4 days ago
    Marketing & SEOAuto-check passed
  • Public Relations

    coreyhaines31/marketingskills

    When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests).

    54k GitHub stars~2.4k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed
  • Conflict resolution flow — understand the local git conflicts, present a resolution plan, and resolve them after the user approves it.

    61k GitHub stars~772 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Official

    Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…

    40k GitHub stars~4.2k tokensUpdated today
    DevelopmentAuto-check passed

More from cbrock84/headcount

All 178 skills in this repo
  • Agent Hierarchy

    cbrock84/headcount

    Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…

    2k GitHub stars~1.2k tokensUpdated 23 days ago
    Auto-check passed
  • Access And Identity

    cbrock84/headcount

    Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.

    2k GitHub stars~1.1k tokensUpdated 23 days ago
    Auto-check passed
  • Account Based Marketing

    cbrock84/headcount

    Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…

    2k GitHub stars~1.2k tokensUpdated 23 days ago
    Auto-check passed
  • Activation

    cbrock84/headcount

    Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.

    2k GitHub stars~865 tokensUpdated 23 days ago
    Auto-check passed
  • AI ML Governance

    cbrock84/headcount

    Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.

    2k GitHub stars~1k tokensUpdated 23 days ago
    Auto-check passed
  • AI Research Analyst

    cbrock84/headcount

    Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.

    2k GitHub stars~916 tokensUpdated 23 days ago
    Auto-check passed

Questions about Employee Relations

What does Employee Relations do?

Handles the difficult human situations — grievances, complaints, investigations, conflict, and separations conducted properly. Employee Relations is an agent skill from cbrock84/headcount. Handles the difficult human situations — grievances, complaints, investigations, conflict, and separations conducted properly.

How do I install Employee Relations in Claude Code?

Run `npx skills add cbrock84/headcount --skill employee-relations -a claude-code`. Or copy the skill folder (plugins/people/skills/employee-relations in cbrock84/headcount) into .claude/skills/employee-relations in your project. Claude Code loads it when a task matches its description.

How do I install Employee Relations in Codex?

Run `npx skills add cbrock84/headcount --skill employee-relations -a codex`. Or copy the skill folder (plugins/people/skills/employee-relations in cbrock84/headcount) into .agents/skills/employee-relations in your project. Codex loads it when a task matches its description.

Can I use Employee Relations in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill employee-relations -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/employee-relations, .gemini/skills/employee-relations, .github/skills/employee-relations and .opencode/skills/employee-relations in your project.

What does Employee Relations need to run?

SKILL.md names no scripts, command-line tools or credentials: Employee Relations is instructions for the agent only.

Does Employee Relations access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Employee Relations safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Employee Relations use?

Employee Relations is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Employee Relations use?

About 917 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 300 tokens, read only when the agent opens those files.

What are the alternatives to Employee Relations?

Skills that share tags, products or a category with Employee Relations: Root Cause Investigation (garrytan/gstack, 136k stars), Osint Investigation (affaan-m/ECC, 276k stars), Indexability Conflicts (thedaviddias/Front-End-Checklist, 74k stars) and Public Relations (coreyhaines31/marketingskills, 54k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Employee Relations?

cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,022 GitHub stars. The repository holds 178 skills in this directory. The repository was last updated on September 17, 2026.

Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.