A skill is a folder with a SKILL.md that teaches the agent one workflow it then applies on its own. Talk to the user in their language, short, without jargon (say "for every folder" or "only in your brain", never "symlink", "frontmatter" or "repo").

Where a skill lives, always one source and links elsewhere, never two copies:

For every folder (the default): ~/.agents/skills/<name>/ (Codex reads it there), linked in ~/.claude/skills/ for Claude Code.
Only for the brain or one project: <folder>/.agents/skills/<name>/, read by Claude Code through <folder>/.claude/skills, one link to that folder. Brain workflows (done, create-project, cleanup, projects) live there; the brain path is in the ## Brain section of ~/.agents/AGENTS.md or ~/.claude/CLAUDE.md.

scripts/skills.sh does every install, update and removal; never copy or delete skill folders by hand. When you got this skill from a link, download it first: curl -fsSL https://raw.githubusercontent.com/Melvynx/ai-maxxing-skills/main/skills/skill-manager/scripts/skills.sh -o <scratch>/skills.sh. Add --to <folder> to any command to work in the brain or a project instead of every folder. On Windows, run it from Git Bash.

To install: a source is skill names of the ai-maxxing kit (create-landing lumail), a GitHub repo (owner/repo), a GitHub link to a skill folder or its SKILL.md, or a local folder.

When the user asks what they can install, run bash skills.sh available (or available <repo>) and show each skill with what it lets them ask, in one short list.
Pick the place: every folder, unless the skill only makes sense in the brain or one project. Run bash skills.sh install <source> [<skill>...]. A repo with several skills and none named exits 2 with the list: ask which ones (or all). Exit 3 means a skill with that name is already there and was not installed this way: compare the two descriptions, replace it with --force when it is the same skill, otherwise ask, since it may be the user's own. Exit 4: check the name with available or the link.
Check that ~/.claude/skills/<name>/SKILL.md (or <folder>/.claude/skills/<name>/SKILL.md) opens, and tell the user the skill is ready from their next session, with the sentence that starts it.

To see what is installed: bash skills.sh list (own is a skill they made or installed another way, claude-only one Codex cannot see; offer to move it into ~/.agents/skills). To update: bash skills.sh update [<skill>...] fetches again every skill it installed. To remove: confirm the names in one line, then bash skills.sh remove <skill>...; it moves them to ~/.cache/removed-skills, so a mistake is undone by moving the folder back.

On their server agent (ssh -o BatchMode=yes hermes true < /dev/null works), run each remote command as ssh hermes '<command>' < /dev/null. Skills of the kit go through the server's own manager: hermes-setup catalog, hermes-setup add <skill>..., hermes-setup update, hermes-setup remove <skill>... (the install-skills skill walks through it). Any other skill, their own or from another link: ssh hermes 'bash -s -- install <source>' < skills.sh (or remove, list). Hermes sees it from its next conversation.