Skills & Plugins

Skills

A skill is a reusable instruction bundle — a playbook hara can pull into context on demand (deploy steps, a review checklist, a house style). Skills load from .hara/skills/ (project) and ~/.hara/skills/ (global).

hara skills init    # scaffold an example skill
hara skills         # list available skills

In the REPL, /skills lists them and /skill <id> loads one into your next message.

Plugins

A plugin is an installable bundle — roles, skills, and tools shared across projects or teams. hara is interoperable with the Claude Code plugin layout.

hara plugin add file:./my-plugin            # local path
hara plugin add github:owner/repo           # a GitHub repo
hara plugin add git:https://host/repo.git   # any git URL
 
hara plugin                 # list installed plugins (version, status, description)
hara plugin disable <name>  # keep it installed but inactive
hara plugin remove <name>   # uninstall

How roles resolve

When the same role name exists in several places, the highest-precedence one wins:

plugins  <  org (B-end push)  <  global (~/.hara/roles)  <  .claude/agents  <  project (.hara/roles)

So a project can always override a plugin's role, and your global roles override an org-pushed bundle. See The Org Model for what a role definition contains.