
Packport Local
Install packport-local to manage portable Claude agent packs and local pack configuration with packport and configport control skills.
Overview
packport-local is a plugin marketplace for the Build phase that adds packport and configport plugins to manage portable Claude agent packs and their local configuration.
What is this marketplace?
- 2 plugins: packport and configport
- packport: control skills for portable agent packs
- configport: control skills for local agent-pack configuration
- Designed for .packs/claude layout in the packport repo pattern
- Keeps agent capabilities modular across machines and repos
- 2 plugins in marketplace (packport, configport)
- Plugin sources under .packs/claude/packport and .packs/claude/configport
What problem does it solve?
Agent skills and pack settings fracture across laptops and repos when there is no standard way to port or configure agent packs locally.
Who is it for?
Indie builders standardizing reusable Claude agent packs across multiple codebases or machines.
Skip if: Builders who run only ephemeral one-repo setups with no interest in pack portability or config management.
What do I get? / Deliverables
After installing packport-local, you can manage portable agent packs and tune local pack configuration through dedicated control skills instead of manual file shuffling.
- packport and configport plugins available in your agent
- Portable agent packs and local pack config managed via control skills
Plugins in this marketplace
2 plugins — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Canonical shelf is Build because the marketplace delivers control skills for packaging and configuring agent capability bundles you carry across projects. agent-tooling fits skills that govern how packs are built, moved, and wired—not application frontend or production monitoring.
How it compares
Agent-pack portability marketplace, not an MCP server catalog or OSS distribution plugin.
Common Questions / FAQ
Who is Packport Local for?
Claude Code users who treat agent capabilities as versioned packs and need skills to port and configure them locally.
When should I use Packport Local?
Use it when you are consolidating skills into portable packs or syncing pack configuration across development environments during build and iterate cycles.
How do I add Packport Local to my agent?
Register the dhruvbaldawa/packport marketplace in Claude Code, enable packport and configport, and run them from a repo using the .packs/claude pack layout.