Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →30eggis/harness-hiring
HR hiring. Searches .harness/shared/HR-Resource candidates, installs selected worker skills into .claude and .codex, and records roster wiring.
Passed 12 of 17 test cases with the skill, and 4 of 17 without it.
and 12 more in the full report
11 fixed5 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
We just finished placing a new worker skill into the local installation paths for the 'devops-ci' mission under Ops with model 'claude-3-5-sonnet-20241022'. Which skill should be requested to update the trigger wording for the newly added worker?
| Checked | Without skill | With skill |
|---|---|---|
| Delegates trigger wording updates to harness-resource-manager | Missed | Passed |
The instructions your model reads when the skill loads.
Hire workers from .harness/shared/HR-Resource/.
At effective S, CTO/CQO execute directly and do not hire. COO/CDO deliverables remain worker-backed at every tier. At S/M, OPS observes directly and hires only for recovery or monitoring setup. A role whose {cxx}.md is ## Not Applicable hires nobody.
cto, cqo, coo, cdo, or ops).harness/shared/HR-Resource/*/SKILL.md..claude/skills/{owning-cxx}/{name}/SKILL.md and .codex/skills/{owning-cxx}/{name}/SKILL.md..harness/shared/hr-roster.json without deleting existing hired entries. Record owner as the owning CXX, skillPath as .harness/shared/HR-Resource/{name}/SKILL.md, and skillPaths.claude / skillPaths.codex as tool-specific hierarchical installed paths..harness/documents/{mission}/{owning-cxx}/workers/{name}.md. Do not write flat .harness/documents/{mission}/workers/{name}.md except when migrating legacy missions.harness-resource-manager skill to update trigger wording.Every hired worker receives the owning CXX's relevant convention/gotcha links in the worker brief. Workers read those linked topic files only when they match the assigned task.
Worker brief: name the seeded report path and instruct the worker to fill its existing sections incrementally. Do not copy the report skeleton, Tally, or Notes block into the brief. Continue to pass relevant corpus links and copy behavioral requirements absent from the seed (including the browser-automation clause) verbatim. Reject briefs missing the seeded report path or applicable behavioral requirements.
A hire request with no model is incomplete. Record the declared model in hr-roster.json alongside owner and the skill paths, and return it to the owning CXX for the Worker Evidence Manifest.
A worker terminated by a usage limit is indistinguishable, from the outside, from a worker that finished. When a CXX comes back asking to re-hire a worker whose round went silent, ask for the usage-limit status first: a silent loop is a rate limit until proven otherwise, and re-hiring on the same exhausted model family repeats the failure.
test cases passed, vs 4 / 17 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.