@zhixuan92/multi-model-agent 4.7.7 → 4.7.9

package/dist/skills/mma-audit/SKILL.md

@@ -12,7 +12,7 @@ when_to_use: >-
   (superpowers:dispatching-parallel-agents, /security-review) points at one AND
   mmagent is running. Audit on PROSE/SPEC docs — use mma-review for source code.
   Audit a CODE-EXECUTION PLAN against the codebase — use subtype=plan.
-version: 4.7.7
+version: 4.7.9
 ---
 
 # mma-audit

package/dist/skills/mma-context-blocks/SKILL.md

@@ -12,7 +12,7 @@ when_to_use: >-
   Register once here, then pass the ID via `contextBlockIds` on mma-delegate /
   mma-execute-plan / mma-audit / mma-review / mma-debug / mma-investigate.
   Cheaper and faster than inlining the same content N times.
-version: 4.7.7
+version: 4.7.9
 ---
 
 # mma-context-blocks

package/dist/skills/mma-debug/SKILL.md

@@ -10,7 +10,7 @@ when_to_use: >-
   read files, reproduce, trace — OR a methodology skill
   (superpowers:systematic-debugging) points at the investigation step. Delegate
   the read/reproduce/trace; the main agent stays on the hypothesis and the fix.
-version: 4.7.7
+version: 4.7.9
 ---
 
 # mma-debug

package/dist/skills/mma-delegate/SKILL.md

@@ -11,7 +11,7 @@ when_to_use: >-
   and keep main context free. If a plan file exists → use mma-execute-plan. If
   the task is audit / review / verify / debug / investigate → use the matching
   specialized skill.
-version: 4.7.7
+version: 4.7.9
 ---
 
 # mma-delegate

package/dist/skills/mma-execute-plan/SKILL.md

@@ -10,7 +10,7 @@ when_to_use: >-
   superpowers:subagent-driven-development / superpowers:executing-plans —
   workers are cheaper and don't pollute main context. Task descriptors must
   match plan headings verbatim.
-version: 4.7.7
+version: 4.7.9
 ---
 
 # mma-execute-plan

package/dist/skills/mma-explore/SKILL.md

@@ -12,7 +12,7 @@ when_to_use: >-
   out mma-investigate (internal) + mma-research (external) in parallel and
   synthesise the results yourself. DO NOT use for convergent single-answer
   questions — those are mma-investigate.
-version: 4.7.7
+version: 4.7.9
 ---
 
 # mma-explore

package/dist/skills/mma-investigate/SKILL.md

@@ -12,7 +12,7 @@ when_to_use: >-
   git-history queries. OR you are about to read 3+ files / run any grep in main
   context — that's the inline-labor-leakage anti-pattern (AP2); delegate to this
   skill instead.
-version: 4.7.7
+version: 4.7.9
 ---
 
 # mma-investigate

package/dist/skills/mma-research/SKILL.md

@@ -10,7 +10,7 @@ when_to_use: >-
   others do, what published methods exist) AND mmagent is running. Delegate the
   multi-source web/adapter research to a worker so the main context stays on
   judgment. NOT for codebase questions — those are mma-investigate.
-version: 4.7.7
+version: 4.7.9
 ---
 
 # mma-research
@@ -47,6 +47,26 @@ mean and which directions to pursue.
 
 @include _shared/auth.md
 
+## Configuration prerequisites
+
+The `mma-research` worker integrates with Semantic Scholar to search academic papers. This adapter is optional but recommended for comprehensive peer-reviewed source coverage.
+
+**Required environment variable:**
+
+```bash
+export SEMANTIC_SCHOLAR_API_KEY="your-key-from-semanticscholar.org"
+```
+
+Obtain a free API key from [Semantic Scholar API](https://www.semanticscholar.org/product/api).
+
+**Degraded behavior:**
+
+If the Semantic Scholar API key is not configured:
+- The worker continues with available adapters (arxiv, github_search, rss, brave-search)
+- Semantic Scholar queries are skipped without errors
+- Research completes successfully but may lack academic-paper coverage
+- No failure occurs; graceful fallback is automatic
+
 ## Request body
 
 ```json

package/dist/skills/mma-retry/SKILL.md

@@ -10,7 +10,7 @@ when_to_use: >-
   re-try the failed indices only. Prefer this over re-dispatching the whole
   batch or inline-retrying — it's idempotent and preserves the original batch's
   diagnostics.
-version: 4.7.7
+version: 4.7.9
 ---
 
 # mma-retry

package/dist/skills/mma-review/SKILL.md

@@ -10,7 +10,7 @@ when_to_use: >-
   AND mmagent is running. Delegate so each file reviews on its own worker; the
   main agent only decides what to merge. Review on SOURCE CODE — use mma-audit
   for prose specs / configs.
-version: 4.7.7
+version: 4.7.9
 ---
 
 # mma-review

package/dist/skills/multi-model-agent/SKILL.md

@@ -11,7 +11,7 @@ when_to_use: >-
   tasks — AND mmagent is running. Read this once, pick the matching mma-* skill,
   and delegate there. Applies equally whether the user invoked a superpowers
   methodology skill or asked directly.
-version: 4.7.7
+version: 4.7.9
 ---
 
 # multi-model-agent (router)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zhixuan92/multi-model-agent",
-  "version": "4.7.7",
+  "version": "4.7.9",
   "type": "module",
   "license": "MIT",
   "description": "Standalone HTTP server for multi-model-agent. Routes tool-invocation work to Claude, Codex, or OpenAI-compatible sub-agents with async-polling REST dispatch and installable skills for Claude Code, Gemini CLI, Codex CLI, and Cursor.",
@@ -53,7 +53,7 @@
   },
   "dependencies": {
     "@asteasolutions/zod-to-openapi": "^8.5.0",
-    "@zhixuan92/multi-model-agent-core": "^4.7.7",
+    "@zhixuan92/multi-model-agent-core": "^4.7.9",
     "gray-matter": "^4.0.3",
     "minimist": "^1.2.8",
     "proper-lockfile": "^4.1.2",