alexsmedile/apm

記録された最新のソース活動: 2026年5月5日 23:08

SkillsMP カタログ更新: 2026年10月26日 11:37

収集済み skills: 5

GitHub スター: 2
GitHub フォーク: 0

AI アシスタントでインストール

このプロンプトをコピーして、使用中の AI アシスタントに送ってください。

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/alexsmedile/apm.

リポジトリの README

README の元ファイル：README.md

README の元ファイルを読む

README 全文を表示

# apm — Agent Package Manager _Write an agent once. Install it everywhere._ **A local-first CLI package manager for AI agent and skill files.** `apm` syncs your library of agent definitions and manages installation into the agent runtimes it currently verifies end-to-end. It handles: `install`, `diff`, `update`, `import`, and optional **GitHub sync** — all with atomic writes, locking, and backups. | Status | Targets | |---|---| | **Managed now** | Claude Code agents and skills, Gemini CLI agents, Codex skills, Windsurf skills, `agents-dir` generic store | | **Coming soon / not yet verified end-to-end** | Cursor, Continue, Codex agents, Windsurf rules, Gemini skills, generic export UX | > This tool is under active development. It may contain bugs. Always back up your data. ## Features <table> <tr> <td align="center" width="33%"> <h3>📚 One Library, All Tools</h3> Define an agent once in your library. Install it to the runtimes `apm` currently verifies — with the right format for each. </td> <td align="center" width="33%"> <h3>🔄 Sync State Tracking</h3> Always know what's installed, what's outdated, and what's drifted. <code>apm list</code> gives you a full picture at a glance. </td> <td align="center" width="33%"> <h3>📥 Import Agents</h3> Already have agents scattered across tool directories? <code>apm import</code> brings them into your library with a single command. </td> </tr> <tr> <td align="center"> <h3>☁️ GitHub Sync</h3> Back up and share your library via GitHub. Monorepo or per-agent mode. Push, pull, and diff from the CLI. </td> <td align="center"> <h3>🛡️ Safe by Default</h3> Atomic writes, file locking, and automatic backups before every destructive operation. No silent overwrites. </td> <td align="center"> <h3>🗂️ Categories</h3> Tag agents with a category and install entire groups at once. Keep your library organized as it grows. </td> </tr> </table> ## Problems apm solves | Without apm | With apm | |---|---| | ❌ You copy-paste the same agent prompt into multiple coding tools — and they drift apart over time. | ✅ One source of truth in your library. Install to supported runtimes with one command. | | ❌ You edit an agent directly in `~/.claude/agents/` and forget which version is canonical. | ✅ Library always wins. Runtime is treated as a deploy target, never the source. | | ❌ You have no idea which installed agents are outdated or missing after switching machines. | ✅ `apm list` shows sync state for every agent — in-sync, outdated, ready, or unmanaged. | | ❌ You accumulate random `.md` files in your agents directories with no record of where they came from. | ✅ Every installed file is stamped with `apm.id`, platform, and install timestamp. | | ❌ Updating an agent means manually finding and overwriting files across multiple tools. | ✅ `apm update` reinstalls every outdated agent in one shot, with backups. | ## Install ```bash git clone https://github.com/alexsmedile/apm.git cd apm bash install.sh # links apm into ~/.local/bin apm setup # configure library path, platform, optional GitHub ``` **Requirements:** - bash 4+ - python3 + PyYAML (`pip3 install pyyaml`) - git (optional, for GitHub sync) ## Quickstart ```bash apm list # show all agents and sync state apm install agent-mentor # install agent to runtime (~/.claude/agents/) apm link agent-mentor # symlink runtime file directly to split instructions apm diff agent-mentor # compare library vs runtime apm update # reinstall all outdated agents apm import # import unmanaged runtime agents into library # Skills apm -s list # list all skills and sync state apm -s find browser-use # search library apm -s -p cc install browser-use # install to claude-code apm -s -p cc,agt install browser-use # install to multiple platforms at once apm -s -p cc install --all # install all ready/outdated skills ``` ## Library layout `apm` supports different canonical layouts for agents and skills. Agents: ```text agents_db/ agent-mentor/ agent-mentor.md # required root file instructions/ # optional agent-mentor@latest.md # optional generic active body agent-mentor.cc@latest.md # optional platform-specific body versions/ # optional snapshots/backups/history ``` Agent rules: - The canonical ID is the folder name. - The required root file is `<id>/<id>.md`. - `instructions/` is optional and keeps the current body split out of the root file. - Body resolution order is `<id>.<platform-alias>@latest.md` → `<id>@latest.md` → `<id>_latest.md` (legacy) → root file body. Skills: Preferred monorepo-style layout: ```text skills_db/ repo-name/ skills/ browser-use/ SKILL.md shadcn/ SKILL.md ``` Fallback direct layout: ```text skills_db/ browser-use/ SKILL.md shadcn/ SKILL.md ``` Skill rules: - `apm` prefers `skills_db/<repo>/skills/<skill>/SKILL.md`. - If a top-level entry has no `skills/` folder, `apm` falls back to `skills_db/<skill>/SKILL.md`. - The canonical skill ID is the skill folder name that directly contains `SKILL.md`. - When a repo has multiple sub-skills, register the repo once in `skills_db` — all sub-skills are auto-discovered and individually installable by ID with no extra symlinks. Platform aliases: `claude-code→cc`, `cursor→crs`, `gemini→gmn`, `codex→cdx`, `agents-dir→agt`, `generic→gen` > **About the "agents".** In most AI tools, "agent" means the tool's primary AI persona, but the `agents/` directories (`~/.claude/agents/`, `~/.cursor/agents/`, etc.) actually hold **subagents** — specialized, named agents invoked for specific tasks. `apm` manages subagents only. ### Categories Add `category: <name>` (or `group: <name>`) to any agent's frontmatter to group it: ```yaml category: devtools ``` Then install the whole group at once: ```bash apm install --cat devtools ``` `apm list` shows the category column when any agents have one set. ## Install target folders The tables below list the targets `apm` currently manages and that were re-checked against current platform docs. Verified agent install targets: | Platform | Global target | Project target | |---|---|---| | `claude-code` | `~/.claude/agents/` | `.claude/agents/` | | `gemini` | `~/.gemini/agents/` | `.gemini/agents/` | | `agents-dir` | `~/.agents/` | `.agents/` | Verified skill install targets: | Platform | Global target | Project target | Behavior | |---|---|---|---| | `claude-code` | `~/.claude/skills/` | `.claude/skills/` | symlink skill dir | | `codex` | `~/.agents/skills/` | `.agents/skills/` | symlink skill dir | | `windsurf` | `~/.codeium/windsurf/skills/` | `.windsurf/skills/` | symlink skill dir | | `agents-dir` | `~/.agents/skills/` | `.agents/skills/` | symlink skill dir | `generic` currently means an export-only convenience target (`~/Desktop/agents-export/` by default), not a verified first-class platform integration. Coming soon: - `cursor`: official docs currently point to `.cursor/rules` and `AGENTS.md`, not a verified `.cursor/agents/` runtime. - `continue`: official docs currently point to `.continue/rules`, not a subagent runtime directory. - `codex` agents: current Codex docs emphasize `AGENTS.md` and skills; an `agents` runtime folder is not verified here yet. - `windsurf` agents: Windsurf exposes rules, skills, workflows, and `AGENTS.md`; `apm` does not yet model Windsurf rules as a first-class managed target. - `gemini` skills: Gemini CLI documents subagents in `.gemini/agents/`, but a SKILL.md-based skill runtime is not verified here yet. ## Install modes and direct symlinks `apm` supports two different symlink-based workflows: - `install` with `INSTALL_MODE=symlink`: `apm` writes the generated runtime file into `~/.agents/` and symlinks the tool-specific runtime path back to that managed file. This keeps frontmatter like `apm.id`, `installed-at`, and deploy metadata intact. - `--mode skills install`: `apm` creates a directory symlink from the selected verified skill target back to the canonical skill folder in `SKILLS_DB`. - `link` / `unlink`: `apm link <id>` creates a runtime symlink that points directly at the resolved split instruction body in your library. This is useful when you want runtime to follow the library body exactly without generating a runtime wrapper file. Examples: ```bash apm install agent-mentor # normal copy install INSTALL_MODE=symlink apm install agent-mentor apm --mode skills --platform claude-code install browser-use apm link agent-mentor apm link agent-mentor --as review-helper apm links apm unlink agent-mentor --all ``` Notes: - `link` resolves the active body using the normal platform precedence: `<id>.<platform>@latest.md`, then `<id>@latest.md`, then the root file body. - If the split file does not exist yet, `apm link` can generate `instructions/<id>.<platform-alias>@latest.md` from the root body. - `unlink` removes only tracked symlinks and refuses to delete regular files. - Plain `unlink` targets the current scope. Use `--project`, `--global`, or `--all` to be explicit when needed. ## GitHub sync Two modes: - **monorepo** — all agents in one repo, each in a subdirectory - **per-agent** — each agent has its own repo ```bash apm github connect # configure mode, owner, repo apm github push --all # push everything apm github pull agent-mentor # pull one agent (staged by default) ``` ### Private and team repos Both modes work with private repos — apm shells out to `git`, so it uses whatever credentials git already has. Authenticate once per machine: ```bash gh auth login gh auth setup-git # routes HTTPS github.com clones through your gh token ``` That is the whole setup. A private agent library then syncs exactly like a public one, and access is managed by GitHub repo or org-team permissions rather than by apm. > Without `gh auth setup-git`, a private repo fails as if it does not exist > rather than as a permission error — easy to misread as a typo in the owner > or repo name. ## Commands | Command | Description | |---------|-------------| | `setup` | Interactive config wizard | | `config` | Show resolved configuration | | `list` | List agents with sync state and category | | `status` | Count summary by state | | `validate [id]` | Validate agent(s) in library | | `diff <id>` | Show library vs runtime diff | | `install <id> [id…]` | Install agents, or in `-s` mode create skill symlinks | | `install --all` | Install every ready/outdated agent or skill | | `install --cat <name>` | Install all agents in a category (agents mode) | | `find <query>` | Search library by name or description | | `scan [--dir <path>]` | Find unmanaged skills in tool directories | | `scan autofix` | Convert managed-copy skill entries to symlinks | | `duplicates` | Find content-identical or redundant skills (skills mode) | | `link <id>` | Symlink agent body directly into the runtime dir | | `unlink <id>` | Remove tracked symlink(s) for an agent | | `links [id]` | List tracked symlinks for one agent or all agents | | `remove <id>` | Remove agent runtime file, or in `--mode skills` remove the skill symlink | | `update [id]` | Reinstall outdated agent(s) — omit for all | | `import` | Pick from unmanaged runtime agents (interactive) | | `import [id]` | Import specific agent, or `--all` for everything | | `github connect` | Configure GitHub sync | | `github status` | Show library vs GitHub sync state | | `github push <id>` | Push agent to GitHub, or `--all` for everything | | `github pull <id>` | Pull agent from GitHub, or `--all` for everything | | `github diff <id>` | Diff library vs GitHub | | _(no args)_ | Interactive REPL dashboard | ### Global flags ``` --db <path> Override library path --platform <name> Override platform (claude-code, cursor, codex, gemini, agents-dir, generic) Comma-separated for multi-platform install: -p cc,agt --install-mode <mode> Override install mode (`copy` or `symlink`) --json Machine-readable JSON output --dry-run Preview without writing --force Skip confirmation prompts ``` ## Sync states | Symbol | State | Meaning | |--------|-------|---------| | `✓` | in-sync | Runtime matches library | | `⤷` | linked | Runtime is a direct symlink to the active library body or skill dir | | `⤸` | linked-outdated | Runtime is a symlink, but points to the wrong target | | `~` | outdated | Runtime installed but behind library | | `○` | ready | In library, not yet installed | | `!` | unmanaged | Runtime file with no library entry | | `?` | orphan | Has apm.id but library entry missing | | `-` | no-deploy | No deploy config for current platform | | `x` | collision | Canonical ID conflict | ## Docs - [`docs/TUTORIAL.md`](docs/TUTORIAL.md) — practical getting-started guide for normal users - [`docs/ARCHITECTURE.md`](docs/ARCHITECTURE.md) — module boundaries and data flow - [`docs/WORKFLOWS.md`](docs/WORKFLOWS.md) — usability Q&A and edge cases - [`docs/AGENT_ENTRY_SCHEMA.md`](docs/AGENT_ENTRY_SCHEMA.md) — library metadata and deploy schema reference - [`docs/DATABASE_LIBRARY.md`](docs/DATABASE_LIBRARY.md) — canonical database layout guide - [`docs/CHANGELOG.md`](docs/CHANGELOG.md) — version history - [`docs/CONTRIBUTING.md`](docs/CONTRIBUTING.md) — how to contribute ## Playground A safe, resettable test database lives in `tests/fakeagents-db/` with two fake agents (`gino`, `pino`) synced to a private GitHub monorepo at `<user>/fakeagents-db`. ```bash # One-time config setup (recreate after reboot) mkdir -p /tmp/apm-fake-config && cat > /tmp/apm-fake-config/config.sh <<EOF AGENTS_DB="$(pwd)/tests/fakeagents-db" APM_PLATFORM="claude-code" APM_GITHUB_MODE="monorepo" APM_GITHUB_OWNER="<user>" APM_GITHUB_MONOREPO="fakeagents-db" APM_GITHUB_BRANCH="main" EOF # Session env export AGENTS_DB="$(pwd)/tests/fakeagents-db" export APM_CONFIG_DIR=/tmp/apm-fake-config export CLAUDE_AGENTS=/tmp/fake-rt && mkdir -p \$CLAUDE_AGENTS # Try it out bash apm --platform claude-code list bash apm --platform claude-code install gino bash apm --platform claude-code github status # Reset library to committed state git checkout tests/fakeagents-db/ ``` ## Development ```bash make test # run all 9 test suites (~127 tests) make lint # static checks (bash -n, py_compile) make install # install to ~/.local/bin make uninstall # remove symlink ```

リポジトリの README を読み込んでいます…

このリポジトリの skills

ソフトウェア開発者ウェブ開発者

2 件の職業カテゴリ · 100% 分類済み

skill

職業分類

説明

更新

apm

ソフトウェア開発者

Use apm to manage AI agents and skills. Trigger on: "install skill X", "install agent X", "remove skill X", "uninstall agent X", "list skills", "list agents", "import agent", "update agent", "check agent status", "scan skills", "find duplicate skills", "what…

原文の言語: 英語

2026-05-05

browser-use

ソフトウェア開発者

Browser automation skill.

原文の言語: 英語

2026-04-18

shadcn

ウェブ開発者

shadcn/ui workflow skill.

原文の言語: 英語

2026-04-18

browser-use

ソフトウェア開発者

Browser automation skill.

原文の言語: 英語

2026-04-18

shadcn

ソフトウェア開発者

shadcn/ui workflow skill.

原文の言語: 英語

2026-04-18

収集済み skill 5 件中 5 件を表示しています。