How do I install the Managing Library skill?

Run npx skillmds@latest add itaywol/managing-library in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Managing Library safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Managing Library?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Managing Library free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Managing Library?

itaywol (@itaywol) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Managing Library by itaywol — Agent Skill

Name: Managing Library
Author: itaywol

Managing Library

Maintain an adept skill library (repo from `adept init --as-library`): published vs private skills, add --publish, syncing dev helpers to your harness. Apply in a library-layout project or when `adept skill list` shows a published/private source.

itaywol 2ec335d 2.6 KB Updated Sep 17, 2026

File contents

Managing an adept library

A library is a repo created with adept init --as-library. It exists to publish skills to other repos. It has two skill locations — keep them straight:

location	source in `adept skill list`	published to consumers?	purpose
`skills/<id>/` (repo root)	`published`	yes	the library's product
`.adeptability/skills/<id>/`	`private`	no	dev-only helpers, rendered to your harness

config.json carries "layout": "library". Consumers add the repo with adept library add <name> --from <git-url> and only ever see the published skills/.

Adding skills

In a library, adept skill add defaults to private (it's the safe default — nothing is published by accident). Use --publish for skills that ship to consumers:

adept skill add my-helper            # → .adeptability/skills/my-helper/   (private, dev-only)
adept skill add pr-review --publish  # → skills/pr-review/                 (published)
adept skill list                     # SOURCE column shows published | private | library:<name>

edit and remove take a bare <id> and find it in either location (published wins on a name clash):

adept skill edit pr-review
adept skill remove my-helper

Rendering dev helpers to your own harness

Private skills render to your enabled harnesses so they assist you while you author the library, without shipping:

adept harness add claude-code        # once
adept sync                           # renders published + private → .claude/skills/, …
echo ".claude/" >> .gitignore        # rendered output is not source

adept init --as-library seeds this skill and the authoring helpers (using-adept, authoring-adept-skills) straight into .adeptability/skills/ for you.

Publishing

Commit and push. Only skills/ (published) reaches consumers; .adeptability/skills/ and the gitignored .claude/ stay local.

git add skills .adeptability && git commit -m "add <skill>" && git push

Rules of thumb:

Edit canonical (skills/<id>/SKILL.md or .adeptability/skills/<id>/SKILL.md), then adept sync. Never hand-edit rendered harness files — run adept sync-from to adopt those.
Run adept status / adept diff before and after a sync to see what changed.
adept --help and adept skill --help are the source of truth for flags.

---name: managing-librarydescription: Maintain an adept skill library (repo from `adept init --as-library`): published vs private skills, add --publish, syncing dev helpers to your harness. Apply in a library-layout project or when `adept skill list` shows a published/private source.---# Managing an adept libraryA **library** is a repo created with `adept init --as-library`. It exists to publish skillsto other repos. It has two skill locations — keep them straight:| location | source in `adept skill list` | published to consumers? | purpose ||---|---|---|---|| `skills/<id>/` (repo root) | `published` | **yes** | the library's product || `.adeptability/skills/<id>/` | `private` | **no** | dev-only helpers, rendered to your harness |`config.json` carries `"layout": "library"`. Consumers add the repo with`adept library add <name> --from <git-url>` and only ever see the **published** `skills/`.## Adding skillsIn a library, `adept skill add` defaults to **private** (it's the safe default — nothing ispublished by accident). Use `--publish` for skills that ship to consumers:```bashadept skill add my-helper # → .adeptability/skills/my-helper/ (private, dev-only)adept skill add pr-review --publish # → skills/pr-review/ (published)adept skill list # SOURCE column shows published | private | library:<name>````edit` and `remove` take a bare `<id>` and find it in either location (published wins on aname clash):```bashadept skill edit pr-reviewadept skill remove my-helper```## Rendering dev helpers to your own harnessPrivate skills render to your enabled harnesses so they assist you *while you author thelibrary*, without shipping:```bashadept harness add claude-code # onceadept sync # renders published + private → .claude/skills/, …echo ".claude/" >> .gitignore # rendered output is not source````adept init --as-library` seeds this skill and the authoring helpers (`using-adept`,`authoring-adept-skills`) straight into `.adeptability/skills/` for you.## PublishingCommit and push. Only `skills/` (published) reaches consumers; `.adeptability/skills/` and thegitignored `.claude/` stay local.```bashgit add skills .adeptability && git commit -m "add <skill>" && git push```Rules of thumb:- Edit canonical (`skills/<id>/SKILL.md` or `.adeptability/skills/<id>/SKILL.md`), then `adept sync`. Never hand-edit rendered harness files — run `adept sync-from` to adopt those.- Run `adept status` / `adept diff` before and after a sync to see what changed.- `adept --help` and `adept skill --help` are the source of truth for flags.

Frequently asked questions