@modootoday/pmcp 0.13.0 → 0.14.0

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

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

package/plugins/figures-6/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "figures-6",
+  "version": "6.0.0",
+  "description": "Use figures 6.x to render Unicode symbols with terminal-aware fallbacks, access explicit main/fallback symbol sets, and replace symbols in strings.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/figures-6/skills/figures/SKILL.md

@@ -0,0 +1,99 @@
+---
+name: figures
+description: Use figures 6.x to render Unicode symbols with terminal-aware fallbacks, access explicit main/fallback symbol sets, and replace symbols in strings.
+---
+
+Verified against figures@6.1.0 on 2026-09-08. 3 of 3 examples executed.
+
+# figures
+
+`figures` 6.x is a native ESM package for Unicode symbols with fallbacks for terminals that do not support all Unicode figures. The documented version is 6.1.0 and it requires Node.js 18 or newer.
+
+## Imports and package shape
+
+Use named exports for the symbol collections and replacement helper:
+
+```ts
+import figures, {mainSymbols, fallbackSymbols, replaceSymbols} from 'figures';
+```
+
+The default export is the terminal-selected figure set. `mainSymbols` always contains the Unicode symbols, while `fallbackSymbols` always contains their fallback equivalents. The listed figures are also attached to the default export, so `figures.tick`, `figures.star`, `figures.line`, and similar properties are valid.
+
+Do not rely on the commonly copied v5-style shape:
+
+```ts
+figures.mainSymbols.tick
+figures.fallbackSymbols.tick
+figures.replaceSymbols('✔ check')
+```
+
+In v6, use the named exports `mainSymbols`, `fallbackSymbols`, and `replaceSymbols`. The v6 package is native ESM, so use `import`, not CommonJS `require`.
+
+## Default terminal-selected symbols
+
+The default export selects symbols using terminal Unicode support detection. For example, `figures.tick` is `✔` on a Unicode-capable terminal and `√` otherwise. Because selection is environment-dependent, do not assert one exact value for the default export in portable tests.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import figures, {mainSymbols, fallbackSymbols} from 'figures';
+
+assert.ok(typeof figures.tick === 'string');
+assert.ok(figures.tick === mainSymbols.tick || figures.tick === fallbackSymbols.tick);
+assert.equal(typeof figures.star, 'string');
+assert.equal(typeof figures.line, 'string');
+```
+
+The default export includes the documented figure names, including common status symbols such as `tick`, `info`, `warning`, and `cross`; shapes such as `circle`, `checkboxOn`, `pointer`, and `star`; arrows and fractions; and box-drawing names such as `line`, `lineBold`, `lineVertical`, and `lineCross`.
+
+## Explicit symbol sets
+
+Use `mainSymbols` when output must always use the Unicode figures, regardless of the terminal. Use `fallbackSymbols` when output must always use the fallback figures.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import {mainSymbols, fallbackSymbols} from 'figures';
+
+assert.equal(mainSymbols.tick, '✔');
+assert.equal(fallbackSymbols.tick, '√');
+assert.equal(typeof mainSymbols.info, 'string');
+assert.equal(typeof fallbackSymbols.warning, 'string');
+assert.equal(typeof mainSymbols.lineCross, 'string');
+assert.equal(typeof fallbackSymbols.oneSeventh, 'string');
+```
+
+Both collections expose readonly string properties. Do not mutate them.
+
+## Replacing symbols in text
+
+`replaceSymbols(string, options?)` replaces recognized main symbols with the terminal-appropriate versions by default. Pass `{useFallback: true}` to force fallback symbols even on a Unicode-capable terminal.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import {replaceSymbols} from 'figures';
+
+const input = '✔ check';
+const replaced = replaceSymbols(input);
+
+assert.ok(replaced === '✔ check' || replaced === '√ check');
+assert.equal(replaceSymbols(input, {useFallback: true}), '√ check');
+```
+
+The option type is:
+
+```ts
+type Options = {
+	readonly useFallback?: boolean;
+};
+```
+
+`useFallback: true` is the v6.1 addition. Use it when generated output must be stable and use fallback symbols rather than depending on terminal detection.
+
+## Terminal behavior
+
+The default set and `replaceSymbols()` without `useFallback` are terminal-sensitive. Unsupported terminals documented by the package include `xterm`, Linux Terminal (kernel), and `cmder`; they can display most but not all symbols. Prefer `fallbackSymbols` or `replaceSymbols(text, {useFallback: true})` when compatibility matters.
+
+In v6.0, `circleQuestionMark` and `questionMarkPrefix` are always displayed as `(?)`. Older macOS-specific circled-question-mark behavior should not be expected.
+
+## What this skill does not cover
+
+This skill does not cover symbols beyond the documented named properties, terminal detection internals, or behavior of terminals not described by the package research. It also does not cover a CLI, build step, or test-runner integration: the package exposes no such tool surface in the researched material and is used directly from a Node ESM script.

package/plugins/firebase-12/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "firebase-12",
+  "version": "12.0.0",
+  "description": "Use Firebase JS SDK ^12.0.0 with the modular API, correct v12 imports, and Node 20-compatible tooling. Covers app initialization, Auth and Firestore entry points, Firestore Lite query construction, compat migration traps, and v12 naming changes.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

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

@@ -0,0 +1 @@
+{ "name": "firebase-12", "version": "12.0.0" }

package/plugins/firebase-12/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "firebase-12",
+  "version": "12.0.0",
+  "description": "Use Firebase JS SDK ^12.0.0 with the modular API, correct v12 imports, and Node 20-compatible tooling. Covers app initialization, Auth and Firestore entry points, Firestore Lite query construction, compat migration traps, and v12 naming changes.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/firebase-12/skills/firebase/SKILL.md

@@ -0,0 +1,161 @@
+---
+name: firebase
+description: Use Firebase JS SDK ^12.0.0 with the modular API, correct v12 imports, and Node 20-compatible tooling. Covers app initialization, Auth and Firestore entry points, Firestore Lite query construction, compat migration traps, and v12 naming changes.
+---
+
+Verified against firebase@12.18.0 on 2026-09-08. 2 of 2 examples executed.
+
+# Firebase JS SDK ^12.0.0
+
+Firebase v12 uses the modular, function-based API. Install it with `npm install firebase`. Firebase v12 requires Node.js 20+ and targets ES2020; older build tooling may need updates.
+
+## Prefer modular imports
+
+Import functions from product subpaths rather than using a namespace:
+
+```ts
+import { initializeApp } from 'firebase/app';
+import { getAuth, onAuthStateChanged } from 'firebase/auth';
+import { getFirestore, collection, query, where, getDocs } from 'firebase/firestore';
+```
+
+Modular imports are tree-shakeable. The modular API generally requires a module bundler such as webpack or Rollup in application builds.
+
+## App lifecycle
+
+Use `initializeApp` to create an app, `getApp` to retrieve a named or default app, `getApps` to inspect initialized apps, and `deleteApp` to clean one up.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import { initializeApp, getApp, getApps, deleteApp } from 'firebase/app';
+
+const app = initializeApp({
+  apiKey: 'test-api-key',
+  authDomain: 'example.firebaseapp.com',
+  projectId: 'example-project'
+}, 'skill-example');
+
+assert.equal(getApp('skill-example'), app);
+assert.equal(getApps().includes(app), true);
+
+await deleteApp(app);
+assert.equal(getApps().some(candidate => candidate === app), false);
+```
+
+`initializeApp(options, name?)` accepts an optional name. Avoid initializing the same named app repeatedly; use `getApp(name)` or inspect `getApps()` when code may run more than once.
+
+## Authentication
+
+Get an Auth instance with `getAuth(app?)`, or use `initializeAuth(app, deps?)` when explicit initialization dependencies are needed:
+
+```ts
+import { getAuth, initializeAuth } from 'firebase/auth';
+```
+
+The Auth instance is associated with the Firebase app. Modular authentication functions receive that instance as an argument, for example `getRedirectResult(auth)` and `onAuthStateChanged(auth, callback)`.
+
+A migration trap is the redirect-result shape: the old namespaced API returned a `UserCredential` whose `user` could be `null` when there was no redirect; modular `getRedirectResult(auth)` returns `null` when there was no redirect.
+
+## Cloud Firestore
+
+Use `getFirestore(app)` for the default database or `getFirestore(app, databaseId)` for a named database. Use `initializeFirestore(app, settings, databaseId?)` when Firestore settings must be supplied before obtaining the instance.
+
+```ts
+import { getFirestore, initializeFirestore } from 'firebase/firestore';
+```
+
+The Firestore API is usable for constructing references and queries without performing I/O:
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import { initializeApp, deleteApp } from 'firebase/app';
+import { getFirestore, collection, query, where } from 'firebase/firestore';
+
+const app = initializeApp({
+  apiKey: 'test-api-key',
+  authDomain: 'example.firebaseapp.com',
+  projectId: 'example-project'
+}, 'firestore-skill-example');
+
+const db = getFirestore(app);
+const cities = collection(db, 'cities');
+const capitalCities = query(cities, where('capital', '==', true));
+
+assert.equal(capitalCities.type, 'query');
+await deleteApp(app);
+```
+
+For reads, pass the query or collection to `getDocs`:
+
+```ts
+const snapshot = await getDocs(capitalCities);
+const cities = snapshot.docs.map(doc => doc.data());
+```
+
+That read performs a backend operation and therefore is not suitable for an offline, standalone example. Firestore persistence and other environment support are product- and environment-specific.
+
+## Firestore Lite
+
+The Lite entry point is `firebase/firestore/lite`:
+
+```ts
+import { getFirestore, collection, getDocs } from 'firebase/firestore/lite';
+
+const db = getFirestore(app);
+const citiesCol = collection(db, 'cities');
+const citySnapshot = await getDocs(citiesCol);
+const cityList = citySnapshot.docs.map(doc => doc.data());
+```
+
+`getDocs` requires access to the configured Firebase backend when executed; do not assume it can run in an offline script.
+
+## v12 naming changes
+
+Firebase v12 removed `firebase/vertexai` and VertexAI-named symbols. Use the AI names instead:
+
+```ts
+import { getAI } from 'firebase/ai';
+```
+
+`getVertexAI`, `VertexAIError`, and the old `firebase/vertexai` import are not the v12 API. v12 also adds AI Logic grounding with Google Search, thinking budget, and `anyOf` schemas.
+
+## Compat and migration pitfalls
+
+Existing namespaced code can use the compatibility bridge, but compat is a migration path rather than the preferred long-term API and provides little or no modular size/performance advantage:
+
+```ts
+import firebase from 'firebase/compat/app';
+import 'firebase/compat/auth';
+import 'firebase/compat/firestore';
+
+const auth = firebase.auth();
+const db = firebase.firestore();
+```
+
+Do not mix old instance methods with modular functions mechanically. Typical translations include:
+
+```ts
+// Compat
+const result = await auth.getRedirectResult();
+
+// Modular
+const result = await getRedirectResult(auth);
+```
+
+```ts
+// Compat snapshot
+if (snapshot.exists) {}
+
+// Modular snapshot
+if (snapshot.exists()) {}
+```
+
+In browser script-tag integrations, `window.firebase` is the compat path; the modular npm API is not exposed that way.
+
+## Environment notes
+
+Firebase v12 itself requires Node 20+, although product-specific support documentation also describes browser, Node, extension, React Native, and Cordova environments. Polyfills may still be needed. Analytics, Installations, Messaging, Performance Monitoring, and Remote Config do not work in Node.js. Firestore edge/Node support excludes persistence, and Storage edge support excludes uploads.
+
+## Not covered
+
+This skill does not cover product-specific configuration values, authentication providers or sign-in flows, Firestore writes and security rules, persistence setup, Storage, Analytics, Messaging, Remote Config, Performance Monitoring, or the detailed AI API. It also does not cover Firebase CLI commands, framework integration, bundler configuration, or network-backed tests.

package/plugins/firebase-admin-14/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "firebase-admin-14",
+  "version": "14.0.0",
+  "description": "Practical firebase-admin ^14.0.0 guidance for Node.js 22+ server applications, using v14 modular imports and avoiding removed legacy APIs.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}