# Hr Staffing

> Build staffing plans for pure-soul agents, mixed soul+skill agents, and skill attachments

- **Type:** Skill
- **Install:** `agentstack add skill-sdwolf4103-opencode-agenthub-hr-staffing`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [sdwolf4103](https://agentstack.voostack.com/s/sdwolf4103)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [sdwolf4103](https://github.com/sdwolf4103)
- **Source:** https://github.com/sdwolf4103/opencode-agenthub/tree/main/src/skills/hr-staffing

## Install

```sh
agentstack add skill-sdwolf4103-opencode-agenthub-hr-staffing
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# HR Staffing Protocol

## Purpose

Produce a staffing plan that is advisory, explicit, and downstream-compatible with Agent Hub composition.

## Prerequisites

This skill must not be invoked until the parent HR agent has completed `Stage 1 - REQUIREMENTS` and the user has confirmed the requirements summary. If requirements are still ambiguous, return that gap to the parent instead of pretending the plan is ready.

## Output Files

Write the latest plan to:

- `$HR_HOME/state/staffing-plans/latest.json`
- `$HR_HOME/state/staffing-plans/latest.md`

## Required Plan Structure

Every staffing plan must include:

- `schema_version`
- `task_summary`
- `recommended_team`
- `alternatives`
- `composition`
- `required_skills`
- `required_tools`
- `draft_names` (draft agent names and draft profile name for user review)
- `risks`
- `team_size_advisory` (included when recommended team exceeds four agents)
- `next_action`

## Compact Summary Shape

Keep `latest.md` compact and field-based. Use this shape:

```text
recommended:
- role: ... | source: ... | agent_class: ... | model: ...
alternatives:
- ...
composition:
- ...
draft_names:
- seat: ... | proposed_agent_name: ... | reason: ...
- profile: ... | reason: ...
required_skills:
- skill: ... | why: ...
risks:
- ...
team_size_advisory: 
next_action: ...
```

## Composition Rules

For each recommended entry, specify:

- `asset_kind`: `agent` or `skill`
- `agent_class`: `pure-soul`, `mixed-soul-skill`, or `not-applicable`
- `deployment_role`: `primary-capable`, `subagent-preferred`, or `skill-attachment`
- `compatibility`: `native-ready`, `needs-adaptation`, or `skill-only`

## Decision Rules

- At least one staffing-plan entry must have `deployment_role: primary-capable`.
- Prefer the smallest team that can cover planning, sourcing/exploration, implementation, audit, verification, and documentation.
- If the recommended team has more than four agents, include a `team_size_advisory` noting that the team should be structured around one to two primary agents with the remaining agents deployed as subagents. Do not recommend more than two primary-capable agents unless the user explicitly requests it.
- When multiple candidates can cover the same seat, prefer a pure-soul agent with attached skills over a mixed soul+skill agent. Use a mixed soul+skill agent only when the specialized workflow cannot be cleanly separated, the source is tightly fused, or the user explicitly wants that mixed form.
- Prefer local worker cards from `$HR_HOME/inventory/workers/` with `inventory_status = available`.
- Treat `draft` worker cards as sourcing inputs that still need review or explicit operator acceptance.
- Exclude `retired` worker cards from recommended staffing compositions.
- Treat user-supplied model names as advisory. Model confirmation happens during staging via opencode environment availability probing, not during staffing planning. If a user-supplied name looks syntactically invalid, note that, but do not attempt catalog-based validation here.
- If multiple valid compositions exist, present them as options rather than pretending one is certain.
- If a skill host is unresolved, say so plainly.
- Draft names must be treated as proposals only. The parent HR agent must show them to the user and get confirmation before adaptation starts.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [sdwolf4103](https://github.com/sdwolf4103)
- **Source:** [sdwolf4103/opencode-agenthub](https://github.com/sdwolf4103/opencode-agenthub)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-sdwolf4103-opencode-agenthub-hr-staffing
- Seller: https://agentstack.voostack.com/s/sdwolf4103
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.