the-library
A Meta-Skill for Private-First Distribution of Agentics (Skills, Agents, and Prompts) across your Agents, Devices, and Teams.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/disler--the-library)HTML
<a href="/listings/disler--the-library"><img src="/api/listings/disler--the-library/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
This is a template repo. You fork it, clone it into your global skills directory, and it becomes a `/library` slash command available in every Claude Code session.
1. Fork This Repo
Fork to your own GitHub account (private repo recommended). This fork is your personal library catalog — you'll push catalog updates to it.
# Using GitHub CLI gh repo fork disler/the-library --private --clone=false
Or fork manually via the GitHub UI.
2. Clone to Global Skills Directory
Clone your fork into `~/.claude/skills/library`. This path is what makes `/library` available as a global slash command in Claude Code.
# Using git mkdir -p ~/.claude/skills/library git clone <your-fork-url> ~/.claude/skills/library # Or using GitHub CLI gh repo clone <yourname>/the-library ~/.claude/skills/library
3. Configure
Open `~/.claude/skills/library/SKILL.md` and update the `## Variables` section with your fork URL. The agent reads these variables at runtime to know where to sync the catalog.
# Before (template defaults) - **LIBRARY_REPO_URL**: `<your forked repo url>` # After (your values) - **LIBRARY_REPO_URL**: `https://github.com/yourname/the-library.git`
The other two variables (`LIBRARY_YAML_PATH` and `LIBRARY_SKILL_DIR`) are correct by default if you cloned to `~/.claude/skills/library/`.
4. Verify
Start a new Claude Code session anywhere. `/library list` should work and show an empty catalog.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 190 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- ---
- name: library
- description: Private skill distribution system. Use when the user wants to install, use, add, push, remove, sync, list, or search for skills, agents, or prompts from their private library catalog. Triggers on /library commands or mentions of library, skill distribution, or agentic management.
- argument-hint: [command or prompt] [name or details]
- ---
- # The Library
- A meta-skill for private-first distribution of agentics (skills, agents, and prompts) across agents, devices, and teams.
- ## Variables
- > Update these after forking and cloning the library repo.
- - **LIBRARY_REPO_URL**: `<your forked repo url>`
- - **LIBRARY_YAML_PATH**: `~/.claude/skills/library/library.yaml`
- - **LIBRARY_SKILL_DIR**: `~/.claude/skills/library/`
- ## How It Works
- The Library is a catalog of references to your agentics. The `library.yaml` file points to where skills, agents, and prompts live (local filesystem or GitHub repos). Nothing is fetched until you ask for it.
- **The `library.yaml` is a catalog, not a manifest.** Entries define what's *available* — not what gets installed. You pull specific items on demand with `/library use <name>`.
- ## Commands
- | Command | Purpose |
- | --------------------------- | ---------------------------------------- |
- | `/library install` | First-time setup: fork, clone, configure |
- | `/library add <details>` | Register a new entry in the catalog |
- | `/library use <name>` | Pull from source (install or refresh) |
- | `/library push <name>` | Push local changes back to source |
- | `/library remove <name>` | Remove from catalog and optionally local |
- | `/library list` | Show full catalog with install status |
- | `/library sync` | Re-pull all installed items from source |
- | `/library search <keyword>` | Find entries by keyword |
- ## Cookbook
- Each command has a detailed step-by-step guide. **Read the relevant cookbook file before executing a command.**
- | Command | Cookbook | Use When |
- | ------- | --------------------------------------- | ----------------------------------------------------------- |
- | install | [cookbook/install.md](cookbook/install.md) | First-time setup on a new device |
- | add | [cookbook/add.md](cookbook/add.md) | User wants to register a new skill/agent/prompt in catalog |
- | use | [cookbook/use.md](cookbook/use.md) | User wants to pull or refresh a skill from the catalog |
- | push | [cookbook/push.md](cookbook/push.md) | User improved a skill locally and wants to update the source |
- | remove | [cookbook/remove.md](cookbook/remove.md) | User wants to remove an entry from the catalog |
- | list | [cookbook/list.md](cookbook/list.md) | User wants to see what's available and what's installed |
- | sync | [cookbook/sync.md](cookbook/sync.md) | User wants to refresh all installed items at once |
- | search | [cookbook/search.md](cookbook/search.md) | User is looking for a skill but doesn't know the exact name |
- **When a user invokes a `/library` command, read the matching cookbook file first, then execute the steps.**
- ## Source Format
- The `source` field in `library.yaml` supports these formats (auto-detected):
- - `/absolute/path/to/SKILL.md` — local filesystem
- - `https://github.com/org/repo/blob/main/path/to/SKILL.md` — GitHub browser URL
- - `https://raw.githubusercontent.com/org/repo/main/path/to/SKILL.md` — GitHub raw URL
- Both GitHub URL formats are supported. Parse org, repo, branch, and file path from the URL structure. For private repos, use SSH or `GITHUB_TOKEN` for auth automatically.
- **Important:** The source points to a specific file (SKILL.md, AGENT.md, or prompt file). We always pull the entire parent directory, not just the file.
- ## Source Parsing Rules
- **Local paths** start with `/` or `~`:
- - Use the path directly. Copy the parent directory of the referenced file.
- **GitHub browser URLs** match `https://github.com/<org>/<repo>/blob/<branch>/<path>`:
- - Parse: `org`, `repo`, `branch`, `file_path`
- - Clone URL: `https://github.com/<org>/<repo>.git`
- - File location within repo: `<path>`
- **GitHub raw URLs** match `https://raw.githubusercontent.com/<org>/<repo>/<branch>/<path>`:
- - Parse: `org`, `repo`, `branch`, `file_path`
- - Clone URL: `https://github.com/<org>/<repo>.git`
- - File location within repo: `<path>`
- ## GitHub Workflow
- When working with GitHub sources, prefer `gh api` for accessing single files (e.g., reading a SKILL.md to check metadata). For pulling entire skill directories, clone into a temp dir per the steps below.
- **Fetching (use):**
- 1. Clone the repo with `git clone --depth 1 <clone_url>` into a temporary directory
- 2. Navigate to the parent directory of the referenced file
- 3. Copy that entire directory to the target local directory
- 4. The temporary directory is cleaned up automatically
- **Pushing (push):**
- 1. Clone the repo with `git clone --depth 1 <clone_url>` into a temporary directory
- 2. Overwrite the skill directory in the clone with the local version
- 3. Stage only the relevant changes: `git add <skill_directory_path>`
- 4. Commit with message: `library: updated <skill name> <what changed>`
- 5. Push to remote
- 6. The temporary directory is cleaned up automatically
- ## Typed Dependencies
- The `requires` field uses typed references to avoid ambiguity:
- - `skill:name` — references a skill in the library catalog
- - `agent:name` — references an agent in the library catalog
- - `prompt:name` — references a prompt in the library catalog
- When resolving dependencies: look up each reference in `library.yaml`, fetch all dependencies first (recursively), then fetch the requested item.
- ## Target Directories
- By default, items are installed to the **default** directory from `library.yaml`:
- ```yaml
- default_dirs:
- skills:
- - default: .claude/skills/
- - global: ~/.claude/skills/
- agents:
- - default: .claude/agents/
- - global: ~/.claude/agents/
- prompts:
- - default: .claude/commands/
- - global: ~/.claude/commands/
- ```
- - If the user says "global" or "globally", use the `global` directory.
- - If the user specifies a custom path, use that path.
- - Otherwise, use the `default` directory.
- ## Library Repo Sync
- The library skill itself lives in `<LIBRARY_SKILL_DIR>` as a cloned git repo. When running `add` (which modifies `library.yaml`), always:
- 1. `git pull` in the library directory first to get latest
- 2. Make the changes
- 3. `git add library.yaml && git commit && git push`
- This keeps the catalog in sync across devices.
- ## Example Filled Library File
- ```yaml
- default_dirs:
- skills:
- - default: .claude/skills/
- - global: ~/.claude/skills/
- agents:
- - default: .claude/agents/
- - global: ~/.claude/agents/
- prompts:
- - default: .claude/prompts/
- - global: ~/.claude/prompts/
- library:
- skills:
- - name: firecrawl
- description: Scrape, crawl, and search websites using Firecrawl CLI
- source: /Users/me/projects/tools/skills/firecrawl/SKILL.md
- - name: meta-skill
- description: Creates new Agent Skills following best practices
- source: /Users/me/projects/tools/skills/meta-skill/SKILL.md
- - name: diagram-kroki
- description: Generate diagrams via Kroki HTTP API supporting 28+ languages
- source: https://github.com/myorg/private-skills/blob/main/skills/diagram-kroki/SKILL.md
- requires: [skill:firecrawl]
- - name: green-screen-captions
- description: Generate and burn AI-powered captions onto green screen videos
- source: https://raw.githubusercontent.com/myorg/video-tools/main/skills/green-screen-captions/SKILL.md
- requires: [agent:video-processor, prompt:caption-style]
- agents:
- - name: video-processor
- description: Processes video files with ffmpeg and whisper transcription
- source: /Users/me/projects/tools/agents/video-processor/AGENT.md
- - name: code-reviewer
- description: Reviews code for quality, security, and performance
- source: https://github.com/myorg/agent-configs/blob/main/agents/code-reviewer/AGENT.md
- prompts:
- - name: caption-style
- description: Style guide for generating video captions
- source: /Users/me/projects/content/prompts/caption-style.md
- - name: commit-message
- description: Standardized commit message format for all projects
- source: https://github.com/myorg/team-prompts/blob/main/prompts/commit-message.md
- ```
README.md · README · 278 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- # The Library
- A meta-skill for private-first distribution of agentics (skills, agents, and prompts) across agents, devices, and teams.
- 
- ## Who This Is For
- If you're an engineer working on 10+ codebases with agents and you're building specialized private skills, agents, and prompts — this was made for you.
- If you work in one or two repos, you don't need this. If you install skills from the public internet without reviewing them, this isn't for you either.
- The Library solves a specific problem: you've built powerful agentics scattered across repos, devices, and teams. They're duplicated, out of sync, and hard to coordinate. This gives you a single reference catalog to distribute them privately.
- ## What It Is
- The Library is a single skill whose only job is to manage other skills. It's a catalog of references — local file paths and GitHub repo URLs — that point to where your agentics live. Nothing is copied or installed until you ask for it.
- Think of it as a `package.json` for agent capabilities — but instead of packages, you're managing skills, agents, and prompts. Instead of a registry, you're pointing at your own private GitHub repos and local paths.
- **This is a pure agent application.** There are no scripts, no CLIs, no dependencies, no build tools. The entire application is encoded in `SKILL.md` and a set of cookbook instructions that teach the agent exactly what to do. The agent IS the runtime. This matters because:
- - Any agent harness that reads skill files can run it (Claude Code, Pi, etc.)
- - You can modify behavior by editing markdown, not code
- - The skill can be extended, forked, and adapted instantly
- - An orchestrator agent can chain library commands without any tooling overhead
- ## Why It Exists
- 
- As you build with AI agents, you accumulate skills, custom agents, and prompts — potentially hundreds of them. You need to:
- - **Reuse** them across projects without copy-pasting
- - **Distribute** them to your agents running on other devices (Mac mini, remote servers, cloud sandboxes)
- - **Share** them with your team without making everything public
- - **Keep them private** — these are specialized capabilities built for competitive edge
- - **Stay in sync** — one source of truth, not 10 stale copies
- 
- Existing solutions don't fit:
- - **Global `~/.claude/*`** — exposes everything to every agent. Global is the opposite of specialized.
- - **Claude Code plugins** — requires marketplace infrastructure, manifests, and locks you into one platform.
- - **Single monorepo** — doesn't reflect reality. You build agentics in specific codebases for specific use cases.
- ## How It Works
- 
- ### The Catalog (`library.yaml`)
- ```yaml
- default_dirs:
- skills:
- - default: .claude/skills/
- - global: ~/.claude/skills/
- agents:
- - default: .claude/agents/
- - global: ~/.claude/agents/
- prompts:
- - default: .claude/commands/
- - global: ~/.claude/commands/
- library:
- skills:
- - name: my-skill
- description: What this skill does
- source: /Users/me/projects/tools/skills/my-skill/SKILL.md
- requires: [agent:helper-agent]
- - name: remote-skill
- description: A skill from a private repo
- source: https://github.com/myorg/private-skills/blob/main/skills/remote-skill/SKILL.md
- agents: []
- prompts: []
- ```
- The catalog stores pointers, not copies. Skills live in their source repos. You pull on demand.
- ### Source Formats
- | Format | Example |
- | ------------------ | ------------------------------------------------------------------ |
- | Local filesystem | `/absolute/path/to/SKILL.md` |
- | GitHub browser URL | `https://github.com/org/repo/blob/main/path/to/SKILL.md` |
- | GitHub raw URL | `https://raw.githubusercontent.com/org/repo/main/path/to/SKILL.md` |
- The source points to a specific file. The system pulls the entire parent directory (skills include scripts, references, assets — not just the markdown file).
- For private repos, authentication uses SSH keys or `GITHUB_TOKEN` automatically.
- ### Typed Dependencies
- Dependencies use typed references to avoid name collisions:
- ```yaml
- requires: [skill:base-utils, agent:reviewer, prompt:task-router]
- ```
- Dependencies are resolved and pulled first, recursively.
- ## Prerequisites
- - **Claude Code** (or a compatible agent harness that reads `.claude/skills/` — e.g., Pi)
- - **git** — for cloning sources and syncing the catalog
- - **gh** (optional) — GitHub CLI for forking, cloning, and private repo access. Install: `brew install gh` or see [gh docs](https://cli.github.com)
- - **GitHub SSH key or `GITHUB_TOKEN`** — for accessing private repos (not needed if using `gh auth login`)
- - **just** (optional) — for justfile shortcuts. Install: `brew install just` or see [just docs](https://github.com/casey/just)
- ## Installation
- This is a template repo. You fork it, clone it into your global skills directory, and it becomes a `/library` slash command available in every Claude Code session.
- ### 1. Fork This Repo
- Fork to your own GitHub account (private repo recommended). This fork is your personal library catalog — you'll push catalog updates to it.
- ```bash
- # Using GitHub CLI
- gh repo fork disler/the-library --private --clone=false
- ```
- Or fork manually via the GitHub UI.
- ### 2. Clone to Global Skills Directory
- Clone your fork into `~/.claude/skills/library`. This path is what makes `/library` available as a global slash command in Claude Code.
- ```bash
- # Using git
- mkdir -p ~/.claude/skills/library
- git clone <your-fork-url> ~/.claude/skills/library
- # Or using GitHub CLI
- gh repo clone <yourname>/the-library ~/.claude/skills/library
- ```
- ### 3. Configure
- Open `~/.claude/skills/library/SKILL.md` and update the `## Variables` section with your fork URL. The agent reads these variables at runtime to know where to sync the catalog.
- ```markdown
- # Before (template defaults)
- - **LIBRARY_REPO_URL**: `<your forked repo url>`
- # After (your values)
- - **LIBRARY_REPO_URL**: `https://github.com/yourname/the-library.git`
- ```
- The other two variables (`LIBRARY_YAML_PATH` and `LIBRARY_SKILL_DIR`) are correct by default if you cloned to `~/.claude/skills/library/`.
- ### 4. Verify
- Start a new Claude Code session anywhere. `/library list` should work and show an empty catalog.
- ## Quick Start
- 
- Here's the typical workflow: **build → catalog → distribute → use**.
- ### Add a skill to the catalog
- You built a deploy skill in one of your repos. Register it:
- ```
- /library add deploy skill from https://github.com/yourorg/infra-tools/blob/main/skills/deploy/SKILL.md
- ```
- This adds a reference to `library.yaml` and pushes the update to your fork.
- ### Use it in another project
- On another device, repo, or agent:
- ```
- /library use deploy
- ```
- This pulls the skill from the source repo into `.claude/skills/deploy/`.
- Want it globally available on this machine?
- ```
- /library use deploy install globally
- ```
- ### Push changes back
- You improved the skill locally. Push the update to the source repo:
- ```
- /library push deploy
- ```
- Now every device that runs `/library sync` gets the latest version.
- ### Sync everything
- Pull the latest version of all installed items:
- ```
- /library sync
- ```
- ## Commands
- | Command | What It Does |
- | --------------------------- | ---------------------------------------------------------- |
- | `/library install` | First-time setup — fork, clone, configure |
- | `/library add <details>` | Register a new entry in the catalog |
- | `/library use <name>` | Pull from source into local directory (install or refresh) |
- | `/library push <name>` | Push local changes back to the source |
- | `/library remove <name>` | Remove from catalog and optionally delete local copy |
- | `/library list` | Show full catalog with install status |
- | `/library sync` | Re-pull all installed items from source |
- | `/library search <keyword>` | Find entries by name or description |
- ### Justfile Shortcuts
- The included `justfile` lets you run library commands from your terminal without an interactive Claude session.
- ```bash
- just list # List catalog
- just use my-skill # Pull a skill
- just push my-skill # Push changes back
- just add "name: foo, description: bar, source: /path/to/SKILL.md"
- just sync # Re-pull all installed items
- just search "keyword"
- ```
- > **Note:** Justfile recipes use `--dangerously-skip-permissions` because the agent needs filesystem and git access to clone, copy, and push. Review the `justfile` if you want to modify this behavior.
- ## Architecture
- ```
- ~/.claude/skills/library/ # The Library skill (globally installed)
- SKILL.md # Agent instructions — the brain
- library.yaml # Your catalog of references
- cookbook/ # Step-by-step guides for each command
- install.md
- add.md
- use.md
- push.md
- remove.md
- list.md
- sync.md
- search.md
- justfile # CLI shorthand for all commands
- README.md # This file
- ```
- ## Design Principles
- - **Private-first**: Built for your specialized, competitive-edge agentics. Not a public marketplace.
- - **Reference-based**: The catalog stores pointers, not copies. Skills live in their source repos.
- - **Pure agent**: No scripts, no build tools. The SKILL.md teaches the agent everything it needs to know.
- - **Agent-agnostic**: Default target is `.claude/skills/` but supports any directory for any agent harness.
- - **Catalog, not manifest**: Entries define what's available, not what's installed. Pull on demand.
- ## The Agentic Stack
- 
- | Layer | Purpose |
- | --------------- | ---------------------------------------------- |
- | **Skills** | Raw capabilities — what an agent can do |
- | **Agents** | Scale + parallelism + specialization |
- | **Prompts** | Orchestration — coordinate skills and agents |
- | **Justfile** | Terminal access without an interactive session |
- | **The Library** | Distribution across devices, teams, and agents |
- ## Master Agentic Coding
- > Prepare for the future of software engineering
- Agentic Engineering is a NEW SKILL for software engineers. And soon it will be a required skill for software engineers. Master it before the masses with [Tactical Agentic Coding](https://agenticengineer.com/tactical-agentic-coding?y=tlibms)
- Follow the [IndyDevDan YouTube channel](https://www.youtube.com/@indydevdan) to improve your agentic coding advantage.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.