@modootoday/pmcp 0.13.1 → 0.14.0

package/plugins/yargs-18/skills/yargs/SKILL.md

@@ -0,0 +1,175 @@
+---
+name: yargs
+description: Use yargs ^18.0.0 as a factory-based argument parser in supported Node runtimes.
+---
+
+Verified against yargs@18.1.0 on 2026-09-08. 7 of 7 examples executed.
+
+# yargs ^18
+
+## Runtime and version constraints
+
+`^18.0.0` stays within major version 18. Version 18 requires Node `^20.19.0 || ^22.12.0 || >=23`.
+
+Version 18 removed the singleton API. Do not use older examples such as `yargs.foo` or `yargs().argv`. Create a parser with the default factory export and explicitly call `.parse()`, `.parseSync()`, or `.parseAsync()`.
+
+```ts pmcp-example
+import assert from 'node:assert/strict'
+import yargs from 'yargs'
+
+const argv = yargs(['--name', 'Ada', 'file.txt']).parse()
+
+assert.equal(argv.name, 'Ada')
+assert.deepEqual(argv._, ['file.txt'])
+```
+
+The input array represents arguments after the program name. The factory also accepts `process.argv.slice(2)` directly.
+
+## Normal process-argument parsing
+
+Use `hideBin` when parsing the current process arguments. It is shorthand for `process.argv.slice(2)`.
+
+```ts pmcp-example
+import assert from 'node:assert/strict'
+import yargs from 'yargs'
+import { hideBin } from 'yargs/helpers'
+
+const argv = yargs(hideBin(['node', 'example.ts', '--count', '3', 'input.txt'])).parse()
+
+assert.equal(argv.count, 3)
+assert.deepEqual(argv._, ['input.txt'])
+```
+
+For a plain script, passing an explicit array is usually easier to test. The `hideBin` helper is exported from `yargs/helpers`, not from the main package entry.
+
+## Options and aliases
+
+Register options with `.option(key, configuration)`. The documented configuration supports fields such as `alias`, `describe`, and `choices`. The convenience methods `.alias()`, `.choices()`, and `.demandOption()` are also available.
+
+```ts pmcp-example
+import assert from 'node:assert/strict'
+import yargs from 'yargs'
+
+const argv = yargs(['-s', 'm', '--format', 'json'])
+  .option('size', {
+    alias: 's',
+    describe: 'choose a size',
+    choices: ['xs', 's', 'm', 'l', 'xl']
+  })
+  .option('format', { choices: ['json', 'text'] })
+  .demandOption('format')
+  .parse()
+
+assert.equal(argv.size, 'm')
+assert.equal(argv.s, 'm')
+assert.equal(argv.format, 'json')
+```
+
+The equivalent convenience methods can be used when the option has already been declared:
+
+```ts pmcp-example
+import assert from 'node:assert/strict'
+import yargs from 'yargs'
+
+const argv = yargs(['--mode', 'fast'])
+  .option('mode')
+  .alias('mode', 'm')
+  .choices('mode', ['fast', 'safe'])
+  .parse()
+
+assert.equal(argv.mode, 'fast')
+```
+
+`.demandOption(key)` makes the option required. Invalid choices or missing demanded options are validation failures handled by yargs; do not expect them to produce a normal parsed result.
+
+## Commands
+
+Register commands with `.command(cmd, desc, builder, handler)`. A builder configures the command parser and the handler receives the parsed command arguments.
+
+```ts pmcp-example
+import assert from 'node:assert/strict'
+import yargs from 'yargs'
+
+let received: { url?: string; _: unknown[] } | undefined
+
+const result = yargs(['get', '--url', 'https://example.test'])
+  .command(
+    'get',
+    'make a get request',
+    (command) => command.option('url', {
+      alias: 'u',
+      describe: 'URL to request'
+    }),
+    (argv) => {
+      received = { url: argv.url, _: argv._ }
+    }
+  )
+  .parse()
+
+assert.equal(received?.url, 'https://example.test')
+assert.deepEqual(received?._, ['get'])
+assert.equal(result.url, 'https://example.test')
+```
+
+In v18, command names are no longer derived from modules passed to `.command`; register the command explicitly. Do not call `.parse()` inside a command builder. Parse once at the application level.
+
+Command modules are not standalone parsers. A module registered with `.command()` must expose command-module fields such as `command`, `aliases`, `describe`, `builder`, and `handler`.
+
+`commandDir()` loads command modules from the filesystem. It depends on filesystem/module loading and does not work with Deno. For Deno, import command modules explicitly and pass an array to `.command()` instead.
+
+## Help, version, strictness, and wrapping
+
+The parser exposes `.help([option|boolean])`, `.version([version|boolean])`, `.strict([enabled=true])`, and `.wrap(columns)`.
+
+```ts pmcp-example
+import assert from 'node:assert/strict'
+import yargs from 'yargs'
+
+const parser = yargs(['--name', 'Ada'])
+  .option('name', { type: 'string' })
+  .help('help')
+  .version('1.2.3')
+  .strict()
+  .wrap(80)
+
+const argv = parser.parse()
+assert.equal(argv.name, 'Ada')
+```
+
+`strict()` enables failure for unknown arguments. Use `.wrap(columns)` to set help wrapping. In v18, `wrap(null)` has changed behavior; avoid assuming older-major behavior when migrating.
+
+Help and version flags are CLI output paths: invoke them through the yargs application when the process should display help or version information, rather than treating them as ordinary parsed values.
+
+## Async parsing
+
+Use `.parseAsync()` whenever a builder, handler, middleware, or coercion is asynchronous. It always returns a promise. `.parseSync()` throws if asynchronous work is involved.
+
+```ts pmcp-example
+import assert from 'node:assert/strict'
+import yargs from 'yargs'
+
+const argv = await yargs(['--value', 'ada'])
+  .option('value', { type: 'string' })
+  .coerce('value', async (value) => value.toUpperCase())
+  .parseAsync()
+
+assert.equal(argv.value, 'ADA')
+```
+
+Use `.parseSync()` only for configurations that contain no async builder, handler, or middleware. `.parse()` is the synchronous top-level entry point.
+
+## Migration checklist
+
+- Replace singleton chains with `yargs(args).parse()`.
+- Replace `yargs().argv` with an explicit parse call.
+- Pass arguments after the program name; use `hideBin(process.argv)` for real process arguments.
+- Register command names explicitly instead of relying on module-derived names.
+- Do not parse inside command builders.
+- Use `.parseAsync()` for asynchronous behavior.
+- Account for v18 strict-mode behavior: unknown arguments fail when strict mode is enabled.
+- Do not rely on the old behavior where positionals overwrite options.
+- `implies` accepts implied values `0`, `false`, and `''` in v18.
+
+## Not covered
+
+This skill does not cover the complete yargs API, detailed validation/error-output customization, middleware, positional-builder syntax beyond the command surface shown here, command-module packaging, filesystem discovery implementation, Deno-specific package URLs, browser bundling, or the behavior of the standalone CLI/tool in a configured application. Those areas require the package's own runtime or additional documentation beyond the researched surface.

package/plugins/yargs-parser-22/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "yargs-parser-22",
+  "version": "22.0.0",
+  "description": "Use yargs-parser v22 as a standalone ESM-first argument parser, including its callable parser, detailed results, helper methods, and documented parsing options.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/yargs-parser-22/LICENSE

@@ -0,0 +1,93 @@
+Elastic License 2.0
+
+URL: https://www.elastic.co/licensing/elastic-license
+
+## Acceptance
+
+By using the software, you agree to all of the terms and conditions below.
+
+## Copyright License
+
+The licensor grants you a non-exclusive, royalty-free, worldwide,
+non-sublicensable, non-transferable license to use, copy, distribute, make
+available, and prepare derivative works of the software, in each case subject to
+the limitations and conditions below.
+
+## Limitations
+
+You may not provide the software to third parties as a hosted or managed
+service, where the service provides users with access to any substantial set of
+the features or functionality of the software.
+
+You may not move, change, disable, or circumvent the license key functionality
+in the software, and you may not remove or obscure any functionality in the
+software that is protected by the license key.
+
+You may not alter, remove, or obscure any licensing, copyright, or other notices
+of the licensor in the software. Any use of the licensor’s trademarks is subject
+to applicable law.
+
+## Patents
+
+The licensor grants you a license, under any patent claims the licensor can
+license, or becomes able to license, to make, have made, use, sell, offer for
+sale, import and have imported the software, in each case subject to the
+limitations and conditions in this license. This license does not cover any
+patent claims that you cause to be infringed by modifications or additions to
+the software. If you or your company make any written claim that the software
+infringes or contributes to infringement of any patent, your patent license for
+the software granted under these terms ends immediately. If your company makes
+such a claim, your patent license ends immediately for work on behalf of your
+company.
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of the software from you
+also gets a copy of these terms.
+
+If you modify the software, you must include in any modified copies of the
+software prominent notices stating that you have modified the software.
+
+## No Other Rights
+
+These terms do not imply any licenses other than those expressly granted in
+these terms.
+
+## Termination
+
+If you use the software in violation of these terms, such use is not licensed,
+and your licenses will automatically terminate. If the licensor provides you
+with a notice of your violation, and you cease all violation of this license no
+later than 30 days after you receive that notice, your licenses will be
+reinstated retroactively. However, if you violate these terms after such
+reinstatement, any additional violation of these terms will cause your licenses
+to terminate automatically and permanently.
+
+## No Liability
+
+*As far as the law allows, the software comes as is, without any warranty or
+condition, and the licensor will not be liable to you for any damages arising
+out of these terms or the use or nature of the software, under any kind of
+legal claim.*
+
+## Definitions
+
+The **licensor** is the entity offering these terms, and the **software** is the
+software the licensor makes available under these terms, including any portion
+of it.
+
+**you** refers to the individual or entity agreeing to these terms.
+
+**your company** is any legal entity, sole proprietorship, or other kind of
+organization that you work for, plus all organizations that have control over,
+are under the control of, or are under common control with that
+organization. **control** means ownership of substantially all the assets of an
+entity, or the power to direct its management and policies by vote, contract, or
+otherwise. Control can be direct or indirect.
+
+**your licenses** are all the licenses granted to you for the software under
+these terms.
+
+**use** means anything you do with the software requiring one of your licenses.
+
+**trademark** means trademarks, service marks, and similar rights.

package/plugins/yargs-parser-22/NOTICE

@@ -0,0 +1,51 @@
+pmcp
+
+Copyright (c) 2026 modootoday. All rights reserved.
+
+Licensor: modootoday
+Licensed under the Elastic License 2.0; see LICENSE.
+
+The licensor is modootoday, the company, not any individual contributor. This
+file names the licensor because the Elastic License 2.0 defines that term rather
+than carrying a copyright line of its own; LICENSE is kept unmodified.
+
+What the licence permits, in short, without replacing the terms in LICENSE:
+
+  - Using this software inside your own company, on any scale.
+  - Embedding it in a product you sell, and modifying or forking it.
+  - Redistributing it, with these notices intact.
+  - Running it locally as an MCP server, which is what it is for. A host
+    process spawning it on your own machine is use, not a hosted service.
+
+What it does not permit:
+
+  - Offering this software to third parties as a hosted or managed service.
+    A remotely hosted MCP endpoint serving other people is the case this
+    forbids.
+  - Circumventing licence key functionality.
+  - Removing or obscuring these notices.
+
+The Elastic License 2.0 is source-available, not an OSI-approved open source
+licence. It grants a patent licence and ends that licence if you assert a patent
+claim against the software; see the Patents section of LICENSE.
+
+LICENSE governs. Where this summary and LICENSE differ, LICENSE is what applies.
+
+---
+
+This software depends on the following packages, which are distributed under
+their own terms and are not covered by the licence above.
+
+  @modelcontextprotocol/server   MIT   Copyright (c) Anthropic, PBC
+  @modelcontextprotocol/core     MIT   Copyright (c) Anthropic, PBC
+  zod                            MIT   Copyright (c) Colin McDonnell
+  semver                         ISC   See the dependency's LICENSE file.
+  smol-toml              BSD-3-Clause   Copyright (c) Squirrel Chat et al.
+  yaml                           ISC   Copyright Eemeli Aro
+
+Full licence texts and copyright notices ship with those packages. Their
+respective licence terms govern distribution of those dependencies.
+
+@huggingface/transformers is an optional peer dependency. It is never
+distributed with this package; a user who wants semantic ranking installs it
+themselves, under its own Apache-2.0 terms.

package/plugins/yargs-parser-22/gemini-extension.json

@@ -0,0 +1 @@
+{ "name": "yargs-parser-22", "version": "22.0.0" }

package/plugins/yargs-parser-22/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "yargs-parser-22",
+  "version": "22.0.0",
+  "description": "Use yargs-parser v22 as a standalone ESM-first argument parser, including its callable parser, detailed results, helper methods, and documented parsing options.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/yargs-parser-22/skills/yargs-parser/SKILL.md

@@ -0,0 +1,179 @@
+---
+name: yargs-parser
+description: Use yargs-parser v22 as a standalone ESM-first argument parser, including its callable parser, detailed results, helper methods, and documented parsing options.
+---
+
+Verified against yargs-parser@22.0.0 on 2026-09-08. 8 of 8 examples executed.
+
+# yargs-parser v22
+
+## Import and runtime
+
+`yargs-parser` v22 is ESM-first. In an ESM script, use its default export:
+
+```ts
+import parser from 'yargs-parser'
+```
+
+The package metadata declares `type: "module"` and supports Node `^20.19.0 || ^22.12.0 || >=23`. The callable default export accepts either a command-line string or an array and returns parsed values, including `_` for positional arguments.
+
+Older examples commonly use `require('yargs-parser')`. Do not copy that shape into an ESM-first v22 application without checking the module environment. The documented v22 import is the default ESM import above.
+
+## Basic parsing
+
+Pass a string or an array of argument strings. Long options support `--name=value` and separated values. Positional arguments are returned in `_`.
+
+```ts pmcp-example
+import assert from 'node:assert/strict'
+import parser from 'yargs-parser'
+
+const argv = parser('--foo=99 --bar=9987930 positional', {
+  string: ['bar']
+})
+
+assert.equal(argv.foo, 99)
+assert.equal(argv.bar, '9987930')
+assert.deepEqual(argv._, ['positional'])
+```
+
+When the caller already has an argument vector, pass the array directly rather than joining it into a string:
+
+```ts pmcp-example
+import assert from 'node:assert/strict'
+import parser from 'yargs-parser'
+
+const argv = parser(['--name', 'Ada', 'file.txt'], {
+  string: ['name']
+})
+
+assert.equal(argv.name, 'Ada')
+assert.deepEqual(argv._, ['file.txt'])
+```
+
+## Typed and repeated options
+
+The documented option groups include `string`, `number`, `boolean`, `array`, `count`, `default`, `narg`, `coerce`, `config`, `configObjects`, `configuration`, `envPrefix`, and `normalize`.
+
+Use `string` when a value must not be converted to a number. Use `number` when a numeric option should be treated as numeric. `array` collects repeated values, while `count` increments each time the flag occurs.
+
+```ts pmcp-example
+import assert from 'node:assert/strict'
+import parser from 'yargs-parser'
+
+const argv = parser([
+  '--tag', 'one',
+  '--tag', 'two',
+  '--verbose',
+  '--verbose',
+  '--port', '8080'
+], {
+  array: ['tag'],
+  boolean: ['verbose'],
+  count: ['verbose'],
+  number: ['port']
+})
+
+assert.deepEqual(argv.tag, ['one', 'two'])
+assert.equal(argv.verbose, 2)
+assert.equal(argv.port, 8080)
+```
+
+Defaults and coercion are parser options, not post-processing requirements:
+
+```ts pmcp-example
+import assert from 'node:assert/strict'
+import parser from 'yargs-parser'
+
+const argv = parser('--user ada', {
+  string: ['user', 'mode'],
+  default: { mode: 'safe' },
+  coerce: {
+    user: (value: string) => value.toUpperCase()
+  }
+})
+
+assert.equal(argv.user, 'ADA')
+assert.equal(argv.mode, 'safe')
+```
+
+`narg` declares how many arguments an option consumes. Keep the declaration consistent with the input shape; it is not equivalent to declaring an option as an array.
+
+## Detailed parsing
+
+`parser.detailed(args, opts)` returns more than the final argument object. Its result contains `argv`, `error`, `aliases`, `newAliases`, `defaulted`, and `configuration`.
+
+```ts pmcp-example
+import assert from 'node:assert/strict'
+import parser from 'yargs-parser'
+
+const result = parser.detailed('--foo=99', {
+  alias: { foo: ['f'] }
+})
+
+assert.equal(result.error, null)
+assert.equal(result.argv.foo, 99)
+assert.equal(result.argv.f, 99)
+assert.ok(result.aliases)
+assert.ok(result.newAliases)
+assert.ok(result.defaulted)
+assert.ok(result.configuration)
+```
+
+Use the detailed form when the caller needs to distinguish parser metadata, aliases, defaults, configuration, or an error from the final `argv` object. Use the callable form when only parsed arguments are needed.
+
+## Helper exports
+
+The default parser function exposes these helpers:
+
+- `parser.camelCase(str)`
+- `parser.decamelize(str, joinString?)`
+- `parser.looksLikeNumber(value)`
+
+```ts pmcp-example
+import assert from 'node:assert/strict'
+import parser from 'yargs-parser'
+
+assert.equal(parser.camelCase('foo-bar'), 'fooBar')
+assert.equal(parser.decamelize('fooBar'), 'foo-bar')
+assert.equal(parser.looksLikeNumber('99.3'), true)
+assert.equal(parser.looksLikeNumber('not-a-number'), false)
+```
+
+## Environment and configuration-related options
+
+`envPrefix` reads matching prefixed environment variables. Set the environment in the process before parsing if a standalone script needs to exercise this behavior:
+
+```ts pmcp-example
+import assert from 'node:assert/strict'
+import parser from 'yargs-parser'
+
+process.env.DEMO_PORT = '4321'
+const argv = parser('', { envPrefix: 'DEMO' })
+
+assert.equal(argv.port, 4321)
+```
+
+`configObjects` accepts configuration objects directly and is suitable when configuration is already available in memory:
+
+```ts pmcp-example
+import assert from 'node:assert/strict'
+import parser from 'yargs-parser'
+
+const argv = parser('--cli yes', {
+  string: ['cli', 'fromConfig'],
+  configObjects: [{ fromConfig: 'memory' }]
+})
+
+assert.equal(argv.cli, 'yes')
+assert.equal(argv.fromConfig, 'memory')
+```
+
+`config` loads a configuration-file path, and `normalize` uses `path.normalize()`. These options depend on Node-specific environment or filesystem behavior and are not demonstrated in the standalone examples here.
+
+## `--` values and configuration
+
+The parser can optionally retain values after `--`, depending on the `configuration` options. Treat this as an explicit parser configuration rather than assuming every invocation exposes a `--` property. The returned object may contain the optional `--` values in addition to `_` and named options.
+
+## What this skill does not cover
+
+This skill does not cover yargs itself, command registration, `describe`/`it`/`expect`, CLI runner behavior, browser or Deno entrypoints, the exact filesystem format consumed by `config`, or platform-specific results of `normalize`. It also does not cover options or behaviors not supported by the supplied v22 research.

package/plugins/yeoman-environment-7/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "yeoman-environment-7",
+  "version": "7.0.0",
+  "description": "Use yeoman-environment's ESM environment API when working against the v7.0.0 source shape. Note that ^7.0.0 is not a published version according to the researched npm metadata; verify the installed version before relying on this skill.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/yeoman-environment-7/LICENSE

@@ -0,0 +1,93 @@
+Elastic License 2.0
+
+URL: https://www.elastic.co/licensing/elastic-license
+
+## Acceptance
+
+By using the software, you agree to all of the terms and conditions below.
+
+## Copyright License
+
+The licensor grants you a non-exclusive, royalty-free, worldwide,
+non-sublicensable, non-transferable license to use, copy, distribute, make
+available, and prepare derivative works of the software, in each case subject to
+the limitations and conditions below.
+
+## Limitations
+
+You may not provide the software to third parties as a hosted or managed
+service, where the service provides users with access to any substantial set of
+the features or functionality of the software.
+
+You may not move, change, disable, or circumvent the license key functionality
+in the software, and you may not remove or obscure any functionality in the
+software that is protected by the license key.
+
+You may not alter, remove, or obscure any licensing, copyright, or other notices
+of the licensor in the software. Any use of the licensor’s trademarks is subject
+to applicable law.
+
+## Patents
+
+The licensor grants you a license, under any patent claims the licensor can
+license, or becomes able to license, to make, have made, use, sell, offer for
+sale, import and have imported the software, in each case subject to the
+limitations and conditions in this license. This license does not cover any
+patent claims that you cause to be infringed by modifications or additions to
+the software. If you or your company make any written claim that the software
+infringes or contributes to infringement of any patent, your patent license for
+the software granted under these terms ends immediately. If your company makes
+such a claim, your patent license ends immediately for work on behalf of your
+company.
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of the software from you
+also gets a copy of these terms.
+
+If you modify the software, you must include in any modified copies of the
+software prominent notices stating that you have modified the software.
+
+## No Other Rights
+
+These terms do not imply any licenses other than those expressly granted in
+these terms.
+
+## Termination
+
+If you use the software in violation of these terms, such use is not licensed,
+and your licenses will automatically terminate. If the licensor provides you
+with a notice of your violation, and you cease all violation of this license no
+later than 30 days after you receive that notice, your licenses will be
+reinstated retroactively. However, if you violate these terms after such
+reinstatement, any additional violation of these terms will cause your licenses
+to terminate automatically and permanently.
+
+## No Liability
+
+*As far as the law allows, the software comes as is, without any warranty or
+condition, and the licensor will not be liable to you for any damages arising
+out of these terms or the use or nature of the software, under any kind of
+legal claim.*
+
+## Definitions
+
+The **licensor** is the entity offering these terms, and the **software** is the
+software the licensor makes available under these terms, including any portion
+of it.
+
+**you** refers to the individual or entity agreeing to these terms.
+
+**your company** is any legal entity, sole proprietorship, or other kind of
+organization that you work for, plus all organizations that have control over,
+are under the control of, or are under common control with that
+organization. **control** means ownership of substantially all the assets of an
+entity, or the power to direct its management and policies by vote, contract, or
+otherwise. Control can be direct or indirect.
+
+**your licenses** are all the licenses granted to you for the software under
+these terms.
+
+**use** means anything you do with the software requiring one of your licenses.
+
+**trademark** means trademarks, service marks, and similar rights.

package/plugins/yeoman-environment-7/NOTICE

@@ -0,0 +1,51 @@
+pmcp
+
+Copyright (c) 2026 modootoday. All rights reserved.
+
+Licensor: modootoday
+Licensed under the Elastic License 2.0; see LICENSE.
+
+The licensor is modootoday, the company, not any individual contributor. This
+file names the licensor because the Elastic License 2.0 defines that term rather
+than carrying a copyright line of its own; LICENSE is kept unmodified.
+
+What the licence permits, in short, without replacing the terms in LICENSE:
+
+  - Using this software inside your own company, on any scale.
+  - Embedding it in a product you sell, and modifying or forking it.
+  - Redistributing it, with these notices intact.
+  - Running it locally as an MCP server, which is what it is for. A host
+    process spawning it on your own machine is use, not a hosted service.
+
+What it does not permit:
+
+  - Offering this software to third parties as a hosted or managed service.
+    A remotely hosted MCP endpoint serving other people is the case this
+    forbids.
+  - Circumventing licence key functionality.
+  - Removing or obscuring these notices.
+
+The Elastic License 2.0 is source-available, not an OSI-approved open source
+licence. It grants a patent licence and ends that licence if you assert a patent
+claim against the software; see the Patents section of LICENSE.
+
+LICENSE governs. Where this summary and LICENSE differ, LICENSE is what applies.
+
+---
+
+This software depends on the following packages, which are distributed under
+their own terms and are not covered by the licence above.
+
+  @modelcontextprotocol/server   MIT   Copyright (c) Anthropic, PBC
+  @modelcontextprotocol/core     MIT   Copyright (c) Anthropic, PBC
+  zod                            MIT   Copyright (c) Colin McDonnell
+  semver                         ISC   See the dependency's LICENSE file.
+  smol-toml              BSD-3-Clause   Copyright (c) Squirrel Chat et al.
+  yaml                           ISC   Copyright Eemeli Aro
+
+Full licence texts and copyright notices ship with those packages. Their
+respective licence terms govern distribution of those dependencies.
+
+@huggingface/transformers is an optional peer dependency. It is never
+distributed with this package; a user who wants semantic ranking installs it
+themselves, under its own Apache-2.0 terms.

package/plugins/yeoman-environment-7/gemini-extension.json

@@ -0,0 +1 @@
+{ "name": "yeoman-environment-7", "version": "7.0.0" }