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 Cv Lifecycle

ASecurity

Write, rewrite, and review CVs/résumés; screen candidates against a job description; summarize interview notes; generate interview questions. Use for CV, résumé, screening, ATS, talent, recruiter, kandidat, lamaran.

2 stars
0 votes
0 copies
3 views
Added 9/19/2026
ai-agentsgitapi

Works with

api

Security Analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned 9/19/2026

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

Installs into .claude/skills of the current project.

Are you the author of Hr Cv Lifecycle?

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

Security grade badge for Hr Cv Lifecycle
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rogue-dev-studio-hr-cv-lifecycle/badge)](https://www.skillsdirectory.com/skills/rogue-dev-studio-hr-cv-lifecycle)

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-cv-lifecycle
description: >-
  Write, rewrite, and review CVs/résumés; screen candidates against a job
  description; summarize interview notes; generate interview questions.
  Use for CV, résumé, screening, ATS, talent, recruiter, kandidat, lamaran.
---

# HR CV Lifecycle

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

## When to use

Langsung dari prompt user (tanpa setup tim):

- User minta **buat / perbaiki CV** (diri sendiri atau dari bahan yang diberi)
- **Review CV** vs job description / role
- Ringkas catatan wawancara atau bullet kandidat
- Buat pertanyaan wawancara dari JD + profil
- Kata kunci: CV, résumé, screening, ATS, talent, recruiter, kandidat, lamaran

## When not to use

- Background check ilegal, doxxing, atau scraping data orang tanpa izin
- Memalsukan riwayat kerja, gelar, atau sertifikat
- Keputusan hiring otomatis tanpa reviewer manusia (skor AI = bantuan, bukan vonis)

## Procedure

### 1. Ingest

Kumpulkan: target role/JD, bahan mentah (CV lama, catatan, LinkedIn text), locale (ID/EN), panjang target.

Jika JD tidak ada: tulis **asumsi role** 3–5 bullet, lanjut.

### 2. Privacy gate

Ikuti rule `hr-people-data`. Jangan tulis NIK, rekening, alamat lengkap, atau data kesehatan ke artifact git. Redaksi di output jika user menempel PII berlebih.

### 3. Mode

| Mode | Output |
|------|--------|
| **Write** | CV terstruktur (lihat `reference.md`) dari fakta user saja |
| **Review** | Temuan: kejelasan, bukti, gap JD, ATS, bias, klaim lemah |
| **Screen** | Matriks skill wajib/nice-to-have + skor 1–5 + alasan + risiko |
| **Notes** | Ringkasan catatan pewawancara → kekuatan, risiko, pertanyaan lanjutan |

### 4. Evidence vs claim

Setiap bullet kuat harus punya **bukti** (metrik, scope, stack, outcome). Tandai `UNVERIFIED` jika user tidak memberi bukti.

### 5. Bias check

Jangan skor berdasarkan usia, gender, foto, agama, status pernikahan, atau nama. Flag jika CV memuat data yang tidak relevan untuk role.

### 6. Deliver

- Markdown di chat atau `project/{id}/artifacts/other/` jika project aktif
- File `.docx`/PDF hanya jika user minta → skill `office-document-tools`
- Review: daftar P0 (blokir) vs P1 (perbaiki)

## DoD

- [ ] Fakta tidak ditambah di luar input user
- [ ] Review punya temuan konkret + saran rewrite (bukan “bagus saja”)
- [ ] Screening memisahkan must-have vs nice-to-have
- [ ] PII berlebih tidak disimpan ke repo

## 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', ...

698621 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 →