
What claude-kit provides
claude-kit is a collection of standalone skills, agents, and mods for Claude Code. Each item lives under the repository's plugins/ directory, so you can install only the functionality you need.
- savvy-flow: A skill and agent package that lets the session plan a task, delegate work to tiered worker subagents, and review their results. You invoke it with
/savvy-flowwhen installed manually, or with its plugin namespace when installed through the marketplace. - savvy-progress: A mod that adds a progress bar above the prompt and a live agents panel. It is designed for savvy-flow, but can also display any subagents.
The two plugins work independently. When both are installed, savvy-flow drives the progress bar while its workers report their progress to the agents panel.
Install claude-kit from the marketplace
The marketplace method is the simplest way to install the plugins in Claude Code.
- Open Claude Code.
- Add the repository as a marketplace and install the plugins you want:
/plugin marketplace add johnnyvizz/claude-kit
/plugin install savvy-flow@claude-kit
/plugin install savvy-progress@claude-kit
Restart the session after installation. Marketplace-installed skills and agents are namespaced. Therefore, the savvy-flow skill is invoked as /savvy-flow:savvy-flow, and its agents use names such as savvy-flow:savvy-careful.
You can install just one plugin if that better matches your workflow. Install both when you want the planning workflow and visual progress indicators to work together.
Install components manually
Manual installation is useful when you want to copy a skill into your Claude Code configuration or load a mod directly from a local checkout.
Clone the repository
git clone https://github.com/johnnyvizz/claude-kit.git ~/claude-kit
Copy the savvy-flow skill and agents
A skill does not require the plugin system when installed this way. Copy the skill folder into your Claude Code skills directory:
cp -R ~/claude-kit/plugins/savvy-flow/skills/savvy-flow ~/.claude/skills/
Then copy the supplied agent definitions into the agents directory:
cp ~/claude-kit/plugins/savvy-flow/agents/*.md ~/.claude/agents/
With this approach, names stay short: use /savvy-flow for the skill and names such as savvy-careful for the agents.
Load savvy-progress for one session
To load the progress mod only for a particular Claude Code session, start Claude Code with its plugin directory:
claude --plugin-dir ~/claude-kit/plugins/savvy-progress
Load savvy-progress for every session
To make the mod available for every session, including the desktop app, configure CLAUDE_CODE_PLUGIN_DIRS in ~/.claude/settings.json:
{
"env": {
"CLAUDE_CODE_PLUGIN_DIRS": "~/claude-kit/plugins/savvy-progress"
}
}
If you configure several plugin folders, separate them with :. If CLAUDE_CODE_PLUGIN_DIRS already has a value, append the new folder instead of replacing the existing entries.
Run a basic workflow
After installing savvy-flow, give it a task to plan and coordinate. For example, with a manually copied skill:
/savvy-flow review the authentication changes and identify missing tests
With the marketplace installation, use the namespaced form:
/savvy-flow:savvy-flow review the authentication changes and identify missing tests
The session model plans the work, delegates tasks to its worker subagents, and reviews their output. If savvy-progress is also active, the progress bar and agents panel provide a live view of that activity.
The exact task is up to you: pass a code review, investigation, or other development task that benefits from planning and delegated work.
Understand the repository layout
Each plugin follows a predictable structure. The marketplace catalog and plugin manifests define how Claude Code discovers the components:
.claude-plugin/marketplace.json the catalog `/plugin marketplace add` reads
plugins/<name>/
.claude-plugin/plugin.json manifest
skills/<skill>/SKILL.md a skill
agents/*.md subagents it ships
hooks/hooks.json a mod: points at the hooks module
hooks/register.tsx a mod: the module itself
types/index.d.ts a mod: its $.state contract
In this layout, a skill is described by a SKILL.md file and can ship agent definitions. A mod uses hook configuration and a registration module; its type declaration documents the $.state contract.
Validate plugins before publishing
Use Claude Code's validation commands to check an individual plugin or the marketplace catalog:
claude plugin validate plugins/<name>
claude plugin validate .
The first command validates a plugin directory. The second validates the repository catalog from its root.
Keep manual installations up to date
When you load a mod directly from the cloned repository, update it with:
cd ~/claude-kit
git pull
A mod loaded from that directory uses the updated files. Skills copied into ~/.claude/skills/ do not update automatically; after pulling new changes, copy the skill and agent files again.
Advanced considerations
Choose namespaced or short commands intentionally
Marketplace installation provides plugin isolation through namespaced names such as /savvy-flow:savvy-flow. Manual skill installation avoids the plugin system and keeps commands short. Use the method that best fits whether you prioritize marketplace management or direct local files.
Account for mod compatibility
Mods use function hooks through hooks/register.tsx, which is an early-access Claude Code API. The repository was tested on Claude Code 2.1.286, and the API may change between releases.
If a marketplace-installed mod does not appear, load it manually with --plugin-dir or configure its folder through CLAUDE_CODE_PLUGIN_DIRS.
Combine the plugins when you need visibility
savvy-flow can operate without savvy-progress, and savvy-progress can operate without savvy-flow. Installing both is the most informative setup: the workflow coordinates the task while the mod exposes progress and active-agent status.
Conclusion
claude-kit gives Claude Code users modular planning, delegation, review, and progress-monitoring tools. Install savvy-flow and savvy-progress from the marketplace for a managed setup, or clone the repository and copy or load components manually. Remember the namespace differences, validate changes before publishing, and update copied skills separately from repository-loaded mods.
