Publish an Anteroom pack to a Git repository after manifest validation.
npx skills add https://github.com/troylar/anteroom --skill pack-publish
Please help me install this Agent Skill. Skill: pack-publish Source: https://github.com/troylar/anteroom/tree/main/src/anteroom/cli/default_skills/pack-publish Command: npx skills add https://github.com/troylar/anteroom --skill pack-publish
This guide helps package authors publish an Anteroom pack to a Git repository so teammates can reliably discover and consume it, while preventing accidental broken releases or unsafe remote operations.
Validate the pack manifest, prepare or use a git repository, commit changes with user confirmation, and push to the chosen remote so teammates can add the repository to their pack_sources and refresh to install it.
High-intent search queries and answers about installing and using this skill.
To publish an Anteroom pack, you validate the pack manifest, initialize a git repository, stage and commit changes with explicit confirmation, and push to a remote URL so teammates can consume it.
Supported Git URL schemes for pushing a pack to a remote repository include standard formats such as https, git, ssh, or git@host:path to ensure safe remote operations.
Yes, manifest validation is required before creating a git commit or pushing to remotes, ensuring the Anteroom pack is well-formed and preventing accidental broken releases.
No, you cannot push pack updates without explicit user confirmation; the publishing workflow requires user approval before creating commits or pushing updates to remotes for safety.
Teammates install a published Anteroom pack by adding the Git repository URL to their pack_sources and refreshing to download the shared coding standards and prompt templates.
The git repository lifecycle for publishing a pack includes initializing the repository, adding a .gitignore file, creating commits, adding remotes, and pushing updates for team consumption.
MnkyArtsCreate and manage Hytale asset packs with pack.json manifests and standardized folders.
mikkerCache and refresh remote git repositories under ~/.cache/checkouts.
schpetRead and write semantic versions across JSON, TOML, and YAML config files.
jmaglyValidate AIWG YAML/JSON configuration files for syntax, schema, and references.
