flins

flins is an open-source command-line tool that treats AI agent skills like software dependencies. Think of it as a skill installer that also keeps things clean. If you've used npm, bun, or brew, the commands will feel familiar: add, update, remove, outdated, list, search, and clean. The point is to stop managing the same skill files in a dozen places.

The problem it solves is duplication. Each coding assistant expects skills in its own folder, so a skill you want in Claude Code, Cursor, and Copilot normally lives in three directories. Update one and the other two drift out of date. In other words, you end up acting as the AI agent skill manager for every tool you use. flins keeps a single source in .agents/skills and creates symlinks into each agent's directory, so a change in one place shows up in all of them. It follows the Agent Skills open standard and pulls from GitHub, GitLab, Codeberg, or any git repository.

There are practical limits. flins is a developer tool. Not a consumer app. So you'll be working in a terminal. It's built with Bun and commonly run through npx or bunx, which means you need Node or Bun installed first. Skills themselves come from third parties, so quality varies by source, and a broken skill is ultimately the author's responsibility, not flins's. It's also still early software at version 0.3.x.

Getting Started

1. Make sure you have Node.js or Bun available on your machine, since flins runs through npx flins@latest or bunx flins.
2. Run flins search to browse the curated directory, or just pass a source directly, like flins add expo/skills.
3. Install a skill to a specific agent with the -a flag, for example flins add expo -a claude-code, or leave it out to write to the shared universal folder.
4. Run flins update when you want the latest versions, and flins outdated to see what's behind.
5. Check flins list to confirm what's installed, then let your agent pick up the linked skills.