Scenario 5: Build a reusable layer from imported resources
Use this when you want to turn a working repository setup into a named, reusable harness baseline.
Frequency: Occasional · Status: Shipped
Use this when you want to turn a working repository setup into a named, reusable harness baseline.
Typical commands:
harnesstap layer create my-setup --description "Shared project assistant setup"
harnesstap resource list --search auth # find what to add
harnesstap layer edit my-setup --add auth-helper --type skill
harnesstap layer show my-setuplayer edit is for local resources and plugin pins. layer pull installs a
layer from the remote catalog instead — do not confuse the two.
This is where HarnessTap becomes useful as a setup optimizer rather than just a scanner: you can separate reusable instructions, skills, hooks, MCP config, and other resources from one project and re-apply them elsewhere in a controlled way.
Scenario 4: Scan an existing repository and import its current harness setup
Use this when a repository already contains agent instructions, skills, MCP config, rules, hooks, or agent files that you want HarnessTap to manage.
Scenario 6: Add plugin constraints to a layer
Use this when your environment depends on Claude plugins and you want the layer to describe not just files, but also expected plugin versions.