RbBtSn0w

Adg — AI skill for Claude Code

AI community

One CLI to manage AI agent plugins and skills — author once in a single manifest, adapt to Claude Code, Codex & Antigravity.

How to install Adg

This entry records only its repository, not the path inside it, so there is no exact command to give. Open RbBtSn0w/adg and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Adg does

One CLI to manage AI agent plugins and skills — author once in a single manifest, adapt to Claude Code, Codex & Antigravity. Versioned & reproducible.

Alternatives in AI

Manifest — Real-time cost observability for OpenClaw agents — track tokens, costs, messages, and model usage 4.1k ★
Skills Manage — Desktop app to manage AI coding agent skills across Claude Code, Cursor, Gemini CLI, Codex, and 20+ platforms 2.2k ★
Skillport — Bring Agent Skills to Any AI Agent and Coding Agent — via CLI or MCP 408 ★

README

Agent Directory Group (ADG)

`adg` is one umbrella CLI with **two domains**, each aligned to an existing ecosystem so there is little new to learn:

Domain	Command	Aligns to
plugins	`adg plugins`	the Codex plugin flow (`~/.agents/plugins/marketplace.json`)
skills	`adg skills`	vercel-labs/skills — a vendored fork (see vendor/skills)

For plugins, one universal manifest — `.agents/.plugin.json` — is the source of truth. Runtime-specific manifests (`.claude-plugin/plugin.json`, `.codex-plugin/plugin.json`) are *generated* from it, so a plugin is authored once and adapted to each runtime.

**Control plane vs export.** ADG's own management lives in the lock (`.plugin-lock.json`: provenance, `sha256` integrity, dependencies) — that is the only file ADG treats as authoritative. `marketplace.json` is a thin **runtime-facing export** kept in the de-facto shape Codex consumes; ADG never manages plugins through it.

See [docs/authoring.md](docs/authoring.md) to author a plugin, and [docs/agents-spec.md](docs/agents-spec.md) for the `.agents/` directory spec.

Why

Skill explosion — hundreds of skills become unmanageable; ADG groups them into versioned, discoverable plugins.
Runtime fragmentation — Claude and Codex use different plugin layouts; ADG generates each from a single source.
Reproducibility — .plugin-lock.json records source, version and a content hash for every installed plugin.

Default plugin layout

A repository without a manifest is also installable when it uses the standard plugin locations: `skills//SKILL.md`, `hooks/hooks.json`, or `.mcp.json`. ADG derives a default manifest from the locations that exist. Add `.agents/.plugin.json` only when a source needs custom component paths or other plugin metadata; its `skills`, `hooks`, and `mcpServers` fields override only thei