← Reddit

How do you manage skills, update them, across multiple agents?

Reddit · ultrakorne · June 14, 2026
A developer created an open source MIT-licensed CLI tool called skillm to address the lack of solutions for managing and updating skills across multiple AI agents and devices. The tool enables users to add skills globally or locally for different agents in a centralized directory with symlinks, check and update all skills through a single command, and configure support for any agent via a TOML configuration file.

Detailed Analysis

A developer within the Claude and AI coding assistant community has released an open-source CLI tool called `skillm` — available on GitHub under an MIT license — designed to solve a practical but underaddressed problem: managing, updating, and synchronizing "skills" (custom instruction sets or prompt configurations) across multiple AI agents and multiple machines. The tool emerged from a weekend project after the developer found no satisfactory existing solution when exploring commands like `gh skill` and `npx skill`. The core functionality centers on a centralized directory at `~/.skillm` that stores all skills, config files, and metadata, with symlinks distributed to individual agent directories, making it possible to maintain both global and local skill scopes from a single source of truth.

The technical architecture of `skillm` reflects sound software engineering principles for this use case. By storing canonical skill files in one location and using symbolic links to propagate them to agent-specific directories, the tool avoids the fragmentation and drift that naturally occurs when skill files are manually copied and independently maintained. A single command to check and update all skills dramatically reduces the maintenance burden, and uninstalling a skill automatically removes all associated symlinks across every agent — eliminating the orphaned configuration problem that plagues manual management. Out of the box, the tool ships with preconfigured support for Claude Code (`cc`) and OpenAI's Codex, while allowing users to extend support to any agent by adding entries to `~/.skillm/config.toml`.

The problem this tool addresses reflects a maturing phase in the AI developer tooling ecosystem. As power users increasingly work with multiple AI coding assistants — running Claude Code, Codex, Cursor, and others in parallel or in different contexts — the overhead of keeping agent configurations coherent across tools and devices has grown from a minor nuisance into a genuine workflow bottleneck. Skills, CLAUDE.md files, system prompts, and similar customization artifacts are becoming first-class assets in developer workflows, yet the infrastructure for managing them with the same rigor applied to code (versioning, distribution, dependency resolution) has lagged behind adoption.

`skillm` represents an early but meaningful attempt to close that gap by applying familiar Unix-style tooling conventions — centralized config, symlinks, a CLI interface — to AI agent customization. The MIT license and community release suggest the developer is inviting collaboration to extend the tool's agent compatibility list and refine its feature set. Whether or not this specific tool achieves broad adoption, its existence signals a broader trend: the developer community is beginning to treat AI agent configuration as infrastructure worthy of dedicated tooling, version control, and shared standards, much as Docker Compose and dotfile managers before it normalized reproducible environment management across machines.

Read original article →