disler/the-library

Registry

Summary

The Library is a meta-skill for private-first distribution of agentics—skills, agents, and prompts—across your agents, devices, and teams. It enables secure, decentralized sharing of AI capabilities without compromising privacy.

Key features

• Private-first distribution of agentics
• Supports skills, agents, and prompts
• Cross-agent and cross-device sharing
• Team collaboration enabled
• Decentralized and secure

Use cases

• Share custom skills across your personal agents
• Distribute agent prompts securely within a team
• Sync agent configurations across multiple devices
• Collaborate on agent development without exposing data

README excerpt

# 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 ![The Problem:

Topics

No topics yet.