Reseed

reseed: Agent Skills Manager

reseed manages a personal skill library and installs skills into projects. Skills are directories containing a SKILL.md file, following the Agent Skills spec. They live in each project's skills directory (.agents/skills/ by default, or .claude/skills/ for Claude Code) and are read by 30+ agents (Claude Code, Cursor, Copilot, Codex, Gemini CLI, etc.).

Your job is mainly on the project side: checking what's installed, adding what's needed, and keeping things in sync. You can also run reseed install when the user wants to pull skills from GitHub into their library, but leave the library's structure and contents to them otherwise.

Note: bare reseed (no args) opens an interactive TUI. That is for the user to run in their own terminal, not for you. If they want to browse their library visually, tell them to run reseed themselves. For everything else, use the CLI commands below.

Quick reference

reseed                              # interactive TUI (for the user to run, not you)
reseed init <path>                  # create a new library (first-time setup)
reseed status                       # what's installed in this project
reseed list -l                      # what's in the user's library (with descriptions)
reseed add <skills-or-folders...>   # copy skills (or whole folders) from library into the project
reseed remove <skills...>           # remove skills from the project
reseed sync                         # re-copy installed skills from library (get updates)
reseed install <user/repo>          # fetch skills from GitHub into the library

How it works

• The user has a library: a directory on their machine containing all their skills, organized in subfolders of any depth.
• reseed add copies skills from the library into the project's skills directory. These are real file copies, not symlinks, so they show up in git and every team member gets them.
• reseed sync re-copies skills that exist in both the project and the library, pulling in any updates. Skills not in the library are left alone, including orphans: if a skill was removed from the library after it was added to the project, sync will not delete the stale copy. Use reseed remove for that.
• There's no project manifest. Sync matches by folder name.

Typical workflow

0. Confirm the target directory

Before running project-side commands, check what directory reseed is targeting:

reseed config dir

If this prints .agents/skills (default) but the user is on Claude Code (which reads from .claude/skills/), suggest running reseed config dir .claude/skills once to switch the global default. Ask before running it since it changes user-wide config. If they prefer not to change the default, pass --dir .claude/skills on each command instead:

reseed --dir .claude/skills add commit

If reseed config dir already prints the right path, no override is needed. Run the commands below as-is.

1. Check what's already here

reseed status

If the skills directory doesn't exist yet, that's fine. reseed creates it automatically when you add skills.

2. See what's available

reseed list -l

This shows all skills in the user's library, grouped by folder, with descriptions. Use this to understand what's available before suggesting what to add.

3. Add skills to the project

reseed add commit review python-base   # mix skills and folders in one command

You can pass any number of skills and library folders in a single reseed add command; naming a folder adds every skill under it. Pick what matches the project's stack and needs.

4. Keep skills up to date

reseed sync

Run this when the user wants to pull the latest versions of their skills into the project.

Installing skills from GitHub

install and add do different things:

• reseed install fetches from GitHub into the user's library. It takes a user/repo[/path] reference, not a URL. It always fetches the repo's default branch.
• reseed add copies from the library into the project. It takes local skill names or library folder paths.

reseed install user/repo                 # all skills from the repo
reseed install user/repo/path/to/skills  # skills under a specific directory
reseed install user/repo --into mykit    # place them in a library subfolder

After installing, use reseed add to bring them into the project.

GitHub's public API allows only ~60 unauthenticated requests per hour, so running several installs in quick succession can hit the rate limit. If reseed install fails with a rate-limit error, suggest setting GITHUB_TOKEN in the environment to authenticate.

When reseed is not installed

If reseed is not found, point the user to the install command:

curl -fsSL https://raw.githubusercontent.com/nattergabriel/reseed/main/install.sh | sh

On Windows, they can download the binary from the latest release.

When there's no library yet

If reseed is installed but commands fail with "library not initialized", the user needs to create a library once:

reseed init ~/skills    # or any path they prefer

After that, the CLI commands start working against the new library.