Dev Home Toolkit — Development skill for Claude Code
Skills, rules, and scripts that give Claude Code and Codex a private home base, shared across your PCs.
How to install Dev Home Toolkit
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open Sekers/dev-home-toolkit and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Dev Home Toolkit does
Skills, rules, and scripts that give Claude Code and Codex a private home base, shared across your PCs.
Alternatives in Development
- Career-Ops For Codex — Read CLAUDE.md for all project instructions, routing, and behavioral rules 32.5k ★
- Check 1: Cache Exists? — CLAUDE_DIR="${CLAUDE_CONFIG_DIR:-$HOME/.claude}" CACHE_EXISTS=$(ls -d "$CLAUDE_DIR/plugins/cache/claude-hud" 2 10.9k ★
- The Library — A Meta-Skill for Private-First Distribution of Agentics (Skills, Agents, and Prompts) across your Agents, Devi 340 ★
README
dev-home-toolkit
**dev-home** is a home base for working with AI coding agents (Claude Code and Codex): a private GitHub repo of your own, holding what your agents should have in every session. That's your own rules, your own skills, and anything those skills keep for you. Use it on one PC, as a private backup with full history, or on several, each with its own copy, so all of it travels with you from PC to PC.
**dev-home-toolkit**, this repo, is the public tooling that makes dev-home work:
- Setup. Its
setup.pycreates your dev-home the first time you run it, and clones it on your other PCs. On each PC, it connects dev-home to Claude Code and Codex, so every session loads your rules and skills. - Sync. It keeps dev-home in sync with its online copy, so your work is backed up with its
full history, and, if you use more than one PC, a change made on one reaches the others.
- Setup puts dev-home on GitHub for now (just dev-home: your project repos can be hosted anywhere). Automated setup for GitLab, Bitbucket, and Azure DevOps is coming.
- Privacy. It tells every session never to copy dev-home into your project repos, or even mention it there, so your projects can stay public.
- Skills. It comes with ready-made skills, listed below, and adds any you put in your own dev-home to your agents too.
This repo never holds anyone's own content: that stays in each person's private dev-home.
**What's a skill?** It's like a custom command for your agent: a folder of instructions that teaches it one task. Type its name to run it, such as `/handoff` in Claude Code or `$handoff` in Codex, or just ask in your own words, and the agent uses the matching skill on its own. Both agents support skills in the shared [Agent Skills](https://agentskills.io) format. To learn more, see skills in the [Claude Code docs](https://code.claude.com/docs/en/skills) and the [Codex docs](https://learn.chatgpt.com/docs/build-skills).
**Skills included:**
| Skill
Related Skills
Kilroy
A plugin that gives your agents a knowledge base shared across your team. They autonomously read what others l
Llca
A local, private log of what your coding agents do on your machine: Codex and Claude Code now, more next. Secr
AllMyAgents
Self-hosted GUI hub for managing Claude Code and OpenAI Codex agents across multiple accounts — projects, orch
Agent Spaces
Give Codex or Claude Code a separate browser workspace on Windows or Mac. Agents create accounts, automaticall
Agent Dev Toolkit
Multi-agent skills toolkit: sync shared SDD workflows, stack skills, and policy into Cursor, Claude, Codex, Co
Myconfig
Reproducible macOS setup for agent-assisted development: chezmoi dotfiles, a Claude Code/Codex sandbox, and sh
Related Agents
Nick
Nick (Dev) — Generic developer agent, reusable on any stack. Works in the task's shared worktree, reads Sam's
Bench Runner
Executes a11y skill benchmarks across hosted and local model families. Runs cloud/Codex/Ollama benchmark scrip
Stx Dev Tier API
API-tier Dev prelude for /stx-feature waves. Overrides stx-dev-base with rules for thin route handlers, auth,