@modootoday/pmcp 0.13.0 → 0.14.0

package/plugins/type-fest-5/skills/type-fest/SKILL.md

@@ -0,0 +1,132 @@
+---
+name: type-fest
+description: Use type-fest v5.0.0 as a strict, type-only utility package. Covers v5 module/configuration requirements, the documented Except and Tagged APIs, and migration traps from v4.
+---
+
+Verified against type-fest@5.9.0 on 2026-09-08. 3 of 3 examples executed.
+
+# type-fest v5
+
+`type-fest` v5.0.0 is a type-only package. It exports TypeScript declarations from the package root; it does not provide runtime functions. Use it from TypeScript with TypeScript `>=5.9`, `{strict: true}`, and an ESM setup. The package declares Node `>=20` and is pure ESM.
+
+## Importing
+
+Use type-only imports from the package root:
+
+```ts
+import type {Except, Tagged} from 'type-fest';
+```
+
+The package has no documented runtime API. Do not write a plain-script example that expects an imported function, constructor, or runtime value. TypeScript's compiler or type-aware tooling must consume the declarations. The examples below are standalone Bun scripts: their runtime assertions only verify that the type-only code erases cleanly, while the assignments demonstrate the intended compile-time types.
+
+## `Except`
+
+`Except<ObjectType, KeysType, Options>` removes selected keys from an object type. `KeysType` must extend `keyof ObjectType`.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import type {Except} from 'type-fest';
+
+type Foo = {
+	a: number;
+	b: string;
+};
+
+type FooWithoutA = Except<Foo, 'a'>;
+
+const value: FooWithoutA = {b: '2'};
+assert.deepEqual(value, {b: '2'});
+```
+
+The older, commonly shown usage shape remains valid in v5:
+
+```ts
+import type {Except} from 'type-fest';
+
+type Foo = {unicorn: string; rainbow: boolean};
+type FooWithoutRainbow = Except<Foo, 'rainbow'>;
+```
+
+Do not treat `Except` as a runtime object-filtering function. It changes only the static type; it does not remove properties from a JavaScript value.
+
+## Tagged types
+
+`Tagged<Type, TagName, TagMetadata>` creates a branded type while retaining the underlying `Type`. Different tags prevent accidental interchangeability even when their underlying types are identical.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import type {Tagged} from 'type-fest';
+
+type AccountNumber = Tagged<number, 'AccountNumber'>;
+type AccountBalance = Tagged<number, 'AccountBalance'>;
+
+function createAccountNumber(): AccountNumber {
+	return 2 as AccountNumber;
+}
+
+function getMoneyFor(accountNumber: AccountNumber): AccountBalance {
+	assert.equal(accountNumber, 2);
+	return 4 as AccountBalance;
+}
+
+const accountNumber = createAccountNumber();
+const balance = getMoneyFor(accountNumber);
+assert.equal(balance, 4);
+assert.equal(accountNumber + 2, 4);
+```
+
+The tag is compile-time-only. Arithmetic and other operations on the underlying value remain possible, but an untagged `number` or a differently tagged number is not accepted where `AccountNumber` is required.
+
+### Metadata, `GetTagMetadata`, and `UnwrapTagged`
+
+A tag can carry metadata as its third parameter. `GetTagMetadata<Type, TagName>` retrieves metadata for a tag, and `UnwrapTagged<TaggedType>` removes all tags and returns the underlying type.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import type {GetTagMetadata, Tagged, UnwrapTagged} from 'type-fest';
+
+type JsonOf<T> = Tagged<string, 'JSON', T>;
+
+function stringify<T>(value: T): JsonOf<T> {
+	return JSON.stringify(value) as JsonOf<T>;
+}
+
+function parse<T extends JsonOf<unknown>>(value: T): GetTagMetadata<T, 'JSON'> {
+	return JSON.parse(value) as GetTagMetadata<T, 'JSON'>;
+}
+
+const encoded = stringify({hello: 'world'});
+const parsed: {hello: string} = parse(encoded);
+assert.deepEqual(parsed, {hello: 'world'});
+
+const plain: UnwrapTagged<typeof encoded> = 'encoded JSON';
+assert.equal(plain, 'encoded JSON');
+```
+
+`Tagged` does not serialize a tag or metadata into the value. The `JSON` example uses casts at the serialization boundary because the type information is represented only in TypeScript.
+
+## Other exports
+
+The v5 root re-exports many declaration-only utilities, including `PackageJson`, `ArraySlice`, `CamelCase`, `Jsonify`, `Merge`, `Paths`, and `SetReturnType`. They are types rather than runtime helpers. This skill does not infer their exact parameters or behavior beyond the researched surface above.
+
+## v5 migration traps
+
+- v5 is pure ESM and declares `"type": "module"`. It requires Node `>=20` and TypeScript `>=5.9`; configure TypeScript with `{strict: true}`.
+- The v4 name `StringKeyOf` was renamed to `KeyAsString` in v5:
+  ```ts
+  // v4
+  import type {StringKeyOf} from 'type-fest';
+
+  // v5
+  import type {KeyAsString} from 'type-fest';
+  ```
+- `ObservableLike` moved to the `./globals` sub-export. The package also documents the `If*` types as deprecated in favor of `If`.
+- `ArrayTail` preserves `readonly` by default in v5 and no longer uses `preserveReadonly`.
+- Naming-case types disable `preserveConsecutiveUppercase` by default.
+- `PartialDeep` disables `allowUndefinedInNonTupleArrays` by default.
+- `Split` enables `strictLiteralChecks` by default.
+- `Paths` defaults `maxRecursionDepth` to `5`, rather than v4's `10`.
+
+## Not covered
+
+This skill does not cover the exact signatures or usage of the other root exports, the `./globals` declarations beyond the `ObservableLike` move, compiler configuration beyond the researched v5 requirements, or behavior of any runtime tool. type-fest itself exposes no documented runtime API; the remaining surface must be checked through TypeScript's compiler or type-aware tooling.

package/plugins/typescript-5/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "typescript-5",
+  "version": "5.0.0",
+  "description": "Choose module resolution for the runtime and verify declaration exports in consumer projects.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

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

@@ -0,0 +1 @@
+{ "name": "typescript-5", "version": "5.0.0" }

package/plugins/typescript-5/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "typescript-5",
+  "version": "5.0.0",
+  "description": "Choose module resolution for the runtime and verify declaration exports in consumer projects.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

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

@@ -0,0 +1,107 @@
+---
+name: typescript
+description: Configure and troubleshoot TypeScript 5 projects, module resolution, declaration exports, and referenced builds while preserving the project's runtime and build system.
+metadata:
+  target-version: "5.9.3"
+---
+
+# TypeScript 5 development workflow
+
+Use the project's installed compiler and scripts. This skill targets TypeScript
+5.9.3; it does not imply compatibility with every 5.x release or the separate
+native-preview compiler.
+
+## Choose options for the host
+
+Read the nearest package.json, the complete tsconfig extends chain, and the
+existing emitter before changing configuration. Preserve the package manager,
+supported runtimes, module format, and strictness policy.
+
+| Execution host                                 | Configuration decision                                                                                                                              |
+| ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
+| JavaScript emitted for Node.js                 | Use a matching Node module mode, such as NodeNext with NodeNext resolution. Package type and .mts/.cts extensions determine ESM/CJS interpretation. |
+| Application bundled by Vite or another bundler | Bundler resolution with ESNext or Preserve module mode can match the bundler's import behavior. Keep the project's existing emitter.                |
+| Published library                              | Check the emitted JavaScript and declarations from consumer projects; a successful source check alone does not prove package compatibility.         |
+
+NodeNext ESM source imports use the emitted extension, such as ./math.js, even
+when the source is math.ts. Bundler resolution permits extensionless relative
+imports; do not transfer that assumption into unbundled Node.js output.
+
+TypeScript paths describes resolution for the compiler. It does not rewrite
+emitted imports or create runtime aliases. Configure the actual runtime/bundler
+when the application needs aliases.
+
+These decisions follow the [compiler-option guide](https://www.typescriptlang.org/docs/handbook/modules/guides/choosing-compiler-options.html)
+and [module-resolution reference](https://www.typescriptlang.org/docs/handbook/modules/reference.html).
+
+## Make a bounded change
+
+Reproduce the diagnostic with the local compiler and the owning project's
+configuration. Use the existing typecheck script, or tsc -p <config> --noEmit when
+the project uses tsc directly. Passing source filenames directly to tsc bypasses
+normal tsconfig discovery.
+
+Keep runtime data validation separate from TypeScript's compile-time guarantees.
+Use narrowing, discriminated unions, or type-only imports to express an existing
+contract. Do not hide a resolution or declaration defect behind any, an assertion,
+skipLibCheck, or a dependency upgrade.
+
+When resolution is unclear, use tsc -p <config> --traceResolution for the failing
+import and inspect its selected package exports condition. Change the narrowest
+incorrect option or export, then repeat the owning check.
+
+## Check published declarations through exports
+
+For a single ESM entrypoint, the package may expose:
+
+```json
+{
+  "type": "module",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js"
+    }
+  }
+}
+```
+
+Build first and ensure both files exist. A consumer must import the package by
+its public name, not by a source path that bypasses exports. Check the packaged
+files under the supported consumer resolution modes and execute the public
+JavaScript entrypoint in its advertised runtime.
+
+Ship declaration dependencies required by consumers, rather than leaving them
+available only through a developer's local installation. The
+[declaration-publishing guide](https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html)
+describes how declarations and their dependencies travel with a package.
+
+Declaration files must describe the corresponding JavaScript module format.
+Use matching .d.mts/.d.cts when those formats require separate declaration
+entrypoints. Dual ESM/CJS output needs checks of both exposed formats; one
+NodeNext consumer does not establish CJS compatibility.
+
+For libraries bundled with external dependencies, check imports retained in
+declarations and JavaScript. Bundler-only source resolution can accept imports
+that break in Node.js consumers.
+
+## Referenced projects
+
+Use the existing reference graph rather than replacing it with one broad source
+glob. Referenced projects normally use composite and emit declarations; a
+solution tsconfig can contain files: [] and references to the buildable projects.
+Run tsc -b <solution> for dependency-order builds. Use noEmit on a separate
+consumer check when appropriate, rather than removing outputs that downstream
+references require.
+
+Inspect include, rootDir, outDir, declaration outputs, and build-info paths when
+a reference is stale or incomplete. Keep generated outputs separate from source.
+The [project-reference guide](https://www.typescriptlang.org/docs/handbook/project-references.html)
+explains the build contract.
+
+## Completion evidence
+
+Report the compiler version, project configuration checked, and actual commands.
+For a library, include declaration consumption through exports and public runtime
+imports. Distinguish passing checks, expected negative diagnostics, and unchecked
+formats. Do not describe a successful build as proof of all supported platforms.

package/plugins/typescript-eslint-8/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "typescript-eslint-8",
+  "version": "8.0.1",
+  "description": "Check typed lint rules and diagnostics with both supported ESLint fixture majors.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/typescript-eslint-8/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/typescript-eslint-8/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/typescript-eslint-8/gemini-extension.json

@@ -0,0 +1 @@
+{ "name": "typescript-eslint-8", "version": "8.0.1" }

package/plugins/typescript-eslint-8/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "typescript-eslint-8",
+  "version": "8.0.1",
+  "description": "Check typed lint rules and diagnostics with both supported ESLint fixture majors.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}