@laitszkin/apollo-toolkit 2.5.0 → 2.7.0

package/marginfi-development/references/official-development-notes.md

@@ -0,0 +1,191 @@
+# Official Marginfi Development Notes
+
+Checked against official marginfi docs on 2026-03-20.
+
+## Canonical official sources
+
+- Docs home: `https://docs.marginfi.com/`
+- TypeScript SDK docs: `https://docs.marginfi.com/ts-sdk`
+- Rust CLI docs: `https://docs.marginfi.com/rust-sdk`
+- Protocol design: `https://docs.marginfi.com/protocol-design`
+- Program docs (`mfi-v2`): `https://docs.marginfi.com/mfi-v2`
+- The Arena docs: `https://docs.marginfi.com/the-arena`
+
+## 1. Protocol model to keep in mind
+
+marginfi is a pooled-balance lending protocol on Solana. The main developer objects are:
+
+- `MarginfiGroup`: protocol-wide configuration and shared state for a deployment.
+- `Bank`: the per-asset pool with oracle config, risk weights, limits, and utilization-driven rates.
+- `MarginfiAccount`: the user's margin account that holds deposits and liabilities across banks.
+
+Important protocol-design facts from the official docs:
+
+- Risk is controlled by asset weights, liability weights, and loan-to-value style constraints.
+- Oracles come from Pyth and Switchboard, with confidence and staleness checks before prices are accepted.
+- Docs mention a maximum oracle staleness of 60 seconds and a 95% confidence interval requirement.
+- Pyth EMA pricing is described as roughly 5,921 slots (about 1 hour) for smoothing.
+- Interest rates use a two-segment utilization curve: rates rise with utilization, then increase more aggressively after the optimal-utilization threshold.
+- Asset risk tiers include collateral-style assets, borrow-only assets, and isolated assets.
+
+Use these facts when reasoning about account health, liquidations, and bank config; do not reduce health checks to simple spot-price math.
+
+## 2. Official addresses and environments
+
+The official docs currently expose these environment values across the docs home and protocol-design pages:
+
+- Mainnet program: `MFv2hWf31Z9kbCa1snEPYctwafyhdvnV7FZnsebVacA`
+- Mainnet group: `FCPfpHAjHn9R6vWQbtyzcN8PjjobJABQj9rChmC6Cv5j`
+- Staging program: `stag8sTKDs4Df2RehcgddBVAtDx6gbDp7YkA94R6HvK`
+- Staging group: `2rpQwP4ofD6P2AojSeyjc9kUCzjscX4oMtd2N4eySe7W`
+
+Treat these as time-sensitive. Re-check the docs page before hardcoding them in new work.
+
+## 3. TypeScript SDK essentials
+
+Official docs point to the npm package `@mrgnlabs/marginfi-client-v2` plus `@mrgnlabs/mrgn-common` helpers.
+
+Core setup flow from the docs:
+
+1. Create a Solana `Connection`.
+2. Build a wallet adapter or `NodeWallet`.
+3. Load `getConfig("production")` or another environment config.
+4. Call `MarginfiClient.fetch(config, wallet, connection)`.
+5. Fetch existing marginfi accounts for the authority, or create one.
+6. Resolve the target bank, then perform actions.
+
+Minimal example pattern:
+
+```ts
+import { Connection } from "@solana/web3.js";
+import { MarginfiClient, getConfig } from "@mrgnlabs/marginfi-client-v2";
+import { NodeWallet } from "@mrgnlabs/mrgn-common";
+
+const connection = new Connection(process.env.RPC_URL!, "confirmed");
+const wallet = NodeWallet.local();
+const config = getConfig("production");
+const client = await MarginfiClient.fetch(config, wallet, connection);
+
+const accounts = await client.getMarginfiAccountsForAuthority();
+const account = accounts[0] ?? (await client.createMarginfiAccount());
+const bank = client.getBankByTokenSymbol("SOL");
+if (!bank) throw new Error("SOL bank not found");
+
+await account.deposit(1, bank.address);
+```
+
+Useful SDK objects and methods called out in the docs:
+
+- Client bootstrap: `MarginfiClient.fetch`, `getConfig`
+- Bank lookup: `getBankByTokenSymbol`, `getBankByMint`, `getBankByPk`
+- Oracle helpers: `getOraclePriceByBank`
+- Account discovery: `getMarginfiAccountsForAuthority`
+- Account creation: `createMarginfiAccount`
+- Permissionless-bank support: `createLendingPool`
+- Transaction helper: `processTransaction`
+- Margin-account actions on `MarginfiAccountWrapper`: `deposit`, `withdraw`, `borrow`, `repay`, `reload`
+
+Prefer these helpers before assembling raw instructions manually.
+
+## 4. Flash-loan development notes
+
+Official TS SDK docs describe `buildFlashLoanTx` as the preferred helper for building full flash-loan transactions.
+
+The program docs describe flash loans as:
+
+- `lending_account_start_flashloan`
+- user instructions that consume the temporary liquidity
+- `lending_account_end_flashloan`
+
+Important implementation rules:
+
+- Flash loans must begin and end in the same transaction.
+- The end instruction must reference the correct end index.
+- Nested or malformed flash-loan flows are rejected.
+- Relevant program errors include `AccountInFlashloan`, `IllegalFlashloan`, `IllegalFlag`, and `NoFlashloanInProgress`.
+
+If you need raw control, mirror the exact begin/end instruction ordering from the official docs.
+
+## 5. Rust CLI essentials
+
+The Rust CLI docs describe profile-based configuration through `marginfi profile` and account or bank operations through `marginfi group` and `marginfi account` subcommands.
+
+Representative CLI flows from the docs:
+
+- profile and authority setup: `marginfi profile create`, `marginfi profile set`
+- account flows: `marginfi account create`, `deposit`, `borrow`, `withdraw`, `repay`
+- bank and admin flows: `marginfi group add-bank`, `configure-bank`, `collect-fees`, `setup-emissions`, `update-emissions`
+- permissionless-bank creation: `marginfi group add-bank-permissionless`
+
+Use the CLI when the job is operational, administrative, or quick to script from the terminal. Use the TS SDK when embedding marginfi into apps or bots.
+
+## 6. Permissionless banks and The Arena
+
+The Arena docs describe a permissionless flow where developers can create marginfi banks from listed tokens.
+
+Important configuration areas surfaced in the official docs:
+
+- `asset_weight_init` / `asset_weight_maint`
+- `liability_weight_init` / `liability_weight_maint`
+- deposit and borrow limits
+- interest-rate curve parameters such as optimal utilization, plateau rate, max rate, and fees
+- `risk_tier`
+- `operational_state`
+- `oracle_setup`
+
+The official TS docs also show `BankConfigOpt`, `InterestRateConfigOpt`, `OracleSetup`, `RiskTier`, and `OperationalState` in the permissionless-bank example.
+
+When implementing bank creation:
+
+- treat every config field as an explicit input
+- validate the oracle source and required feed accounts
+- keep listing-criteria and The Arena docs open while coding
+- do not fabricate safe defaults for weights or limits
+
+## 7. Program instruction map
+
+The `mfi-v2` docs expose the on-chain instruction set and typed errors.
+
+Key instruction families to consult before raw program work:
+
+- marginfi-group initialization and configuration
+- bank creation and configuration
+- margin-account creation
+- deposit / withdraw
+- borrow / repay
+- emissions setup and update
+- liquidate
+- flash-loan begin / end
+- account transfer flows
+
+Useful error names exposed in the docs include:
+
+- `Unauthorized`
+- `BankNotFound`
+- `MarginfiAccountNotFound`
+- `OperationWithdrawOnly`
+- `IllegalLiquidation`
+- `IllegalFlashloan`
+- `AccountInFlashloan`
+- `NoFlashloanInProgress`
+- `SwitchboardStalePrice`
+- `CannotCloseOutstandingEmissions`
+
+When surfacing failures to users, translate these into the failed business condition instead of echoing raw Solana logs only.
+
+## 8. Security and operational notes
+
+The docs highlight:
+
+- Halborn and Sec3 audits
+- fuzz testing
+- a bug-bounty program
+- verifiable-build support via `solana-verify`
+
+The official verification example is:
+
+```bash
+solana-verify verify-from-repo -um --program-id MFv2hWf31Z9kbCa1snEPYctwafyhdvnV7FZnsebVacA https://github.com/mrgnlabs/marginfi-v2
+```
+
+Use these references when the task touches deployment verification, trust assumptions, or upgrade review.

package/marginfi-development/references/source-index.md

@@ -0,0 +1,31 @@
+# Marginfi Official Source Index
+
+Use this file to jump to the official page that matches the task.
+
+## Primary docs
+
+- `https://docs.marginfi.com/`
+  - Read for current program IDs, group IDs, lookup-table references, and top-level navigation.
+- `https://docs.marginfi.com/ts-sdk`
+  - Read for TypeScript integration, SDK classes, helper methods, and flash-loan or permissionless-bank examples.
+- `https://docs.marginfi.com/rust-sdk`
+  - Read for CLI workflows, operator tasks, profiles, group commands, and bank administration.
+- `https://docs.marginfi.com/protocol-design`
+  - Read for risk model, oracle rules, utilization-based interest design, and liquidation reasoning.
+- `https://docs.marginfi.com/mfi-v2`
+  - Read for raw instruction names, account schemas, and error definitions.
+- `https://docs.marginfi.com/the-arena`
+  - Read for permissionless-bank flows and links to listing criteria.
+
+## When to open which source
+
+- App, bot, backend, or frontend integration: start with `ts-sdk`, then `protocol-design`.
+- CLI or ops automation: start with `rust-sdk`.
+- Custom Anchor or raw Solana instruction work: start with `mfi-v2`.
+- Health checks, liquidation analysis, or risk explanations: start with `protocol-design`, then confirm relevant instruction behavior in `mfi-v2`.
+- Permissionless bank creation: start with `the-arena`, then open `ts-sdk` or `rust-sdk` depending on the chosen toolchain.
+- Address or deployment verification: start with the docs home page, then follow its linked source or verification references.
+
+## Working rule
+
+If the request depends on a value that can change over time, reopen the live official page even if this skill already contains a summary.

package/openclaw-configuration/SKILL.md

@@ -0,0 +1,98 @@
+---
+name: openclaw-configuration
+description: Build, audit, and explain OpenClaw configuration from official documentation. Use when configuring `~/.openclaw/openclaw.json`, mapping config options, adjusting skills or secrets, generating validated snippets, or diagnosing config errors with `openclaw config`, `openclaw configure`, and `openclaw doctor`.
+---
+
+# OpenClaw Configuration
+
+## Dependencies
+
+- Required: none.
+- Conditional: `answering-questions-with-research` when a request depends on newer OpenClaw docs than the bundled references cover.
+- Optional: none.
+- Fallback: If the local CLI is unavailable, work from the bundled references and clearly mark any runtime behavior that was not verified on the machine.
+
+## Standards
+
+- Evidence: Verify the active config file, current values, and CLI diagnostics before editing.
+- Execution: Prefer the smallest safe change; use `openclaw config` for narrow edits and direct JSON edits for broad restructures.
+- Quality: Keep the file schema-valid, avoid plaintext secrets when a SecretRef or env var fits, and preserve unrelated valid settings.
+- Output: Return exact file paths, touched keys, validation commands, and any restart or hot-reload caveats.
+
+## Goal
+
+Help another agent configure OpenClaw safely, quickly, and with citations back to the official docs.
+
+## Workflow
+
+### 1. Classify the request
+
+Decide whether the user needs:
+
+- a config explanation
+- a new starter config
+- a targeted key update
+- skills loading or per-skill env setup
+- secrets or provider wiring
+- validation or repair of a broken config
+
+Assume the canonical config file is `~/.openclaw/openclaw.json` unless the environment proves otherwise.
+
+### 2. Choose the safest edit surface
+
+- Use `openclaw onboard` or `openclaw configure` for guided setup.
+- Use `openclaw config get/set/unset/validate` for precise path-based edits.
+- Use direct JSON edits only when changing several related branches at once.
+- If the local gateway is running, the Control UI config tab at `http://127.0.0.1:18789` can help inspect or edit the same schema-backed config.
+
+### 3. Load only the references you need
+
+- Read `references/official-docs.md` first for the canonical doc map.
+- Read `references/config-reference-map.md` when you need option names, CLI behavior, hot reload, skills config, env handling, or secrets rules.
+- Read `references/best-practices.md` before producing a new config, touching credentials, or fixing a broken setup.
+
+### 4. Apply minimal, schema-safe changes
+
+- Prefer `openclaw config set` for one-path edits.
+- Prefer SecretRefs or env substitution over plaintext credentials.
+- For skill-specific setup, use `skills.load.extraDirs`, `skills.entries.<skillKey>`, and per-skill `env` or `apiKey`.
+- Do not invent unknown root keys; OpenClaw rejects schema-invalid config.
+
+### 5. Validate before finishing
+
+- Run `openclaw config validate` after edits.
+- If the gateway refuses to boot, run `openclaw doctor`.
+- Use `openclaw doctor --repair` only after reviewing what it will change; the tool can back up the config and remove unknown keys.
+- Call out whether the change should hot-apply or may still need a restart.
+
+### 6. Return a concise handoff
+
+Always include:
+
+- the file or keys changed
+- the command or JSON snippet used
+- the validation command
+- any secret or env prereqs
+- the official doc pages that justify the change
+
+## Common Tasks
+
+### Generate a starter config
+
+Start from the official minimal or starter shape, then add only the channels, models, or skills the user actually needs.
+
+### Explain config options
+
+Summarize the relevant branch and point back to the matching official page rather than dumping the entire reference.
+
+### Configure skills
+
+Use `skills.load.extraDirs` for additional skill folders and `skills.entries.<skillKey>` for per-skill enablement, env vars, or `apiKey`.
+
+### Wire secrets
+
+Prefer SecretRefs (`env`, `file`, or `exec`) for supported credential fields. Use plaintext only when the user explicitly wants a local-only quick setup and understands the tradeoff.
+
+### Repair a broken config
+
+Run `openclaw config validate`, then `openclaw doctor`, and only then make the smallest correction that restores schema validity.

package/openclaw-configuration/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "OpenClaw Configuration"
+  short_description: "Configure and troubleshoot OpenClaw settings"
+  default_prompt: "Use $openclaw-configuration to explain, edit, validate, or troubleshoot OpenClaw configuration, including `~/.openclaw/openclaw.json`, `skills` settings, env vars, SecretRefs, and official OpenClaw CLI/config workflows."

package/openclaw-configuration/references/best-practices.md

@@ -0,0 +1,55 @@
+# OpenClaw Configuration Best Practices
+
+These rules are distilled from the official OpenClaw docs and adapted into a practical workflow.
+
+## Authoring rules
+
+- Treat `~/.openclaw/openclaw.json` as the source of truth unless the environment proves otherwise.
+- Prefer the smallest possible edit surface:
+  - one key: `openclaw config set`
+  - one subtree removal: `openclaw config unset`
+  - several coordinated edits: direct JSON edit plus validation
+- Keep JSON structure conservative; OpenClaw rejects unknown keys.
+- Use the configuration examples page as a baseline instead of inventing a new root layout.
+
+## Safety rules
+
+- Never store production credentials in plaintext if a SecretRef or env var can be used.
+- Avoid mixing plaintext and SecretRefs for the same credential path; the ref wins on supported fields and makes ownership clearer.
+- Validate immediately after editing:
+  - `openclaw config validate`
+  - `openclaw doctor` when the gateway still behaves unexpectedly
+- Use `openclaw doctor --repair` only when you are comfortable with automatic cleanup and backup behavior.
+
+## Environment rules
+
+- Prefer `${VAR_NAME}` substitution for portable config shared across machines.
+- Keep env var names uppercase to match the documented substitution pattern.
+- Use `env.shellEnv.enabled` only when the missing-key import behavior is intentional and understood.
+- Avoid scattering the same secret across the parent shell, local `.env`, and `~/.openclaw/.env`; keep precedence simple.
+
+## Skills rules
+
+- Put extra skill roots in `skills.load.extraDirs` instead of hard-coding ad hoc discovery logic elsewhere.
+- Use `skills.entries.<skillKey>.enabled` for explicit enable or disable state.
+- Use `skills.entries.<skillKey>.env` for skill-local environment variables.
+- Use `skills.entries.<skillKey>.apiKey` only when the skill expects a primary env-backed API key convenience field.
+- Leave `skills.load.watch` enabled while iterating on local skills unless file-watch churn becomes a confirmed problem.
+- If you set `skills.install.nodeManager`, remember the official docs still recommend Node as the runtime for the gateway itself.
+
+## Troubleshooting rules
+
+- If the gateway stops booting after a config change, assume schema breakage first and validate before changing unrelated systems.
+- When troubleshooting a credentialed path, inspect both the config branch and the SecretRef provider branch.
+- When a user asks for "why did this stop working," capture the exact key path and the command used to validate it.
+- For broken skill loading, check both `skills.load.extraDirs` and the effective `skillKey` mapping.
+
+## Recommended delivery format
+
+When answering a user or editing a machine, return:
+
+1. the exact file or key path
+2. the change made
+3. the validation command
+4. the secret or env prerequisites
+5. the official docs used

package/openclaw-configuration/references/config-reference-map.md

@@ -0,0 +1,189 @@
+# OpenClaw Config Reference Map
+
+This file condenses the official OpenClaw configuration docs into a quick operator map.
+
+## Main file and edit surfaces
+
+- Canonical file: `~/.openclaw/openclaw.json`
+- Guided setup:
+  - `openclaw onboard`
+  - `openclaw configure`
+- Precise edits:
+  - `openclaw config get <path>`
+  - `openclaw config set <path> <value>`
+  - `openclaw config unset <path>`
+  - `openclaw config validate`
+- UI editing:
+  - Config tab in the local Control UI at `http://127.0.0.1:18789`
+- Direct editing:
+  - safe for broader restructures, but validate immediately afterward
+
+## Validation and reload behavior
+
+- OpenClaw enforces a strict schema.
+- Unknown keys, bad types, or invalid values can prevent the gateway from starting.
+- The root `$schema` string is the documented exception for editor schema metadata.
+- When validation fails, the docs point to diagnostic commands such as:
+  - `openclaw doctor`
+  - `openclaw logs`
+  - `openclaw health`
+  - `openclaw status`
+- The gateway watches `~/.openclaw/openclaw.json` and hot-applies many changes automatically.
+
+## CLI behavior worth remembering
+
+### Paths
+
+- Dot notation works: `agents.defaults.workspace`
+- Bracket notation works: `agents.list[0].tools.exec.node`
+
+### Value parsing
+
+- `openclaw config set` parses JSON5 when possible.
+- Use `--strict-json` when you want parsing to be required.
+- Use strings intentionally for values such as heartbeat durations.
+
+### Assignment modes
+
+- Value mode: plain path/value edit
+- SecretRef builder mode: build a supported ref without hand-writing JSON
+- Provider builder mode: build `secrets.providers.<alias>` entries
+- Batch mode: apply several edits from a JSON payload or file
+
+## Official namespace map
+
+The full reference documents these major sections:
+
+- `channels`
+- `agents`
+- `session`
+- `messages`
+- `talk`
+- `tools`
+- custom providers and base URLs
+- `skills`
+- `plugins`
+- `browser`
+- `ui`
+- `gateway`
+- `hooks`
+- canvas host
+- discovery
+- `environment`
+- `secrets`
+- auth storage
+- logging
+- CLI
+- wizard
+- identity
+- `cron`
+- media model template variables
+- config includes via `$include`
+
+Use the official full reference when you need the exact nested shape under one of these branches.
+
+## Environment variables
+
+The gateway docs describe three non-inline sources:
+
+- env vars from the parent process
+- `.env` in the current working directory
+- `~/.openclaw/.env` as a global fallback
+
+Neither `.env` file overrides variables that are already present in the parent process.
+
+The docs also describe config-side helpers:
+
+- inline `env` sections
+- optional shell env import via `env.shellEnv.enabled`
+- config string substitution with `${VAR_NAME}`
+
+Key rules called out by the docs:
+
+- substitution targets uppercase variable names
+- missing or empty values fail at load time
+- use `$${VAR}` to escape a literal placeholder
+
+## Secrets and credential references
+
+OpenClaw documents a common SecretRef shape:
+
+```json
+{
+  "source": "env",
+  "provider": "default",
+  "id": "OPENAI_API_KEY"
+}
+```
+
+Supported ref sources in the docs:
+
+- `env`
+- `file`
+- `exec`
+
+Operational rules confirmed by the secrets docs:
+
+- if a supported field has both plaintext and a ref, the ref takes precedence
+- `openclaw secrets audit --check` is the default preflight
+- `openclaw secrets configure` helps wire providers
+- a final `openclaw secrets audit --check` confirms the setup
+
+## Skills configuration
+
+The official skills config page documents these fields:
+
+- `skills.allowBundled`
+- `skills.load.extraDirs`
+- `skills.load.watch`
+- `skills.load.watchDebounceMs`
+- `skills.install.preferBrew`
+- `skills.install.nodeManager`
+- `skills.entries.<skillKey>.enabled`
+- `skills.entries.<skillKey>.env`
+- `skills.entries.<skillKey>.apiKey`
+
+Notes confirmed by the docs:
+
+- `skills.entries` keys default to the skill name
+- if a skill defines `metadata.openclaw.skillKey`, use that key instead
+- watcher-driven skill changes are picked up on the next agent turn when watching is enabled
+
+## Example snippets to adapt
+
+### Minimal starter
+
+```json
+{
+  "agents": {
+    "defaults": {
+      "workspace": "~/.openclaw/workspace"
+    }
+  },
+  "channels": {
+    "whatsapp": {
+      "allowFrom": ["+15555550123"]
+    }
+  }
+}
+```
+
+### Custom skill directory plus per-skill env
+
+```json
+{
+  "skills": {
+    "load": {
+      "extraDirs": ["~/skills", "~/.apollo-toolkit"]
+    },
+    "entries": {
+      "openclaw-configuration": {
+        "enabled": true,
+        "env": {
+          "OPENCLAW_CONFIG_PATH": "~/.openclaw/openclaw.json"
+        }
+      }
+    }
+  }
+}
+```

package/openclaw-configuration/references/official-docs.md

@@ -0,0 +1,40 @@
+# OpenClaw Official Config Docs
+
+Last verified: 2026-03-20
+
+Use this file as the entry map into the official OpenClaw documentation on `docs.openclaw.ai`.
+
+## Canonical pages
+
+- Gateway configuration overview: `https://docs.openclaw.ai/gateway/configuration`
+  - Covers the main config file path, edit surfaces, strict validation, hot reload, env vars, and links to the full reference.
+- Full configuration reference: `https://docs.openclaw.ai/gateway/configuration-reference`
+  - Covers the major top-level namespaces such as `channels`, `agents`, `tools`, `skills`, `plugins`, `gateway`, `secrets`, `cron`, and `$include`.
+- Configuration examples: `https://docs.openclaw.ai/gateway/configuration-examples`
+  - Provides minimal and starter-shaped configs plus common deployment patterns.
+- Skills config: `https://docs.openclaw.ai/tools/skills-config`
+  - Covers `skills.allowBundled`, `skills.load.*`, `skills.install.*`, and `skills.entries.<skillKey>`.
+- Secrets management: `https://docs.openclaw.ai/gateway/secrets`
+  - Covers SecretRef structure, providers, precedence, audit flow, and secure credential handling.
+- CLI config command: `https://docs.openclaw.ai/cli/config`
+  - Covers `openclaw config get/set/unset/validate`, path syntax, parsing rules, and SecretRef builder modes.
+- CLI configure command: `https://docs.openclaw.ai/cli/configure`
+  - Covers the guided configuration wizard.
+- CLI doctor command: `https://docs.openclaw.ai/cli/doctor`
+  - Covers diagnostics, repair behavior, backups, and environment checks.
+
+## Core facts confirmed from the official docs
+
+- The canonical config file is `~/.openclaw/openclaw.json`.
+- OpenClaw supports guided edits, CLI path edits, Control UI editing, and direct file editing.
+- The gateway validates the config strictly against schema; unknown keys are rejected except for the root `$schema` metadata key.
+- The gateway watches the config file and hot-applies many changes automatically.
+- Secrets can be supplied through env vars, files, or exec-backed SecretRefs, depending on the field.
+
+## When to open which doc
+
+- Need the exact field name or namespace: open the full reference.
+- Need a starting snippet or pattern: open configuration examples.
+- Need to load custom skills or set per-skill env: open skills config.
+- Need to wire API keys safely: open secrets management plus CLI config.
+- Need to repair a broken config: open gateway configuration plus CLI doctor.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@laitszkin/apollo-toolkit",
-  "version": "2.5.0",
+  "version": "2.7.0",
   "description": "Apollo Toolkit npm installer for managed skill linking across Codex, OpenClaw, and Trae.",
   "license": "MIT",
   "author": "LaiTszKin",