Package Library

Agent-native catalog and installer for all armory package types. Provides browsing, searching, installing, updating, syncing, and removing packages directly within an agent session.

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.

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.