06-reference

indydevdan library meta skill

Sun Apr 19 2026 20:00:00 GMT-0400 (Eastern Daylight Time) ·reference ·source: IndyDevDan YouTube ·by IndyDevDan
indy-dev-danlibrary-meta-skillagentic-distributionprivate-skill-librarymulti-device-agentsmulti-team-agentspackage-manager-for-promptssingle-source-of-truthbuild-catalog-distribute-usepure-agentic-applicationmeta-agenticsorchestrator-agentharness-engineering

IndyDevDan — The Library Meta-Skill: How I Distribute PRIVATE Skills, Agents and Prompts

Why this is in the vault

26-minute Dan walkthrough of the library meta-skill — a SKILL.md + YAML reference file + cookbook of agent-executed commands (/library add, /library use, /library push, /library list, /library search, /library sync) that turns a developer’s collection of private skills/agents/prompts (“agentics”) into a synced library across devices, team members, and agents. The vault keeps it for three reasons. (1) It is the missing distribution layer for RDCO’s own ~/.claude/skills/ ecology — Ray currently has 50+ skills on the Mac Mini, no equivalent on Ben’s MacBook, and no clean way to share or sync between them; this video describes the exact pattern Ray should adopt. (2) It is a load-bearing example of pure-agentic applications — no compiled code, no CLI binary, just SKILL.md + YAML + agent reasoning. Dan’s prediction (“we’re going to see a lot of pure agentic solutions as we move through this year”) is materially relevant to skill-design decisions in 2026 — the bar for “this should be a Python script” vs “this should be a SKILL.md” is shifting. (3) It strengthens CA-013 (R&D framework: Reduce and Delegate) with a concrete reduce-the-CLAUDE.md-load mechanism — references over copies = less context bloat per device — and adds an operational answer for the multi-device synchronization sub-problem that’s been latent in RDCO’s channels-agent stack since the Mac Mini was provisioned.

Core argument

  1. The problem is structural, not annoying. When you operate across 10+ codebases × multiple agents × multiple team members, copy-pasting skills between repositories is technical debt that compounds invisibly. Skills go out of sync, duplicates accumulate, and there’s no shared truth.
  2. Solution: a meta-skill that references rather than copies. The library skill stores pointers (private GitHub URLs, public repos, local file paths) in a single YAML file — never the skill content itself. Like package.json or pyproject.toml for prompts/agents/skills.
  3. Three primitives, not one. Skills (raw capabilities) ≠ Agents (scale and parallelism) ≠ Prompts (single-file orchestration). Most engineers conflate them and “overkill skills doing everything inside the skill.” Dan’s distribution surface treats all three as first-class citizens.
  4. The four-stage workflow: Build → Catalog → Distribute → Use. Build natively in your value-generating repo; catalog with /library add; distribute via git/sync; use via /library use <name> install [locally|globally].
  5. Pure-agentic application. The library skill has zero compiled code. SKILL.md describes intent; library.yaml stores references; the cookbook directory contains markdown for each command (one .md per workflow). The agent reads these and executes git operations directly. “There is no code associated with this… that gives us a lot of very powerful capabilities.”
  6. Privacy-first. “Your top-notch skills, agents, and prompts should absolutely be private. I know a lot of vibe coders, you think that everything is just out there in the public. Trust me, it’s not.” The library is designed for private GitHub distribution as the default; public repos are an exception, not the rule.
  7. Local + global namespacing per consumer device. Same library can install items into <repo>/.claude/skills/ (project-scoped) OR ~/.claude/skills/ (global). The consuming agent decides scope per /library use invocation, NOT the library itself. Some skills want to be global on all devices (meta-agentics); others belong only in the project that needs them.
  8. Push-back-to-source is a first-class command. /library push <name> finds local edits and commits them back to the referenced repo. Bidirectional sync, not just one-way distribution. This is what makes the library a working source of truth, not just a deployment surface.
  9. Trust scaling is the 2026 theme. “The best way to increase trust is to know exactly what they’re doing and know exactly what they’re running. And that means down to the lines inside of your skills, your prompts, and your agents.” The library forces every shared piece through a private-controlled distribution surface — no cloud code plugins, install from wherever for production work.
  10. Orchestrator agents need this. As the agentic path scales (base → better → more → custom → orchestrator), the orchestrator can’t operate effectively without a single coherent capability surface across devices and team members. The library is the prerequisite for serious orchestrator work.

Notable details

Mapping against Ray Data Co

Open follow-ups

Sponsorship

The video has no paid placement. Dan’s standard close (“you know where to find me every single Monday — stay focused and keep building”) is brand-building, not sponsorship. The video does promote Dan’s own GitHub template (disler/the-library) and his previously-released PI coding agent video, but these are self-references to his own ecosystem, not paid advertising.