Abatilo Bits
abatilo-bits is a Claude Code plugin for the Build phase that adds commands, hooks, skills wiring, and tracking to structure agent sessions across your workflow.
by abatilo · github.com/abatilo/bits
Extend Claude Code with commands, hooks, skills, and tracking so solo sessions stay structured across the whole builder journey.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install abatilo-bits@abatilo/bitsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:abatilo/bits") and the paste-ready config with skillselion.get_install_config("plugin:abatilo/bits").
What it does
abatilo-bits is a Claude Code plugin from abatilo/bits that catalog metadata positions around the vocabulary of bits, Claude, commands, hooks, skills, and tracking. For indie builders, that pattern reads as agent infrastructure: you are not buying a narrow API integration—you are shaping how Claude Code accepts commands, runs hooks, surfaces skills, and records what happened across sessions. That utility appears in almost every journey phase whenever you depend on an agent to carry context forward, but the canonical Skillselion shelf stays under Build and agent-tooling because the value is in the tooling layer itself. Use bits when you want more repeatable rituals—starters, guardrails, and traceability—without rebuilding hook plumbing on every new repo. Treat tracking and hook behavior as something to configure once and audit occasionally, especially before automating destructive git or deploy actions.
Highlights
- Keyword surface: bits, claude, commands, hooks, skills, and tracking
- Single-plugin community bundle (pluginCount: 1) from abatilo/bits
- Oriented toward session structure and observability of what the agent did
- Fits builders who treat Claude Code as a long-running workshop, not one-shot prompts
- Complements custom skills rather than replacing domain-specific task plugins
Why builders use it
Ad-hoc Claude Code usage loses continuity because commands, hooks, and skill invocations are not tracked or standardized across projects.
After install, you get a bits-backed layer for commands, hooks, skills, and tracking so sessions are easier to repeat and retrospect.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 9 stars, 0 votes.
FAQ
Who is abatilo-bits for?
It is for Claude Code power users who want commands, hooks, skills integration, and tracking packaged as the abatilo/bits plugin.
When should I use abatilo-bits?
Use it whenever you standardize how you start sessions, chain skills, and record work—from idea notes through ship and operate fixes.
How do I add abatilo-bits to my agent?
Install the plugin from github.com/abatilo/bits following that repository’s Claude Code registration steps, then configure hooks and commands to match your repos.
Comments
Share how you use abatilo-bits, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.