agr CLI
agr is a package manager for agent skills: installs them from any Git repo into Claude Code, Cursor and Codex by a versioned manifest, like npm or uv
- 453 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Clones and installs skill code from arbitrary public Git repositories at a given path with no content review of its own
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/agrDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Clones and installs skill code from arbitrary public Git repositories at a given path with no content review of its own
This is third-party code. Review the repository files before installing.
What it does
agr installs with uv tool install agr and offers five operations. agr add owner/repo/skill takes a path inside a public GitHub repository, for example anthropics/skills/pdf, auto-creates agr.toml, detects which AI tools are installed on the machine, and installs the skill into each one. agr add ./skills/my-internal-skill does the same for a local folder that has not been split into its own repository yet. The agr.toml file keeps the dependency list and the tools field, and agr.lock pins the exact version of each skill. That pair of files gets committed to the repository instead of the .claude/skills and .cursor/skills folders themselves, which the tool suggests adding to .gitignore as build artifacts. A new teammate clones the repository and gets the same skills at the same version with agr sync, and agr upgrade only bumps versions when that is explicitly chosen. Invoking an already installed skill needs a slash in Claude Code and Cursor, a $ in Codex, or just the name in OpenCode and similar tools. The author's own GitHub project description calls it educational, and the repository topics state outright that it is not actively maintained, so a team should check issue activity and recent commits before relying on it.
Who it is for. For developer teams who use the same skills across Claude Code, Cursor and other agents and want them versioned through Git instead of copying folders between machines by hand.
Good fit when
- You want the official Anthropic pdf skill installed with one command, agr add anthropics/skills/pdf, into every detected tool at once
- A team wants everyone on the same skill set at the same version: agr.toml and agr.lock get committed, and a new teammate runs agr sync
- An internal skill is still being written and is not split into its own repository: agr add ./skills/my-internal-skill pulls it from a local folder
- You want a skill version bumped deliberately, not automatically: agr upgrade does that on an explicit command
- A project uses several agents at once, say Claude Code and Cursor, and one skill needs to show up in both
Not a fit when
- You need actively maintained infrastructure with a bug-fix guarantee: the repository's own description and topics call the project educational and not actively maintained
- The skill is in a private repository with no Git access configured on the machine: agr works through a plain git clone, and access is configured separately from agr itself
- You want one public skill registry with search and ratings: agr installs straight from a path in a GitHub repository, with no catalog of its own
Example request
Install Anthropic's official pdf skill through agr into every tool detected on this machine and commit agr.toml with agr.lockLimitations
GitHub marks the repository itself as an educational project about a package manager for agent skills, and its own description lists it as unmaintained. Install needs uv or an equivalent way to run the Python package; the README describes no other install path. agr sync and agr upgrade depend on each skill's source Git repository staying reachable: if that source repository is deleted or turns private, reinstalling it through agr stops working.
How to disable. Remove agr with uv tool uninstall agr. The project's agr.toml and agr.lock files can be deleted by hand, and already installed skill folders in .claude/skills or .cursor/skills stay in place and come off separately if no longer needed.
FAQ
How do I install agr?
With uv tool install agr, which needs uv installed. After that, agr add, agr sync and agr upgrade become available.
How do I install a skill from GitHub through agr?
With agr add owner/repo/skill, for example agr add anthropics/skills/pdf. agr creates agr.toml itself, detects the tools installed on the machine and installs the skill into each one.
How do I keep the same skill set across a whole team?
Commit agr.toml and agr.lock instead of the .claude/skills and .cursor/skills folders. A new teammate clones the repository and runs agr sync to get the same set at the same version.
Is agr actively maintained?
The repository on GitHub describes itself as an educational project about a skill package manager, and its topics mark it as not actively maintained, so a team should check issue and commit activity before relying on it.
Can a local skill not yet in its own repository be installed?
Yes, with agr add ./skills/my-internal-skill pointing at a path on disk. It syncs into every tool the same way a skill from a remote repository does.
Discussion
No questions or reviews yet.
Related
CLI toolsThe author's personal set: shared agent rules and dozens of skills for GitHub, the browser, macOS, messaging and releases, plus a sync script
agnix lints CLAUDE.md, AGENTS.md, SKILL.md, hooks and MCP configs with 702 rules, autofix and editor extensions for VS Code and JetBrains
Softaworks Agent Toolkit
Softaworks Agent Skills
A marketplace of skills, subagents and commands for coding agents: development, documentation, planning and workplace communication
Tech Leads Club Agent Skills
Agent Skills
A vetted skill registry with a CLI that installs into twenty-plus agents and an MCP server for on-demand skill lookup
Claude Code Skills and Agents
Claude Code Skills & Agents
A Claude Code plugin bundling skills and sub-agents: deep research, image generation, GitHub work, code review and model switching
A shared skill and tooling infrastructure for 1C development, wired in as a git submodule and laid out across several agents at once
README in short
The README compares agr to npm, PyPI and uv for code and explains why the same principles, versioning, locking, a shared manifest, should apply to agent skills too. It continues with a list of five operations and example commands, a table of invoke syntax per tool from Claude Code to Pi, and a section on a shared team manifest using agr.toml and agr.lock instead of tool folders in the repository.