hr-root-router-maintaining
Skill58 starsChanged 2 months agoMITView on GitHub
Maintenance guide for the root SKILL.md router in the hr-skills monorepo. Use this skill when adding a new HR skill package, removing a deprecated skill, renaming a skill directory, moving a skill between routing sections, or auditing the router for consistency with the actual skills/ directory.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- biomeSkill
- bunSkill
- changesetSkill
- clackSkill
- dry-refactoringSkill
- github-awesome-copilot-git-commitSkill
- hr-skills-maintainingSkill
- humanizerSkill
- jscpdSkill
- markdownSkill
- pdfSkill
- skill-vetterSkill
- turboSkill
- typescriptSkill
- valibotSkill
- hr-skillsSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Add a new skill entry to the correct routing section
- Distinctive: line 18
Remove a deprecated skill from the routing table
- Very specific: line 22
Update the frontmatter description field when new domains are added
- Very specific: line 104
Follow these rules exactly when editing the root SKILL.md.
- Distinctive: line 140
Use this table to decide which section a new skill belongs in:
- Distinctive: line 159
Always read the existing router table before inserting a new row — confirm the skill does not already exist under a different name before …
- Very specific: line 160
When unsure which section fits, read the new skill's description field and match its primary verb (recruiting vs managing vs analyzing vs …
- Very specific: line 161
After any edit, do a quick count: the number of | [hr- links in the router should equal the number of directories under skills/ that …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
HR root router maintenance
The root SKILL.md at the repository root is the entry point for the entire HR Skills library. It does not contain HR knowledge — its only job is to route requests to the right specialized skill package under skills/.
This skill tells AI assistants exactly how to update that router whenever the library changes.
Supported tasks
- Add a new skill entry to the correct routing section
- Remove a deprecated skill from the routing table
- Rename a skill entry when its directory is renamed
- Move a skill entry between routing sections
- Audit router for skills missing from the table or directories missing from
skills/ - Update the frontmatter
descriptionfield when new domains are added - Suggest which routing section a new skill belongs in
- Generate a complete, ready-to-paste router table row
- Validate that all
skills/<n>/SKILL.mdpaths resolve correctly
Router structure
The root SKILL.md has this layout — every edit must preserve it exactly:
frontmatter (---...---)
name: hr-skills
description: "..." ← update when adding an entirely new domain
metadata:
author: Tuan Duc Tran
version: "1.0.0" ← bump patch version on every router change
# HR Skills ← H1, never change
intro paragraph ← never change
## How to use this skill ← never change
numbered rules 1-5 ← never change
## Routing tables ← H2, never change
### <Section name> ← H3 section headers (see canonical list below)
| Skill | Use when... | ← routing table rows
...
## Notes ← H2, never changeCanonical routing sections
These are the current H3 section headers in order. New skills go into an existing section whenever possible. Only add a new H3 section when no existing one fits.
### Talent acquisition & recruiting### Onboarding, offboarding & people operations### Performance, talent & career management### Compensation, benefits & rewards### Learning & development### Organizational development, design & change### Workforce planning & analytics### HR technology, data & AI### Compliance, labor relations & risk### Culture, engagement, experience & wellbeing### Project management & global/local context### Software-engineering & technical hiring specialists
Section 12 has a two-column format | Skill | Discipline | instead of | Skill | Use when the task involves... | — use the discipline column for tech-specialist skills.
Key prompts
Adding a new skill
- "Add [hr-new-skill] to the root SKILL.md router. The skill covers [description of scope]. Suggest the right section and generate the table row."
- "I just created skills/hr-[name]/SKILL.md. Update the router to include it. Here is the skill's description field: [paste description]."
- "Generate a router table row for a new skill called hr-[name] that handles [scope]. Include the markdown link in the correct format."
Removing or renaming a skill
- "Remove hr-[old-name] from the root SKILL.md router. The skill directory has been deleted."
- "Rename hr-[old-name] to hr-[new-name] in the router. Update the link and keep everything else the same."
- "hr-[name] has been merged into hr-[other-name]. Remove the old entry and update the surviving skill's 'Use when' description to cover both scopes."
Moving a skill between sections
- "Move hr-[name] from '### [current section]' to '### [target section]' in the router."
- "hr-[name] fits better under [section] than its current section. Relocate it and keep the row content unchanged."
Auditing the router
- "Audit the root SKILL.md against the actual skills/ directory and list any mismatches: skills in the directory not in the router, or router entries pointing to non-existent directories."
- "Check every markdown link in the routing tables and confirm the target path exists under skills/."
- "List all skills currently in the router by section."
Updating scope
- "The router description field doesn't mention [new domain]. Update it to include [domain] without making the description longer than it currently is."
- "Add a note to the ## Notes section explaining [new convention]."
Editing rules
Follow these rules exactly when editing the root SKILL.md.
Table row format — always use this exact format, no variation:
| [hr-skill-name](skills/hr-skill-name) | One-line description of when to use this skill |- The link text is the skill slug only, no spaces, no decoration.
- The link target is
skills/hr-skill-name— a relative path, no leading slash, no.md. - The "Use when" column starts with a noun phrase or verb phrase describing the task, not "Use when the task involves" — that prefix lives in the column header only.
Section 12 row format (tech-specialist skills):
| [hr-skill-name](skills/hr-skill-name) | Short discipline label (e.g. "Backend engineering, APIs, databases") |Version bump — every time the router changes, increment the patch version in frontmatter:
version: "1.0.0" → version: "1.0.1"Placement within a section — insert new rows alphabetically by skill slug within the section, unless there is a logical grouping reason to place it elsewhere (e.g. keep closely related skills adjacent).
Never touch:
- The
## How to use this skillblock - The
## Notesblock (unless explicitly asked) - The H1
# HR Skillstitle - The intro paragraph under H1
- Existing rows unless they are the target of the edit
Section assignment guide
Use this table to decide which section a new skill belongs in:
| If the skill covers... | Put it in... |
| Finding, attracting, assessing, or hiring candidates | Talent acquisition & recruiting |
| Starting or ending employment, HR ops, admin | Onboarding, offboarding & people operations |
| Performance, growth, career paths, coaching | Performance, talent & career management |
| Pay, benefits, rewards, job levels | Compensation, benefits & rewards |
| Training, skills, learning programs | Learning & development |
| Org structure, culture change, OD | Organizational development, design & change |
| Headcount forecasting, HR data, workforce models | Workforce planning & analytics |
| HR systems, AI tools, automation, data | HR technology, data & AI |
| Legal, compliance, labor law, risk | Compliance, labor relations & risk |
| Employee experience, culture, DEI, wellbeing | Culture, engagement, experience & wellbeing |
| Cross-functional projects, global/Vietnam context | Project management & global/local context |
| Hiring for a specific technical discipline | Software-engineering & technical hiring specialists |
Tips
- Always read the existing router table before inserting a new row — confirm the skill does not already exist under a different name before adding a duplicate.
- When unsure which section fits, read the new skill's
descriptionfield and match its primary verb (recruiting vs managing vs analyzing vs designing) to the section guide above. - After any edit, do a quick count: the number of
| [hr-links in the router should equal the number of directories underskills/that contain aSKILL.md. - The router description field is a single long string — when updating it, preserve the existing domains and append; never replace the whole string.
- Tech-specialist skills (section 12) are meant to be loaded alongside a functional skill (hr-recruiting, hr-job-description, hr-interviewing), not instead of one — if the new skill is a standalone functional skill mistakenly placed in section 12, move it to the correct section.
- Bump the patch version on every router edit so contributors can track the change history without diffing the full file.
Common mistakes
- Adding a new skill row but forgetting to bump
versionin frontmatter. - Using an absolute path
skills/hr-name/SKILL.mdinstead of the relative pathskills/hr-namein the link target — the router links point to directories, not files. - Inserting the row into the wrong table column order (link column must come first, "Use when" second).
- Duplicating an existing entry under a different section without removing the original.
- Adding a new H3 section when the skill clearly fits an existing section — check all 12 sections before creating a new one.
- Editing the
## How to use this skillblock when only a routing table change was needed. - Forgetting to update the
descriptionfrontmatter field when an entirely new domain (not covered by any existing skill) is added.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

