Faye Plugin Market

Getting started

Help with installation

Find the cause of a setup problem and the next step to take.

Choose the symptom that matches your situation. These checks help diagnose a problem; you do not need to run them during a successful installation.

The terminal does not recognize the command

The application may be missing, unavailable in this terminal, or too old for plugin commands.

  1. Open a new terminal after installing the application.
  2. Check its version and plugin help against the official command reference.
  3. Do not paste interactive slash commands into the system terminal.

Expected resultThe application starts and its plugin commands or Plugins interface are available.

The Git repository cannot be added

The URL, network connection, or Git access may prevent fetching the marketplace.

  1. Compare the source with the repository address in your selected guide.
  2. Confirm access through your normal Git authentication flow; private repositories require access.
  3. Retry after resolving access. Do not disable certificate checks or paste a token into the guide.

Expected resultThe intended marketplace is listed without an access error.

The local folder is not recognized

Marketplace registration uses the repository root; direct plugin installation uses an individual plugin folder.

  1. For Codex or Grok registration, open the directory containing the marketplace registry and plugins folder.
  2. For Antigravity terminal installation, select plugins/<plugin-id> inside that checkout.
  3. Keep the existing checkout; do not delete it to retry registration.

Expected resultThe source is recognized and the desired packages are available.

The plugin is installed but its skills are missing

The session may predate installation, the plugin may be disabled, or a skill may require explicit invocation.

  1. Check the plugin's installed and enabled state.
  2. Start a fresh session and open the skill picker or the selected plugin's skill guide.
  3. Check invocation and tool requirements. Installation does not grant extra tools or permissions.

Expected resultApplicable skills can be discovered or explicitly invoked in the new session.

Grok does not show a newly installed skill

Grok Build

Discovery output can distinguish an unloaded package from a skill requiring an explicit request.

  1. Check the plugin is enabled in /plugins, then start a new session.
  2. Run the optional discovery command below and look for the selected plugin and its expected skill names.
  3. If the package is present but a skill is not offered automatically, read its invocation requirements.
Inspect skill discovery · PowerShell
grok inspect --json
Inspect skill discovery · Bash / zsh
grok inspect --json

Expected resultThe applicable skill names appear, or an explicit-invocation requirement explains the difference.

The same plugin is already installed

A matching installation can be reused; another source may create ambiguity.

  1. Compare the installed identity, source, and version with this guide.
  2. Reuse a matching installation.
  3. For another version or source, follow the product's update procedure after deciding which source to keep.

Expected resultThe intended source and version are identified without removing unrelated registrations.