Scenario 14: Curate and clean up the local resource DB
Use this when months of scans have left the local DB with duplicates, stale resources from deleted repos, or noisy imports you no longer need.
Frequency: Rare · Status: Shipped
Use this when months of scans have left the local DB with duplicates, stale resources from deleted repos, or noisy imports you no longer need.
Typical commands:
harnesstap resource list --type skill
harnesstap resource list --type instruction --search legacy
harnesstap resource list --type plugin_pin_pin
harnesstap resource show skill:legacy-helper
harnesstap resource delete legacy-helper
harnesstap layer delete <stale-layer-name>Valid --type values for material resources: instruction, skill, rule,
mcp_server, permission, hook, agent, command, env_var,
model_config. resource list also shows plugin resources; layer
composition refs stay hidden unless you inspect a layer directly.
Selectors for resource show accept name, type:name, or
type:name@namespace when names collide.
Scenario 13: Choose a materialization strategy (symlink vs copy)
Use this when you need to decide whether a project's alias harness outputs are written as symlinks (atomic, always in sync with the main reference) or...
Scenario 15: Apply a layer to a subset of target platforms
Use this when a repo opts into some harnesses but not others. For example, a backend repo that supports Claude Code and Codex but never used Cursor.