Copilot CLI: tiny additions to plugin docs (#59692)

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Author: hubwriter

content/copilot/how-tos/copilot-cli/customize-copilot/plugins-finding-installing.md

@@ -15,7 +15,7 @@ contentType: how-tos
 
 ## Introduction
 
-Plugins are packages that extend the functionality of {% data variables.copilot.copilot_cli_short %}. You can install a plugin from a marketplace that you have registered with the CLI, from a {% data variables.product.github %} repository, or from a local path.
+Plugins are packages that extend the functionality of {% data variables.copilot.copilot_cli_short %}. You can install a plugin from a marketplace that you have registered with the CLI, from a Git repository, or from a local path.
 
 For more information, see [AUTOTITLE](/copilot/concepts/agents/copilot-cli/about-cli-plugins).
 
@@ -49,12 +49,12 @@ To use the CLI to browse the plugins in one of your registered marketplaces:
 
    ```shell copy
    copilot plugin marketplace browse MARKETPLACE-NAME
-   
+
    ```
 
 ## Installing plugins
 
-Typically, you'll install a plugin from one of your registered marketplaces. However, you can also install a plugin directly from a {% data variables.product.github %} repository, or from a local path.
+Typically, you'll install a plugin from one of your registered marketplaces. However, you can also install a plugin directly from a Git repository, or from a local path.
 
 For information on how to register additional marketplaces, see [Adding and removing plugin marketplaces](#adding-and-removing-plugin-marketplaces).
 
@@ -76,20 +76,37 @@ Alternatively, in an interactive session, enter:
 /plugin install PLUGIN-NAME@MARKETPLACE-NAME
 ```
 
-### Install from {% data variables.product.github %} directly
+### Install directly from an online Git repository
+
+You can install a plugin directly from a repository, rather than doing so using a registered marketplace.
 
-You can install a plugin directly from a {% data variables.product.github %} repository, without first adding a marketplace to your list of registered marketplaces.
+To install a plugin directly from a repository **on {% data variables.product.prodname_dotcom_the_website %}**, enter:
 
 ```shell copy
-copilot plugin install OWNER/REPO:PATH/TO/PLUGIN
+copilot plugin install OWNER/REPO
+```
+
+To install a plugin from **any online Git repository**, enter:
+
+```shell copy
+copilot plugin install URL-OF-GIT-REPO
 ```
 
-For example,
+For example, `copilot plugin install https://gitlab.com/OWNER/REPO.git`.
+
+> [!IMPORTANT]
+> For these commands to work, the repository must contain a `plugin.json` file in a `.github/plugin` or `.claude-plugin` directory, or at the root of the repository.
+
+To install a plugin directly from a repository on {% data variables.product.prodname_dotcom_the_website %} where the `plugin.json` file is located somewhere other than `.github/plugin`, `.claude-plugin`, or the repository root—for example, if you are installing a plugin directly from a marketplace repository such as [anthropics/claude-code](https://github.com/anthropics/claude-code)—enter:
 
 ```shell copy
-copilot plugin install github/awesome-copilot:plugins/security-best-practices
+copilot plugin install OWNER/REPO:PATH/TO/PLUGIN
 ```
 
+Where `PATH/TO/PLUGIN` is the path from the root of the repository to a directory that contains `plugin.json`, `.github/plugin/plugin.json` or `.claude-plugin/plugin.json`.
+
+For example, `copilot plugin install anthropics/claude-code:plugins/frontend-design`
+
 ### Install from a local path
 
 ```shell copy
@@ -130,16 +147,16 @@ Alternatively, in an interactive session, enter:
 /plugin marketplace add OWNER/REPO
 ```
 
-If a marketplace is located on the local file system, instead of on {% data variables.product.github %}, use the path to the marketplace directory instead of OWNER/REPO. For example:
+If a marketplace is located on the local file system, instead of on {% data variables.product.prodname_dotcom_the_website %}, use the path to the marketplace directory instead of OWNER/REPO. For example:
 
 ```shell copy
 copilot plugin marketplace add /PATH/TO/MARKETPLACE-DIRECTORY
 ```
 
-If a marketplace is located in a Git repository that is not hosted on {% data variables.product.github %}, use the URL of the Git repository. For example:
+If a marketplace is located in a Git repository that is not hosted on {% data variables.product.prodname_dotcom_the_website %}, use the URL of the Git repository. For example:
 
 ```shell copy
-copilot plugin marketplace add https://gitlab.example.com/team/plugins.git
+copilot plugin marketplace add https://gitlab.com/OWNER/REPO.git
 ```
 
 ## Removing plugin marketplaces
@@ -157,7 +174,8 @@ Or, in an interactive session:
 ```
 
 > [!NOTE]
-> When adding a marketplace you reference the marketplace using the OWNER/REPO of the {% data variables.product.github %} repository that has been configured as a marketplace. When removing a marketplace, however, you reference the name of the marketplace as it appears in your list of registered marketplaces.
+> * When adding a marketplace you reference the marketplace using the OWNER/REPO of the {% data variables.product.github %} repository that has been configured as a marketplace. When removing a marketplace, however, you reference the name of the marketplace as it appears in your list of registered marketplaces.
+> * If you attempt to remove a marketplace that has plugins installed, the command will fail with an error message that lists the plugins that are currently installed from that marketplace. Add the `--force` option to the command to remove the marketplace and uninstall all plugins that were installed from that marketplace.
 
 ## Further reading
 

content/copilot/how-tos/copilot-cli/customize-copilot/quickstart-for-customizing.md

@@ -61,3 +61,5 @@ For more information, see [AUTOTITLE](/copilot/concepts/context/mcp).
 {% data variables.copilot.copilot_cli_short %} plugins are distributable packages that provide a simple way to extend the functionality of the CLI.
 
 They bundle multiple customization components together into a single installable unit. You can install plugins directly from a repository, from a plugin marketplace, or from a local path.
+
+For more information, see [AUTOTITLE](/copilot/concepts/agents/copilot-cli/about-cli-plugins).

content/copilot/reference/cli-plugin-reference.md

@@ -131,7 +131,7 @@ For more information, see [AUTOTITLE](/copilot/how-tos/copilot-cli/customize-cop
 | `hooks`       | string \| object   | No       | Path to hooks config or inline hooks object. |
 | `mcpServers`  | string \| object   | No       | Path to MCP config or inline server definitions. |
 | `lspServers`  | string \| object   | No       | Path to LSP config or inline server definitions. |
-| `strict`      | boolean            | No       | If false, plugin doesn't need its own `plugin.json`. Default: true. |
+| `strict`      | boolean            | No       | When `true` (the default), plugins must conform to the full schema and validation rules. When `false`, relaxed validation is used, allowing more flexibility—especially for direct installs or legacy plugins. |
 
 ## File locations