HR Guide

Formalize mission, users, and outcomes for digital employees via a five-stage HR workflow.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/rocky2431/hiveclaw --skill hr-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: HR Guide
Source: https://github.com/rocky2431/hiveclaw/tree/main/backend/hr_agent_template/skills/hr-guide
Command: npx skills add https://github.com/rocky2431/hiveclaw --skill hr-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboarding new digital employees often suffers from unclear objectives and weak governance, leading to agents with vague identities and misaligned first objectives. This Skill provides a structured, repeatable HR flow to clarify the mission, users, outcomes, and governance before any creation step.

Core Features & Use Cases

  • Stage 1 — Clarify the mission: Gather the mission, primary users, core outputs, boundaries, and the first concrete objective.
  • Stage 2 — Check existing colleagues: Verify there is no duplicate role by inspecting relationships.md.
  • Stage 3 — Search installable skills (optional): Discover domain capabilities in ClawHub if domain skills are needed.
  • Stage 4 — Preview the blueprint: Present a structured plan for confirmation without performing creation.
  • Stage 5 — Create: Spawn the digital employee only after explicit user confirmation, with any requested domain skills.
  • Governance & safety: Ensure explicit user consent and proper provisioning for recurring work via triggers when applicable.

Quick Start

Clarify the mission with the user, then follow the five-stage HR flow to preview the blueprint and confirm before creating the digital employee.

Frequently Asked Questions about HR Guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I onboard a digital employee with clear objectives and governance?

Onboarding a digital employee requires a structured HR workflow to clarify the mission, primary users, core outputs, and boundaries before previewing a blueprint and spawning the agent. This enforces governance by capturing a concrete first objective and requiring explicit user confirmation prior to creation.

What is the process to create a digital agent without duplicate roles?

Creating a digital agent without duplicates involves checking existing relationships to verify no overlapping role exists before finalizing the onboarding workflow. This governance step ensures the new digital employee has a unique mission and distinct boundaries within the existing team structure.

How do I preview a blueprint before spawning a digital agent?

Previewing a blueprint before spawning a digital agent involves presenting a structured plan of the mission, users, and outcomes for explicit user confirmation. This safety mechanism prevents premature creation by requiring validation of the digital employee's first objective and boundaries.

Can I search ClawHub for installable skills when hiring a digital employee?

Searching ClawHub for installable skills is an optional stage when hiring a digital employee to discover domain capabilities needed for the role. This allows you to provision the digital agent with specific domain skills before the final creation and spawning process occurs.

Why do I need explicit confirmation to create digital employees?

Explicit confirmation to create digital employees is needed to ensure safe and auditable agent onboarding with proper governance. Requiring user consent before spawning prevents vague identities and misaligned first objectives by enforcing a structured preview of the blueprint.

When should I use a structured HR workflow for digital agent creation?

A structured HR workflow for digital agent creation should be used when onboarding suffers from unclear objectives and weak governance. This disciplined process formalizes the mission, users, and expected outcomes to prevent agents with vague identities and misaligned first objectives.