jup 0.3.1

jup - Agent Skills Manager

jup ✨

jup is a small command-line tool for installing and syncing agent skills across the local skill directories used by supported AI assistants.

It helps you:

• install skills from GitHub repositories that expose a top-level skills/ folder (or .claude/skills/ as a fallback)
• keep installed skills organized in a lockfile so they can be synced again later
• copy or link skills into the directories used by agents like Gemini, Copilot, and Claude

Quick Start 🚀

1. Install jup 📦

The preferred way to install jup is from PyPI with uv:

uv tool install jup
jup --help

If you do not want to install it, you can run it on demand:

uvx jup --help

pip also works if you prefer a traditional install:

pip install jup
jup --help

2. Check the current configuration ⚙️

jup config show

3. Choose which agent directories should receive synced skills 🤖

jup config set agents gemini,copilot,claude

Use none to clear the list:

jup config set agents none

4. Add skills ➕

jup add owner/repo --category productivity

Advanced GitHub Usage

You can use --path to specify a subdirectory (default: skills/), and --skills to select specific skill names (comma-separated) to add from the skills directory:

jup add owner/repo --path custom/skills/dir --skills skill-a,skill-b --category productivity

• --path and --skills only work with GitHub sources (not local directories).
• If --skills is omitted, all skills in the specified path are added.
• If --path is omitted, the default is skills/.
• If the specified skills directory does not exist, jup will also look for .claude/skills/ as a fallback.

You can also add local skills using relative or absolute paths (these ignore --path and --skills):

jup add ./local-skills --category productivity
jup add ../team-skills
jup add /absolute/path/to/local-skills

5. Review what is installed 📋

jup list

6. Push the managed skills into the configured agent directories 🔄

jup sync

What It Does 🧭

jup works with repositories that follow a simple structure:

repo/
  skills/
    skill-name/
      SKILL.md

When you run jup add owner/repo, it clones the repository, finds every nested skill directory under skills/ (or .claude/skills/ if present) that contains a SKILL.md file, stores those skills in ~/.jup, and records them in a lockfile.

For local sources, jup add supports either of these layouts:

local-skills/
  skill-a/
    SKILL.md
  skill-b/
    SKILL.md

or a single skill directory:

single-skill/
  SKILL.md

After that, jup sync installs the managed skills into the configured target locations. By default, jup uses symlinks, but you can switch to copying with:

jup config set sync-mode copy

The main configuration values are:

• scope: global or local
• agents: a comma-separated list of agent names
• sync-mode: link or copy

Supported Agents 🧩

jup includes built-in locations for these agent names:

• gemini
• copilot
• claude
• default

Contributing 🤝

Contributions are welcome. See CONTRIBUTING.md for development setup, workflow, and publishing details.