How to consume the EOS plugin marketplace

Use APM to install EOS plugins with dependency resolution, security checks, and cross-runtime deployment. Install repository-independent skills globally by default so they remain available while working across repositories. Use a project installation when a repository or its CI pipeline depends on a plugin.

See the EOS marketplace skills reference for the available skills and their main use cases.

!IMPORTANT Do not use the native marketplace or plugin installer built into Claude Code, Cursor, Codex, or another runtime. Native installs do not create an APM lockfile, pin content hashes, resolve transitive dependencies, run APM's pre-install security scan, or support apm audit --ci drift detection. Use APM for both global and project installations.

Quickstart

1. Install APM

On macOS or Linux, run:

sh

curl -sSL https://aka.ms/apm-unix | sh

On Windows, run in PowerShell:

powershell

irm https://aka.ms/apm-windows | iex

Verify that APM is available:

sh

apm --version

See the official APM quickstart for alternative installation methods and troubleshooting.

2. Install and authenticate the GitHub CLI

APM resolves marketplace registrations through the GitHub CLI. Install gh following the official instructions and authenticate before registering any marketplace:

sh

gh auth login

Verify the session is active:

sh

gh auth status

If gh auth status reports no active account, apm marketplace add will fail with an authentication error.

3. Register EOS and install Ask EOS

Register the EOS marketplace and install its guided setup plugin globally:

sh

apm marketplace add tillotech/eos
apm install eos@eos --global

Restart the active AI program so it discovers the newly installed skill, then run:

text

/ask-eos

Ask EOS routes by goal. For install or discovery requests (including a bare /ask-eos), it asks about the user's role or goal, inventories installed EOS plugins and notable skills, avoids recommending skills that overlap the engineering plugin, reports whether Jira, GitHub CLI, and Notion are ready via their preferred MCP or CLI (and whether a compatible plugin, skill, or CLI alternative is present when the preferred tool needs setup), and offers to install each relevant missing plugin after explaining what it provides. For readiness-only requests, it runs the same environment research and reports gaps without installing unless the user opts into the install walkthrough.

After the plugins are installed, connect Notion, Atlassian, and the GitHub CLI with How to connect SDLC integrations. Then follow How to use the AI-enabled SDLC.

Register the marketplace

Register the EOS marketplace:

sh

apm marketplace add tillotech/eos

APM registers the marketplace as eos. Confirm the registration and inspect the available plugins:

sh

apm marketplace list
apm marketplace browse eos

Install repository-independent skills globally

Install reusable skills in the user scope so they are available across repositories:

sh

apm install engineering@eos --global

Repeat the command for each package needed, retaining the --global flag. APM stores user-scope dependencies and their lockfile under ~/.apm/, scans the packages, and deploys supported primitives to the configured agent runtimes.

Some runtimes only support a subset of APM primitives at user scope. Review any compatibility warning from APM; a warning about an unsupported primitive does not mean that the package's supported skills failed to install.

Install a repository dependency

Install without --global when a repository or its CI pipeline requires a specific EOS plugin:

sh

apm install engineering@eos

APM updates the project's apm.yml and resolves the dependency graph into apm.lock.yaml. Commit both files so contributors and CI install the same commits and content hashes:

sh

git add apm.yml apm.lock.yaml

Install in CI

Replay the committed lockfile without resolving newer package versions:

sh

apm install --frozen
apm audit --ci

Treat a lockfile mismatch or audit failure as a failed build. Do not regenerate the lockfile in CI.

Update global plugins

Refresh the marketplace and update user-scope dependencies:

sh

apm marketplace update eos
apm update --global
apm install --global

The update affects every repository that uses those global skills on the workstation.

Update project plugins

Refresh the marketplace cache, resolve newer matching plugin versions, and verify the result:

sh

apm marketplace update eos
apm update
apm install
apm audit

Review and commit the resulting apm.yml and apm.lock.yaml changes.

See APM's installing from marketplaces guide for the supported installation paths and the capabilities lost when using native runtime installers.