hire
Skill5 starsChanged 6 months agoApache-2.0View on GitHub
Full hiring pipeline: identify skill gap -> Maria researches -> Sarah hires -> Lena syncs DB
8 other projects use a version of this.
Adopted by
Most recently taken up by
- fainir/agent-harnesstheir own version, first seen Nov 1, 2026
- ARCASSystems/FounderOStheir own version, first seen Oct 24, 2026
- menkesu/awesome-pm-skillstheir own version, first seen Oct 13, 2026
- jamillazarev/multica-opstheir own version, first seen Sep 25, 2026
- markfulton/ai-employeestheir own version, first seen Sep 2, 2026
- danielgefen/soustheir own version, first seen Aug 25, 2026
Used with
Projects with it also use ship.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 3 projects that use this
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- markfulton/ai-employees★ 822same name
- menkesu/awesome-pm-skills★ 441same name
- jamillazarev/multica-ops★ 11same name
- ARCASSystems/FounderOS★ 7same name
- jamillazarev/opsinist★ 1same name
- T4LEL/Claude-Arsenal★ 1same name
- danielgefen/sous★ 0same name
- fainir/agent-harness★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- db-healthSkill
- dreamSkill
- forum-pulseSkill
- genesisSkill
- grill-meSkill
- handoffSkill
- inbox-processSkill
- kaizenSkill
- quality-gateSkill
- quarterly-reviewSkill
- session-endSkill
- session-startSkill
- sync-upstreamSkill
- twin-updateSkill
- voice-gateSkill
- weekly-reviewSkill
- write-a-skillSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
If no match, proceed with hiring.
- Very specific: line 40
Verify with grep -q "Voice rules (mandatory" .claude/agents/<name>.md.
- Distinctive: line 66
Never skip steps. Always Maria -> Sarah -> Lena.
- Distinctive: line 67
Every hire must have: agent definition, profile, roster entry, DB entry.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Hiring Pipeline
Step 1 -- Identify the Gap
The orchestrator determines that no existing team member can handle the task. Check the roster:
SELECT id, name, role FROM team_members WHERE is_active = 1;If no match, proceed with hiring.
Step 2 -- Maria Researches
Delegate to Maria (Senior Researcher):
- "Maria, pesquisa o que um expert real em [AREA] sabe, faz, e prioriza."
- Maria uses WebSearch and WebFetch to research real-world professionals
- Maria delivers a research brief to
outbox/Team Reports/research-brief-[role].md
Step 3 -- Sarah Hires
Delegate to Sarah (HR Manager) with Maria's research brief:
- Sarah designs the new team member: name, persona, identity, skills
- Sarah creates:
- Agent definition in
.claude/agents/<name>.md - Profile in
Team/<name>.md - Updates
Team/roster.md
- Agent definition in
- Sarah classifies the agent as text-producing or code-only (default: text-producing — anything emitting human-readable prose: emails, reports, briefs, slide content, posts, analyses).
- If text-producing, Sarah APPENDS the canonical voice-rules block:
Verify withcat .claude/rules/_agent-voice-block.md >> .claude/agents/<name>.mdgrep -q "Voice rules (mandatory" .claude/agents/<name>.md. Skip the whole step if you have not written a banlist yet — see.claude/rules/. - Code-only agents (pure infra, ops or code roles with no human-facing prose) skip the voice block.
Step 4 -- Lena Syncs DB
MANDATORY -- hire is NOT complete until DB is updated.
Delegate to Lena:
INSERT INTO team_members (name, role, profile_path, agent_path, joined_at)
VALUES (?, ?, 'Team/<name>.md', '.claude/agents/<name>.md', strftime('%Y-%m-%dT%H:%M:%SZ', 'now'));Log the hire:
INSERT INTO activity_history (actor_id, action, entity_type, entity_id, summary, occurred_at)
VALUES (1, 'hire_completed', 'team_member', (SELECT id FROM team_members WHERE name = ?), 'Hired [name] as [role]', strftime('%Y-%m-%dT%H:%M:%SZ', 'now'));Step 5 -- Delegate Original Task
Now delegate the original task to the new hire.
Rules
- Never skip steps. Always Maria -> Sarah -> Lena.
- Every hire must have: agent definition, profile, roster entry, DB entry.
- Report to {{OWNER}} when complete: who was hired, why, and where to find them.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

