An open API service indexing awesome lists of open source software.

https://github.com/kasperjunge/agent-resources

A package for Claude Code, Cursor and Github Copilot. Install agent skills from GitHub with a single command.
https://github.com/kasperjunge/agent-resources

agent-skills claude-code claude-code-commands claude-code-skills claude-code-subagents

Last synced: 4 months ago
JSON representation

A package for Claude Code, Cursor and Github Copilot. Install agent skills from GitHub with a single command.

Awesome Lists containing this project

README

          

# ๐Ÿงฉ agent-resources (agr)

**A package manager for AI agents.**

Install agent skills from GitHub with one command.

[![PyPI](https://img.shields.io/pypi/v/agr?color=blue)](https://pypi.org/project/agr/)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

---

## Getting Started

Install agr CLI:

```bash
pip install agr
```

Install your first skill:

```bash
agr add anthropics/skills/frontend-design
```

That's it. The skill is now available in your configured tool (Claude Code, Codex, Cursor, OpenCode, Copilot, or Antigravity).

---

## What is agr?

**agr** installs agent skills from GitHub directly into your tool's skills folder
(`.claude/skills/`, `.codex/skills/`, `.cursor/skills/`, `.opencode/skill/`, `.github/skills/`, or `.agent/skills/`).

**agrx** runs skills instantly from your terminal โ€” download, run, then clean up.

---

## Install Skills

```bash
agr add anthropics/skills/frontend-design # Install a skill
agr add -g anthropics/skills/frontend-design # Install globally for your user
agr add anthropics/skills/pdf anthropics/skills/mcp-builder # Install multiple
agr add anthropics/skills/pdf --source github # Install from an explicit source
```

Remote installs require `git` to be available on your system.

**Beta note:** Multi-source support is only in the beta release right now. Install `agr==0.7.2b1` to use `default_source`, `[[source]]`, or `--source`.

### Handle format

```
username/skill-name โ†’ From user's skills repo
username/repo/skill-name โ†’ From a specific repo
./path/to/skill โ†’ From local directory
```

Note: `username/skill-name` now defaults to a repo named `skills`. During a
deprecation period, agr will fall back to `agent-resources` (with a warning) if
the skill isn't found in `skills`.

---

## Run Skills From Your Terminal

```bash
agrx anthropics/skills/pdf # Run a skill instantly
agrx anthropics/skills/pdf -p "Extract tables from report.pdf" # With a prompt
agrx anthropics/skills/skill-creator -i # Run, then continue chatting
agrx anthropics/skills/pdf --source github # Explicit source
```

---

## Team Sync

Your dependencies are tracked in `agr.toml`:

```toml
default_source = "github"

dependencies = [
{handle = "anthropics/skills/frontend-design", type = "skill"},
{handle = "anthropics/skills/brand-guidelines", type = "skill"},
]

[[source]]
name = "github"
type = "git"
url = "https://github.com/{owner}/{repo}.git"
```

Note: `dependencies` must appear before any `[[source]]` blocks in `agr.toml`.

Teammates run:

```bash
agr sync
```

---

## Create Your Own Skill

```bash
agr init my-skill
```

Creates `my-skill/SKILL.md`:

```markdown
---
name: my-skill
description: What this skill does.
---

# My Skill

Instructions for the agent.
```

If you're adding it to this repo, place it under `./skills/`.

Test it locally:

```bash
agr add ./skills/my-skill
```

Share it:

```bash
# Push to GitHub, then others can:
agr add your-username/my-skill
```

---

## Initialize a Repo

`agr init` can discover skills in your repo and add them to `agr.toml`.

```bash
agr init # Auto-discover skills and create agr.toml
agr init -i # Guided setup
```

Skills inside tool folders (e.g. `.claude/skills/`, `.codex/skills/`,
`.cursor/skills/`, `.opencode/skill/`, `.github/skills/`, `.agent/skills/`) are ignored by default. To bring them into
`./skills/`, run:

```bash
agr init --migrate
```

---

## All Commands

| Command | Description |
|---------|-------------|
| `agr add ` | Install a skill |
| `agr add -g ` | Install a skill globally |
| `agr remove ` | Uninstall a skill |
| `agr remove -g ` | Uninstall a global skill |
| `agr sync` | Install all from agr.toml |
| `agr sync -g` | Sync global dependencies |
| `agr list` | Show installed skills |
| `agr list -g` | Show global skills |
| `agr init` | Create agr.toml |
| `agr init ` | Create a new skill |
| `agr config tools ...` | Manage configured tools |
| `agr config default-tool ...` | Manage agrx default tool |
| `agrx ` | Run skill temporarily |

---

## Community Skills

```bash
# Go development โ€” @dsjacobsen
agr add dsjacobsen/golang-pro

# Drupal development โ€” @madsnorgaard
agr add madsnorgaard/drupal-expert
```

**Built something?** [Share it here](https://github.com/kasperjunge/agent-resources/issues).

---

## Coming from npx skills?

agr uses a slightly different handle format than `npx skills`:

| What you want | npx skills | agr |
|---|---|---|
| Skill from a repo | `npx skills add owner/repo` | `agr add owner/repo/skill-name` |
| Skill from user's default repo | โ€” | `agr add owner/skill-name` |

The key difference: `agr` handles always point to a **specific skill**, not a
repo to scan. Use the three-part format `owner/repo/skill-name` when the skill
lives in a non-default repo.

If you use a two-part handle and the skill isn't found, `agr` will check if a
matching repository exists and suggest the correct handles.

---

[Documentation](https://kasperjunge.github.io/agent-resources/) ยท [MIT License](LICENSE)