How do I install the Library skill?

Run npx skillmds@latest add vitoabella/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 Library safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: WARNING, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with 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 Library free to use?

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

Who published Library?

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

Library by vitoabella — Agent Skill

Name: Library
Rating: 4.2 (5 reviews)
Author: vitoabella

File contents

library

Run skillkit for every library change. Do not walk skill folders and do not open catalog/index.yaml. skillkit find prints a few paths and descriptions. Open a SKILL.md only after that command names it, or after the user names the skill.

The kit repo holds the files. IDE folders are junctions. Edit skills in the repo.

Find

skillkit find QUERY

Use the printed path. If there are no matches, say so and stop. Do not search the filesystem for another copy.

Add

Follow /create-skill when the user is authoring a new skill. That command writes into custom/ and leaves the skill unlinked.

Remove

skillkit remove NAME

This deletes the skill directory and drops its IDE links.

Move

skillkit move NAME --category CATEGORY
skillkit move NAME --category CATEGORY --root shared

--root changes which tree the skill lives in. Omit it to keep the current root. Category is the folder under that root, such as school or github.

Enable and disable

skillkit enable NAME manual
skillkit enable NAME auto
skillkit disable NAME

manual shows /NAME and sets disable-model-invocation: true.
auto shows /NAME and allows the IDE to select the skill from its description.
disable sets the skill back to library state. It stays on disk and disappears from the slash menu.

New skills stay in library state until the user asks to enable them.

Install

skillkit install --workspace PATH

Links every manual and auto skill into that project's .claude/skills and .agents/skills. The path is stored in skills.config.local.yaml. Later installs can omit --workspace. Do not point --workspace at the kit repo.

User scope is settings.scope: user in skills.config.yaml. Install then links ~/.claude/skills, ~/.gemini/config/skills, and ~/.copilot/skills.

Reset

skillkit reset

Copies defaults onto settings and relinks. It does not change skills.config.local.yaml or files under custom/.

Config

Edit settings in skills.config.yaml, or let these commands write that block. Leave defaults as the reset baseline. Machine-specific keys (workspace, and roots including custom) belong in skills.config.local.yaml.

---name: librarydescription: Search and maintain the skill library. Use when the user wants to find a skill, add or remove one, move it to another category, enable or disable it, install links into a workspace, or reset settings.---# libraryRun `skillkit` for every library change. Do not walk skill folders and do not open `catalog/index.yaml`. `skillkit find` prints a few paths and descriptions. Open a `SKILL.md` only after that command names it, or after the user names the skill.The kit repo holds the files. IDE folders are junctions. Edit skills in the repo.## Find```textskillkit find QUERY```Use the printed path. If there are no matches, say so and stop. Do not search the filesystem for another copy.## AddFollow `/create-skill` when the user is authoring a new skill. That command writes into `custom/` and leaves the skill unlinked.## Remove```textskillkit remove NAME```This deletes the skill directory and drops its IDE links.## Move```textskillkit move NAME --category CATEGORYskillkit move NAME --category CATEGORY --root shared````--root` changes which tree the skill lives in. Omit it to keep the current root. Category is the folder under that root, such as `school` or `github`.## Enable and disable```textskillkit enable NAME manualskillkit enable NAME autoskillkit disable NAME```- `manual` shows `/NAME` and sets `disable-model-invocation: true`.- `auto` shows `/NAME` and allows the IDE to select the skill from its description.- `disable` sets the skill back to library state. It stays on disk and disappears from the slash menu.New skills stay in library state until the user asks to enable them.## Install```textskillkit install --workspace PATH```Links every manual and auto skill into that project's `.claude/skills` and `.agents/skills`. The path is stored in `skills.config.local.yaml`. Later installs can omit `--workspace`. Do not point `--workspace` at the kit repo.User scope is `settings.scope: user` in `skills.config.yaml`. Install then links `~/.claude/skills`, `~/.gemini/config/skills`, and `~/.copilot/skills`.## Reset```textskillkit reset```Copies `defaults` onto `settings` and relinks. It does not change `skills.config.local.yaml` or files under `custom/`.## ConfigEdit `settings` in `skills.config.yaml`, or let these commands write that block. Leave `defaults` as the reset baseline. Machine-specific keys (`workspace`, and `roots` including `custom`) belong in `skills.config.local.yaml`.

Frequently asked questions

Library