Comparison
tackroom is a user-level dotfiles manager for coding agents. It syncs skills, MCP servers, hooks, roles and root instructions across the harnesses you use, and pins and audits what you install from strangers.
At a glance
| tackroom | skillshare | HarnessKit | dotagents | rulesync | ruler | openskills | npx skills |
APM | |
|---|---|---|---|---|---|---|---|---|---|
| Scope | user | user, and per project | user, and per project | user, and per project | project, and a global mode | project | user + project | project, and per user with -g |
project, and a user scope |
| Skills | ✓ | ✓ | ✓ | ✓ | ✓ | ~ | ✓ | ✓ | ✓ |
| MCP | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | - | - | ✓ |
| Hooks | ✓ | ✓ | ~ 10 of 17 agents | ~ 3 of 8 agents | ✓ | - | - | - | ~ per target |
| Roles | ✓ native | ✓ | - lists, does not write | ✓ subagents | ✓ | ~ | - | - | ~ per target |
| Root instructions | ✓ | ✓ | - lists, does not write | - | ✓ | ✓ | - | - | ~ per target |
| Memory | ~ delivers files you list | ✓ shared Markdown notes | ~ lists files; a Kit can carry them | - | - | - | - | - | - |
| Pin + audit externals | ✓ lock + audit | ~ audit; commit pins in project mode | ~ trust score; no lockfile | ~ trust allowlist, ref pins; no audit | ~ lockfile; no audit | - | - | ~ lock: content hash, commit for Git sources; no audit gate | ✓ lock; install blocks hidden Unicode |
| Cooldown (72h minimum release age) | ✓ | - | - | ~ opt-in, git sources only | - | - | - | - | - |
| Per-harness settings | ✓ | - | - | - | - | - | - | - | - |
| Periodic sync | ✓ | - | - | - | - | - | - | - | - |
| Desktop app | - (web view) | ✓ | ✓ | - | - | - | - | - | - |
| Terminal panels | ✓ Herdr panel · Tern crons panel and workspace command · Rex workspace command and palette actions · tmux and zellij workspace commands | ✓ Herdr panel | - | - | - | - | - | - | - |
| Harness depth | deep | broad | broad | broad | broad | broad | narrow | broad | broad |
✓ full, ~ partial, - none. The other tools' cells follow their public READMEs and documentation as read on 2026-11-13, HarnessKit's its docs and dotagents' its README and docs as read on 2026-11-16, skillshare's memory cell its v0.24.0 release notes as read on 2026-11-16, rulesync's pin cell its declarative sources guide as read on 2026-11-17, and the npx skills and APM columns their READMEs and docs as read on 2026-11-18; check them before you rely on one.
skillshare vs tackroom
skillshare is the closest tool. It syncs skills, agents, MCP servers, hooks and plugins at user level, with a desktop app, a web dashboard and a merge, copy or symlink mode per target. It audits skills against a configurable block threshold.
For pins, it writes .skillshare/skills.lock.json in project mode (how the lockfile works). In its global mode it records sources and file hashes in a local .metadata.json, which its documentation calls personal machine state.
tackroom goes further in three places:
- external skills are pinned in
tackroom.lock, which lives in your config repo and is shared by every machine; - new pins and new exact package versions wait out a 72-hour cooldown, the minimum release age, and an item still inside it is skipped until the cooldown ends or you pass
--allow-fresh; - each harness accepts declared settings keys, and a periodic job keeps machines in sync.
skillshare's documentation describes none of these. See Moving from skillshare to move over.
Memory goes the other way. Since v0.24.0 (2026-10-03), skillshare keeps shared Markdown notes in extras/memory, with commands and a dashboard page to browse and search them, and you connect the agents that read them. tackroom runs no memory system: it delivers the files you list under instructions:, and capture is left to a separate tool such as rem. See memory.md.
HarnessKit vs tackroom
HarnessKit is an app: a desktop app, a web UI and an hk CLI. It shows the extensions, rules, memory and subagent files of 17 agents in one place, and copies skills, MCP servers and some hooks from one agent to another. It adds a marketplace, a 0 to 100 trust score from 20 static rules, and per-project scope. tackroom has none of those in that form.
It changes each agent's files in place and keeps no config repo of its own. Its documentation describes no lockfile, no minimum release age for new versions, no scheduled sync and no way to sync two machines. A Kit carries a setup instead: a snapshot of skills, MCP servers, rules and memory files exported as a zip, applied to projects only. The hk CLI lists, audits, enables and disables, and does not install.
tackroom is the other shape: one config repo you edit and commit, written into 16 agents, with pins in a lockfile, a 72-hour cooldown, an audit gate, per-harness settings, roles and root instructions it writes, and a periodic job that keeps machines in sync. The two can run on one machine; HarnessKit then shows what tackroom wrote.
dotagents vs tackroom
dotagents is Sentry's tool, and it works per repository as well as per user. It declares skills, MCP servers, hooks, subagents and plugins in agents.toml, either globally under ~/.agents/ or committed in a repository, so a collaborator runs dotagents --project install and gets the same setup. tackroom has no project manifest and no team workflow, because it manages only your own user-level setup.
dotagents supports eight agents, has a [trust] allowlist of GitHub orgs, repos and git domains, pins a source to a ref such as @v1.0.0, and has an optional minimum_release_age, in minutes and off unless you set it, for git sources. Its agents.lock records the resolved commit, which its documentation calls informational only. Its documentation does not describe an audit of skill contents, root instructions, per-harness settings or a periodic sync.
tackroom pins commits in a lock shared by every machine, audits what it pins, and applies a 72-hour cooldown by default, to exact npm and PyPI versions as well as git sources. For git sources both tools go by the commit date, which the committer sets, so it is a weaker clock than a registry publish time; skills.md lists what the cooldown does not cover. tackroom itself was called dotagents until 2026-10-02 and is unrelated to Sentry's project.
The rest
rulesync and ruler generate config per repository; rulesync also has a --global mode, and ruler a global config used when a repository has no .ruler/ folder. rulesync pins each declared Git source to a commit in rulesync.lock, and each npm source to a version and integrity hash in rulesync-npm.lock.json, and installs from those with --frozen. Its documentation describes no audit of what it pins and no minimum release age.
npx skills and openskills install skills only. npx skills installs into a project or, with -g, for the user. It records a content hash for each project skill in skills-lock.json, and for a skill from a Git source the commit it came from; install --frozen-lockfile checks them. A skill from a direct download has no commit to pin. openskills has had no release since v1.5.0 on 2026-01-17.
APM is Microsoft's package manager for agent setup. apm.yml declares a repository's instructions, skills, prompts, agents, hooks, plugins and MCP servers, apm.lock.yaml pins the resolved tree with content hashes, and every install scans for hidden Unicode and blocks a package with a critical finding. The scan looks for nothing else: prompt-injection text, secrets and piped downloads are outside it. It is built for a team's repository and an organisation's policy file, with a user scope beside it, and its target matrix shows which agent gets which surface. Its documentation describes no minimum release age and no periodic sync.
None of them treats a personal setup as a dependency-managed dotfiles repo. For what tackroom refuses to do, read philosophy.md.
Moving from skillshare
skillshare and tackroom solve the same problem: one place for your agent skills, roles, hooks, MCP servers and instructions. This section maps a skillshare setup onto tackroom.yaml and the ~/.agents folders; skillshare vs tackroom says where the two differ.
Mapping
| skillshare | tackroom |
|---|---|
Skills source folder (default ~/.config/skillshare/skills) |
~/.agents/skills/ for skills you wrote |
Skills installed from a repo (skills: entries with a source) |
external_skills:, pinned in tackroom.lock |
| Agents source folder | ~/.agents/agents/, rendered into each harness's role format |
targets |
agents: entries, one per harness; setup detects them |
mcp.servers |
mcp_servers: |
Hooks managed with skillshare hooks |
hooks: |
audit.block_threshold |
doctor audit: an unaccepted CRITICAL finding in external content blocks sync, and new pins wait 72 hours |
An extra holding a shared AGENTS.md or similar |
~/.agents/AGENTS.md, plus instructions: for more files |
Steps
- Preview.
tackroom setup --dry-runlists what it would import and changes nothing. - Copy what you wrote. Skills are
skills/<name>/SKILL.mdand roles areagents/<name>.mddirectly under the config root:mkdir -p ~/.agents/skills ~/.agents/agents cp -R ~/.config/skillshare/skills/<your-skill> ~/.agents/skills/ cp ~/.config/skillshare/agents/<your-role>.md ~/.agents/agents/ - Pin external skills. For each repo skillshare installed from, add it to tackroom so the commit is pinned and audited instead of copied:
tackroom skill sources add owner/repo --skills a,b - Move hooks into a top-level
hooks:block:hooks: - name: notify-stop enabled: true event: Stop # Claude Code event names command: ~/.agents/hooks/notify.sh timeout: 10 # seconds agents: [claude, codex] # optional; default: every harness with hooks - Move MCP servers with
tackroom mcp add NAME --command ... [--arg ...]or--url ..., or write them inmcp_servers:. To adopt one a harness already has, runtackroom mcp import <harness> <name>. - Move Pi packages and per-harness settings under the harness's own entry:
agents: - name: pi enabled: true detect: pi packages: - npm:<package>@<exact-version> settings: <dotted.key>: <value> - Run it. On the first machine,
tackroom setup. After that,tackroom syncandtackroom doctor.
Skills that skillshare linked into a harness are relinked to the canonical copy on the first sync. A real folder with different content is never replaced without your confirmation, and then only after a backup.
Verify
tackroom statusshows every harness synced with no drift.tackroom doctorhas no failures, and any item in cooldown or blocked has a reason instatus.tackroom hook listandtackroom mcp listmatch what skillshare used to write.
Clean up
Once tackroom status is clean, uninstall skillshare the way you installed it and remove its config folder, so the two tools never write the same harness files.