@modootoday/pmcp 0.13.0 → 0.14.0

package/plugins/responselike-4/skills/responselike/SKILL.md

@@ -0,0 +1,173 @@
+---
+name: responselike
+description: Use responselike ^4.0.0 to construct a Node.js readable HTTP-like response with status, headers, body, and URL metadata.
+---
+
+Verified against responselike@4.0.2 on 2026-09-08. 5 of 5 examples executed.
+
+# responselike
+
+## What this package provides
+
+`responselike` v4.0.0 exports a default `Response` class. It is an ESM package and requires Node.js 20 or newer. `Response` extends Node’s readable stream and represents an HTTP-like response with metadata plus a streamable body.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import Response from 'responselike';
+
+const response = new Response({
+  statusCode: 200,
+  headers: {
+    'Content-Type': 'text/plain',
+    'X-Request-Id': 'abc123'
+  },
+  body: Buffer.from('Hi!'),
+  url: 'https://example.com'
+});
+
+assert.equal(response.statusCode, 200);
+assert.deepEqual(response.headers, {
+  'content-type': 'text/plain',
+  'x-request-id': 'abc123'
+});
+assert.deepEqual(response.body, Buffer.from('Hi!'));
+assert.equal(response.url, 'https://example.com');
+```
+
+## Constructing a response
+
+Pass an options object containing:
+
+- `statusCode`: a number
+- `headers`: an object whose values are strings
+- `body`: a `Buffer` or other `Uint8Array`
+- `url`: the request URL string
+
+Header keys are automatically lowercased. Do not preserve the casing from the input when looking up headers.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import Response from 'responselike';
+
+const response = new Response({
+  statusCode: 201,
+  headers: {
+    Location: '/items/1',
+    'Content-Length': '0'
+  },
+  body: new Uint8Array(),
+  url: 'https://example.com/items'
+});
+
+assert.equal(response.statusCode, 201);
+assert.equal(response.headers.location, '/items/1');
+assert.equal(response.headers['content-length'], '0');
+assert.equal(response.headers.Location, undefined);
+assert.deepEqual(response.body, Buffer.alloc(0));
+assert.equal(response.url, 'https://example.com/items');
+```
+
+The constructor validates the status code, headers, body, and URL. A `Uint8Array` body is accepted even though the TypeScript `Options` declaration specifies `Buffer`.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import Response from 'responselike';
+
+const valid = {
+  statusCode: 200,
+  headers: {},
+  body: Buffer.from('body'),
+  url: 'https://example.com'
+};
+
+assert.throws(() => new Response({...valid, statusCode: '200'}));
+assert.throws(() => new Response({...valid, body: 'body'}));
+assert.throws(() => new Response({...valid, url: 123}));
+```
+
+The runtime accepts an object-shaped headers value such as an empty array; do not rely on an array being rejected merely because the TypeScript declaration describes headers as `Record<string, string>`.
+
+## Reading the body as a stream
+
+The same bytes are available through `response.body` and through the inherited readable-stream interface. Consume the stream with normal Node.js stream APIs or async iteration.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import Response from 'responselike';
+
+const response = new Response({
+  statusCode: 200,
+  headers: {},
+  body: Buffer.from('streamed body'),
+  url: 'https://example.com'
+});
+
+const chunks = [];
+for await (const chunk of response) {
+  chunks.push(chunk);
+}
+
+assert.deepEqual(Buffer.concat(chunks), Buffer.from('streamed body'));
+assert.equal(response.complete, true);
+```
+
+The v4 implementation delays stream completion until a subsequent read. This allows consumers to attach listeners before data flows through pipes and fixes hanging when the response is piped through `decompress-response`. It also sets `complete` to `true` after the stream emits `end`, as required by `mimic-response`.
+
+## Piping
+
+Because `Response` is a Node readable stream, it can be piped to a writable stream. The package does not provide a CLI or test-runner environment; use it from ordinary Node.js ESM code.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import {Writable} from 'node:stream';
+import Response from 'responselike';
+
+const response = new Response({
+  statusCode: 200,
+  headers: {},
+  body: Buffer.from('piped'),
+  url: 'https://example.com'
+});
+
+const received = [];
+const destination = new Writable({
+  write(chunk, encoding, callback) {
+    received.push(Buffer.from(chunk));
+    callback();
+  }
+});
+
+await new Promise((resolve, reject) => {
+  destination.once('finish', resolve);
+  destination.once('error', reject);
+  response.pipe(destination);
+});
+
+assert.deepEqual(Buffer.concat(received), Buffer.from('piped'));
+assert.equal(response.complete, true);
+```
+
+## v4 migration notes
+
+- v4 requires Node.js 20. Code written for v3 may have required only Node.js 14.16 or newer.
+- The existing default-import and constructor shape remains valid:
+
+  ```js
+  import Response from 'responselike';
+  const response = new Response({statusCode, headers, body, url});
+  ```
+
+- Use the ESM default import shown above rather than expecting a CLI or a package runner.
+- The v4 stream-completion behavior is important when integrating with `decompress-response` or `mimic-response`; consume or pipe the response as a stream rather than assuming that merely constructing it has ended the stream.
+
+## TypeScript surface
+
+TypeScript can import the `Options` type and the default `Response` class. The declared options are readonly and use `Buffer` for `body`:
+
+```ts
+import Response, {type Options} from 'responselike';
+```
+
+## Not covered
+
+This skill does not cover constructor defaults when options are omitted, exact validation error messages, HTTP client integration, `decompress-response` configuration, `mimic-response` usage details, or the package’s development-only `xo`, `ava`, and `tsd` commands.

package/plugins/rolldown-1/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "rolldown-1",
+  "version": "1.0.0",
+  "description": "Use Rolldown 1.x programmatically, with the current JavaScript API shape, standalone transform utilities, and correct bundle/plugin lifecycle handling.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/rolldown-1/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/rolldown-1/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/rolldown-1/gemini-extension.json

@@ -0,0 +1 @@
+{ "name": "rolldown-1", "version": "1.0.0" }

package/plugins/rolldown-1/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "rolldown-1",
+  "version": "1.0.0",
+  "description": "Use Rolldown 1.x programmatically, with the current JavaScript API shape, standalone transform utilities, and correct bundle/plugin lifecycle handling.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/rolldown-1/skills/rolldown/SKILL.md

@@ -0,0 +1,182 @@
+---
+name: rolldown
+description: Use Rolldown 1.x programmatically, with the current JavaScript API shape, standalone transform utilities, and correct bundle/plugin lifecycle handling.
+---
+
+Verified against rolldown@1.2.7 on 2026-09-08. 2 of 2 examples executed.
+
+# rolldown
+
+## Scope
+
+This skill covers the documented Rolldown `^1.0.0` JavaScript API and the standalone transform utility. The package is Rollup-compatible, but current Rolldown 1.x has important differences from older Rollup-shaped examples.
+
+## Current JavaScript API shape
+
+Import the bundler functions from the package root:
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import { defineConfig } from 'rolldown';
+
+const config = defineConfig({
+  input: 'src/main.js',
+  output: { file: 'bundle.js' },
+});
+
+assert.equal(config.input, 'src/main.js');
+assert.deepEqual(config.output, { file: 'bundle.js' });
+```
+
+The root-level documented functions include:
+
+- `rolldown`
+- `build`
+- `watch`
+- `defineConfig`
+- utility APIs such as `parse`, `parseAst`, `minify`, and related helpers
+
+For a bundle, create a bundle from input options, then generate or write output:
+
+```js
+import { rolldown } from 'rolldown';
+
+const bundle = await rolldown({
+  input: 'src/main.js',
+});
+
+await bundle.generate({ format: 'esm' });
+await bundle.generate({ format: 'cjs' });
+await bundle.write({ file: 'bundle.js' });
+await bundle.close();
+```
+
+`build()` accepts the combined input/output shape:
+
+```js
+import { build } from 'rolldown';
+
+await build({
+  input: 'src/main.js',
+  output: {
+    file: 'bundle.js',
+  },
+});
+```
+
+`BuildOptions` is input options plus an optional output and optional `write` flag. `write` defaults to `true`.
+
+## The common old-API mistake
+
+Do not carry over a config-file shape blindly to `rolldown()`.
+
+The JavaScript API separates input options from output options when using `rolldown()`:
+
+```js
+import { rolldown } from 'rolldown';
+
+const bundle = await rolldown({
+  input: 'src/main.js',
+});
+
+await bundle.write({
+  file: 'bundle.js',
+});
+```
+
+The `build()` API instead accepts the combined shape:
+
+```js
+import { build } from 'rolldown';
+
+await build({
+  input: 'src/main.js',
+  output: { file: 'bundle.js' },
+});
+```
+
+CLI/config-file usage may use output arrays and config arrays. The plain JavaScript API does not accept config arrays, promises, or functions in place of its options object. Call `rolldown()` separately for each input-options set.
+
+## Standalone transform utility
+
+`transform` is exported from `rolldown/utils`, not the package root. It accepts a filename, source text, optional transform options, and an optional TypeScript config cache:
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import { transform } from 'rolldown/utils';
+
+const result = await transform(
+  'example.js',
+  'const value = 1;',
+  null,
+  null,
+);
+
+assert.equal(typeof result, 'object');
+assert.notEqual(result, null);
+```
+
+The signature is:
+
+```ts
+transform(
+  filename: string,
+  sourceText: string,
+  options?: TransformOptions | null,
+  cache?: TsconfigCache | null,
+): Promise<TransformResult>
+```
+
+This is the most useful part of the documented surface for a direct script that has no input files, output directory, runner, or CLI process.
+
+## Watch mode
+
+`watch()` is Rollup-compatible, but closing the watcher is asynchronous:
+
+```js
+import { watch } from 'rolldown';
+
+const watcher = watch({
+  // watcher options
+});
+
+watcher.on('event', () => {});
+
+await watcher.close();
+```
+
+Do not omit `await` from `watcher.close()`.
+
+## Bundle lifecycle and plugins
+
+The JavaScript API user must call `bundle.close()` after generation or writing. The CLI calls plugin `closeBundle` after each run; the JavaScript API does not replace that lifecycle step automatically.
+
+Rolldown's plugin API is almost fully compatible with Rollup, but output lifecycle details differ:
+
+- Each output is processed separately.
+- `outputOptions` runs before build hooks.
+- Build hooks run per output.
+- `closeBundle` runs only after `generate()` or `write()`.
+
+Stateful plugins that assume Rollup's output-hook ordering or single-build behavior need particular care.
+
+## Configuration and CLI boundaries
+
+Config files are loaded by the CLI. The default config loader bundles the config with Rolldown; `native` requires a runtime that can import the config directly.
+
+CLI config exports may be functions and config arrays. Those forms are not accepted as plain JavaScript API options. Keep CLI configuration concerns separate from direct calls to `rolldown()` and `build()`.
+
+## Version-transition notes
+
+The `^1.0.0` range permits later 1.x versions, so check the installed 1.x behavior when relying on prerelease-era details. The project changelog records these breaking changes before final 1.0:
+
+- TypeScript config auto-discovery became enabled by default in `1.0.0-beta.60`.
+- `minify: 'dce-only'` became the default in `1.0.0-rc.7`.
+- `inlineConst: { mode: 'smart', pass: 1 }` became the default in `1.0.0-rc.7`.
+- `BindingMagicString` was renamed to `RolldownMagicString` in `1.0.0-rc.9`.
+- Built-in CSS bundling was dropped and CSS filename options were removed in `1.0.0-rc.6`.
+- `rolldown:runtime` was renamed to `\0rolldown/runtime.js` in `1.0.0-rc.2`.
+
+## What this skill does not cover
+
+This skill does not cover the complete option, hook, AST, parser, minifier, watcher-event, or plugin-hook signatures. It also does not cover CLI invocation details, config-file discovery in a particular project, filesystem-backed bundling setup, or network-dependent behavior. Bundle examples requiring input files and output files are described but are not runnable as standalone examples under the no-filesystem constraints.

package/plugins/semver-7/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "semver-7",
+  "version": "7.0.0",
+  "description": "Compare exact versions and ranges with explicit prerelease policy.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/semver-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/semver-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/semver-7/gemini-extension.json

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