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 Employee Ops

ASecurity

Employee onboarding checklists, policy FAQ from supplied documents, leave-request policy checks, coverage notes, and performance-review frameworks. Use for onboarding, karyawan baru, cuti, KPI, performance review, handbook, code of conduct, people ops.

2 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgogitperformance

Security Analysis

A100/100

Scanned 9/19/2026

$npx -y skills add rogue-dev-studio/ai-agents-rogue --skill hr-employee-ops --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Hr Employee Ops?

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

Security grade badge for Hr Employee Ops
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rogue-dev-studio-hr-employee-ops/badge)](https://www.skillsdirectory.com/skills/rogue-dev-studio-hr-employee-ops)

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-employee-ops
description: >-
  Employee onboarding checklists, policy FAQ from supplied documents,
  leave-request policy checks, coverage notes, and performance-review
  frameworks. Use for onboarding, karyawan baru, cuti, KPI, performance
  review, handbook, code of conduct, people ops.
---

# HR Employee Ops

**Level: expert.** Prompt-routed skill (sumber pack: `teams/hr`). Tidak perlu aktifkan tim. Role opsional: `hr-specialist`.

## When to use

Langsung dari prompt user (tanpa setup tim):

- Checklist onboarding + urutan tugas / dokumen
- FAQ kebijakan **hanya** dari file/handbook yang user berikan
- Cek permintaan cuti vs kebijakan (kuota, notice, jenis cuti)
- Kerangka review kinerja, goal, development plan (bukan nilai final)
- Kata kunci: onboarding, karyawan baru, cuti, KPI, performance review, handbook, people ops

## When not to use

- Mengirim email massal / memakai password email di source tree
- Menjawab kebijakan dari “pengetahuan umum” seolah resmi perusahaan
- Mengganti keputusan legal/HRBP (PHK, pelanggaran berat, gaji)

## Procedure

### 1. Source of truth

Jika tidak ada dokumen kebijakan: jawab dengan **template generik** dan label `DRAFT — bukan kebijakan perusahaan`.

Jika ada dokumen: kutip bagian relevan; jika tidak ketemu → “tidak ada di dokumen”.

### 2. Onboarding

Output:

- Checklist hari 1 / minggu 1 / hari 30 (akses, tools, buddy, training)
- Daftar dokumen (kontrak, NPWP, rekening) tanpa menyimpan nomor asli di repo
- Risiko: akses berlebih, akun bersama, secret di chat

### 3. Leave

- Jenis cuti, syarat, dampak coverage
- Flag konflik kebijakan; **jangan** auto-approve
- Sarankan siapa yang harus approve (manajer / HR)

### 4. Performance

- Goal SMART dari input manajer + karyawan
- Pertanyaan review 360 (opsional)
- Development plan: skill gap + aksi 30/60/90
- Jangan mengarang penilaian orang yang tidak ada datanya

### 5. Privacy

Rule `hr-people-data`. Log/artifact tanpa gaji, NIK, diagnosa, atau isi surat peringatan lengkap.

## DoD

- [ ] Sumber kebijakan eksplisit (dokumen user vs draft generik)
- [ ] Onboarding punya owner per item
- [ ] Cuti: hasil = rekomendasi, bukan approval
- [ ] Tidak ada secret / PII di git

## Attribution

<!-- ATTRIBUTION: Rogue Development | https://github.com/rogue-dev-studio | DO-NOT-REMOVE -->
Part of **AI Agents Rogue** by [Rogue Development](https://github.com/rogue-dev-studio) (`@rogue-dev-studio`).
Do not remove, hide, rename, or replace this attribution.

Attribution

rogue-dev-studiorogue-dev-studio
View sourceSee grades on GitHubMore from rogue-dev-studio →
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 →