@modootoday/pmcp 0.13.1 → 0.14.1

package/plugins/bullmq-5/skills/bullmq/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: bullmq
+description: Use BullMQ 5 to produce Redis-backed jobs, run workers, distinguish completion/retry/permanent failure and close workers gracefully. Use for queue workflows with explicit connection ownership and idempotent side effects without adopting other-major APIs.
+---
+
+# BullMQ 5
+
+Inspect the installed versions, queues, prefixes, Redis topology and worker lifecycle first. This line targets BullMQ 5.81.4 with ioredis 5.11.1. Preserve project concurrency, retention and retry policy.
+
+## Produce and consume
+
+Use matching queue names and prefixes for `Queue`, `Worker` and `QueueEvents`. Request producers need bounded failure; worker connections need `maxRetriesPerRequest: null`. `QueueEvents` needs its own blocking connection; do not share a Pub/Sub connection.
+
+```ts
+import type Redis from "ioredis";
+import { Queue, Worker } from "bullmq";
+
+export function createWorkflow(
+  producer: Redis,
+  workerConnection: Redis,
+  prefix: string,
+) {
+  const queue = new Queue("jobs", { connection: producer, prefix });
+  const worker = new Worker(
+    "jobs",
+    async (job) => {
+      if (typeof job.data.value !== "number") throw new Error("Invalid value");
+      return job.data.value * 2;
+    },
+    { connection: workerConnection, prefix, concurrency: 1 },
+  );
+  return { queue, worker };
+}
+```
+
+The caller must create `workerConnection` with `maxRetriesPerRequest: null`, register operational error listeners and own shutdown. Add jobs with `queue.add(name, data, { attempts, backoff })`; TypeScript job types do not validate incoming JSON.
+
+## Verify state
+
+Wait for worker and `QueueEvents` readiness. In bounded integration tests, use `job.waitUntilFinished(queueEvents, timeout)` and check stored state. A return value and `completed` state differ from a rejected waiter and `failed` state.
+
+Use a transient failure that succeeds on a configured later attempt and a permanent failure that exhausts attempts. Inspect `attemptsMade` on a refreshed job, not a stale object. An error event is not a completed job.
+
+Retries and stalled recovery can execute work more than once. Make side effects idempotent. `jobId` deduplicates additions only while that job exists; removing a completed job permits reuse. Job IDs do not establish exactly-once delivery.
+
+## Own shutdown
+
+`await worker.close()` stops taking jobs and waits for active work. It has no overall deadline; the host must bound shutdown and choose a forced-stop policy. Close workers, queue event consumers, queues and finally caller-owned Redis clients. A queue does not own an independently supplied ioredis client.
+
+Tests need a unique prefix and cleanup of only their queue after workers stop. Never obliterate an application queue as fixture setup. Review Redis `noeviction` with the service owner instead of modifying shared configuration from a helper.
+
+The fixture targets one worker, concurrency 1, completion, retry, permanent failure, a network interruption and graceful close during active work. It does not establish production stalled-job recovery, multiple-worker coordination, repeatable scheduling, Cluster/Sentinel or BullMQ Pro behavior.
+
+## Primary sources
+
+- [Connections](https://docs.bullmq.io/guide/connections)
+- [Graceful shutdown](https://docs.bullmq.io/guide/workers/graceful-shutdown)
+- [Production guidance](https://docs.bullmq.io/guide/going-to-production)
+- [Upstream](https://github.com/taskforcesh/bullmq)

package/plugins/bun-types-1/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "bun-types-1",
+  "version": "1.1.0",
+  "description": "Use bun-types as TypeScript declarations for Bun runtime APIs, while avoiding the common mistake of treating it as a runtime package. Covers the current @types/bun wrapper shape, explicit configuration for direct bun-types usage, and the Bun APIs described by the declarations.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

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

@@ -0,0 +1 @@
+{ "name": "bun-types-1", "version": "1.1.0" }

package/plugins/bun-types-1/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "bun-types-1",
+  "version": "1.1.0",
+  "description": "Use bun-types as TypeScript declarations for Bun runtime APIs, while avoiding the common mistake of treating it as a runtime package. Covers the current @types/bun wrapper shape, explicit configuration for direct bun-types usage, and the Bun APIs described by the declarations.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/bun-types-1/skills/bun-types/SKILL.md

@@ -0,0 +1,119 @@
+---
+name: bun-types
+description: Use bun-types ^1.0.0 as Bun runtime declarations, with correct v1 installation, module names, and the boundary between type availability and runtime availability.
+---
+
+Verified against bun-types@1.4.2 on 2026-09-08. 2 of 2 examples executed.
+
+# bun-types
+
+`bun-types` is a declaration-only package for Bun's JavaScript runtime APIs. Installing it does not provide a runtime implementation; the program must be run by Bun.
+
+## v1.0.0 installation and TypeScript configuration
+
+For the v1.0.0 package, install the package directly:
+
+```sh
+bun add bun-types
+```
+
+Opt into its declarations in `tsconfig.json` or `jsconfig.json`:
+
+```json
+{
+  "types": ["bun-types"]
+}
+```
+
+The declarations aggregate Bun globals, `bun` APIs, Node-compatible declarations, `bun:sqlite`, `bun:test`, and `bun:ffi` declarations. The `bun` module is documented as an alias of `globalThis.Bun`.
+
+Do not confuse this v1.0.0 setup with the newer documented installation surface. The current README recommends `@types/bun` instead:
+
+```sh
+bun add -D @types/bun
+```
+
+Current `@types/bun` is a shim that loads `bun-types`, and ordinary `@types/*` discovery can make the declarations available without the old explicit `types` entry. That is a later package/documentation shape; when targeting `bun-types` v1.0.0, use the direct package and explicit configuration shown above.
+
+## Runtime boundary
+
+`bun-types` only affects type checking. It does not make Bun APIs available in Node or another JavaScript runtime. Run code using these declarations with Bun.
+
+The examples below are standalone Bun scripts. They import the declaration package by name and use only APIs that can run without a network or filesystem dependency.
+
+## The `bun` module
+
+Import runtime APIs from `bun`, not from `bun-types`:
+
+```ts pmcp-example
+import type {} from "bun-types";
+import { file, serve, write, which, dns } from "bun";
+import assert from "node:assert/strict";
+
+assert.equal(typeof file, "function");
+assert.equal(typeof serve, "function");
+assert.equal(typeof write, "function");
+assert.equal(typeof which, "function");
+assert.equal(typeof dns, "object");
+```
+
+The declared surfaces include:
+
+- `file(path)`, which creates a Bun file object.
+- `serve({ fetch, port })`, which starts a server and therefore belongs in a Bun program with an appropriate lifecycle.
+- `write(destination, input)`, which asynchronously writes a supported string, blob, typed array, array buffer, or blob-part array.
+- `which(command, options?)`, which returns a path or `null`; its options can provide `PATH` and `cwd`.
+- `dns.lookup(hostname, options?)`, whose options include address family, socket type, flags, port, and backend.
+
+For example, the declaration for `which` is shaped like this:
+
+```ts
+const executable: string | null = which("some-command", {
+  PATH: "/some/path",
+  cwd: "/some/working/directory",
+});
+```
+
+Do not assume that installing `bun-types` makes `file`, `serve`, `write`, `which`, or `dns` callable in a plain Node process.
+
+## SQLite
+
+SQLite is a separate Bun built-in module, imported as `bun:sqlite`:
+
+```ts pmcp-example
+import type {} from "bun-types";
+import { Database } from "bun:sqlite";
+import assert from "node:assert/strict";
+
+const db = new Database(":memory:");
+db.run("CREATE TABLE foo (bar TEXT)");
+db.run("INSERT INTO foo VALUES (?)", "baz");
+
+assert.deepEqual(db.query("SELECT * FROM foo").all(), [{ bar: "baz" }]);
+```
+
+`Database` accepts an optional filename and options. The options form includes `readonly`, `create`, and `readwrite`. An in-memory database can be selected with `":memory:"`.
+
+The declaration exposes these important operations:
+
+- `run(sqlQuery, ...bindings)`, returning `void`.
+- `query(sqlQuery)`, returning a statement.
+- `prepare(sqlQuery, params?)`, returning a statement.
+
+Bindings are passed to `run` as SQL query bindings, as in the example. Do not import SQLite from the ordinary `sqlite` package; the declared entry point is `bun:sqlite`.
+
+## Other declared entry points
+
+The package also declares `bun:test` and `bun:ffi`. Their declarations are available through this package, but they are intended for Bun's own test and FFI usage rather than for the standalone examples in this skill. Do not expect `bun-types` itself to execute either feature.
+
+## Common mistakes
+
+- **Using the old setup with a current installation guide:** `bun-types` v1.0.0 uses a direct dependency and explicit `"types": ["bun-types"]`; current documentation instead presents `@types/bun`.
+- **Importing declarations as runtime APIs:** import runtime functions from `bun` and SQLite from `bun:sqlite`. `bun-types` supplies declarations only.
+- **Running the code under Node:** the declarations do not polyfill `globalThis.Bun`, `bun`, or `bun:*` modules.
+- **Using `describe`, `it`, or `expect` in a direct script:** those are not supplied by a standalone script. The examples here use `node:assert/strict` and can be run directly with Bun.
+- **Treating `bun:sqlite` as a normal npm module:** use the built-in module specifier exactly as declared.
+
+## Not covered
+
+This skill does not specify the detailed APIs or usage patterns inside `bun:test` or `bun:ffi`, because the supplied research only identifies those entry points and does not include their declarations. It also does not cover server lifecycle management, filesystem effects from `file` or `write`, DNS results, or the complete `Bun` global API. Those require the Bun runtime and details outside the provided research.

package/plugins/chai-6/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "chai-6",
+  "version": "6.0.0",
+  "description": "Use Chai 6 as an ESM-only assertion library, including its expect, assert, should, plugin, configuration, and Assertion extension surfaces.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

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

@@ -0,0 +1 @@
+{ "name": "chai-6", "version": "6.0.0" }

package/plugins/chai-6/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "chai-6",
+  "version": "6.0.0",
+  "description": "Use Chai 6 as an ESM-only assertion library, including its expect, assert, should, plugin, configuration, and Assertion extension surfaces.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}