Package Library

Browse and search all armory package types within an agent session. Install, update, sync and remove the seven legacy package types through their existing procedures; native extensions use the separate explicit per-host lifecycle.

Variables

• ARMORY_REPO: Mathews-Tom/armory
• ARMORY_BRANCH: main
• ARMORY_CATALOG_URL: https://raw.githubusercontent.com/{ARMORY_REPO}/{ARMORY_BRANCH}/manifest.yaml
• DEFAULT_INSTALL_DIR: ~/.claude/
• CATALOG_CACHE_PATH: /tmp/armory-manifest.yaml
• CATALOG_CACHE_TTL: 600 (seconds)

Supported Package Types

Command Reference

Cookbook Dispatch

User commands are routed to the corresponding cookbook file based on the subcommand. When a /library command is received, extract the subcommand (the first token after /library) and load the matching cookbook file from the cookbook/ directory relative to this skill. The cookbook file contains the full execution procedure for that operation.

For example, /library use commit-standards dispatches to cookbook/use.md with commit-standards as the package name argument. /library list --type agent dispatches to cookbook/list.md with --type agent as the filter.

If the subcommand does not match any known cookbook, report the error and list the valid subcommands from the table above.

Native Extension Boundary

This boundary takes precedence over the legacy cookbook procedures.

• Identify the type from the matching manifest section before inspecting an installed path or fetching package files. Catalog inspection may fetch the manifest; it must not fetch or copy a native extension payload.
• For native catalog queries, read packages.extensions and show catalog metadata. Do not derive native installed status from ~/.claude/skills/, the legacy plugin inventory or any other prompt-package directory; report that native installation status was not inspected.
• Refuse /library use, sync, update or remove filesystem operations on an extension. Never copy native artifacts into skills, agents or other legacy directories, never enable one implicitly, and never treat a profile or preset as native-install authority.
• After the user explicitly confirms the native host, lifecycle action and target root, hand off to uv run python scripts/install.py in an existing Armory checkout with every native flag explicit: --type extension --platform <omp|claude> --name <name> --action <install|update|disable|remove> --target-root <explicit-root> --yes. Never supply --yes before that confirmation. Do not select a host or persistent root on the user's behalf, or execute the handoff as part of a legacy library operation.
• Native entries remain discoverable in the catalog but never contribute to legacy profile membership or package counts. For bulk legacy operations, exclude packages.extensions before expanding the selection.

Type Detection

When /library use <name> is called, determine the package type by searching all sections of the manifest (packages.skills, packages.agents, packages.hooks, etc.). The first section containing a matching name entry determines the type. Use the type to:

1. Resolve the correct source path: {type_dir}/{name}/
2. Determine the install target: ~/.claude/{install_subdir}/
3. Choose the install method: directory copy or body-only extraction

Behavioral Notes

• All bash operations must use absolute paths. Never cd into temp dirs.
• Fetch uses a 3-tier fallback chain: sparse checkout, then gh api, then curl. Attempt each in order; proceed to the next only on failure.
• Cache lives in /tmp/ with a 10-minute TTL. A missing cache file is treated as expired (triggers a re-fetch), not as an error.
• The catalog is read from manifest.yaml on GitHub (at ARMORY_CATALOG_URL), not from a separate catalog file. This is the same manifest format used by the armory repository.
• All package type sections share the same entry format: name, version, description, path, source, plus optional tags, category, difficulty.