Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Delegated subagent sessions cannot load any skill: built-in worker/explore/verifier roles omit the skill tool

オープン 初心者向け
  • 何か問題がありますか？
#556 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
2/5
見積もり時間
1〜3時間
初心者へのやさしさ
76/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
typescript
領域
ai-infra-agents, developer-experience

調査の方向性

packages/local-runtime-v2/assets/agents/{worker,explore,verifier}/agent.mdを読み、ツールとスキルの設定をルートセッションと比較してください。ネイティブのskillツールとスキルカタログが、委任されたセッションにどのように公開されるかを確認してください。委任されたworkerがツールを通じてインストール済みのスキルを読み込め、explore/verifierの設定で意図されたスキル共有アクセスが許可されれば完了です。

索引モデルが issue の本文から書いたものです。

説明

Product or interface

Subagent delegation — the task tool and the built-in worker / explore / verifier roles — and the native skill tool.

Use case and problem

I use MiniMax Code as a long-running personal assistant and delegate almost all real work to subagents (task → worker / explore / verifier). Third-party skills are how I encode repeatable procedures (TDD, code review, debugging, planning), so that every delegated task follows the same process instead of reinventing it.

Delegated children currently cannot load any skill at all.

The built-in roles are defined in packages/local-runtime-v2/assets/agents/{worker,explore,verifier}/agent.md (verified at 50448abe), and their tools: lists do not contain the native skill tool:

  • worker/agent.md → read, write, edit, bash, task_query, task_output, task_stop, grep, glob, todowrite, web_fetch, website_deploy
  • explore/agent.md → bash, read, grep, glob, web_fetch, plus builtinTools: [] and skills: []
  • verifier/agent.md → read, grep, glob, bash, task_query, task_output, task_stop, web_fetch, plus builtinTools: [] and skills: []

Measured on my machine (desktop app, Windows): I ran four parallel delegated tasks with plain natural prompts — implement a function with tests, fix a failing test, review a diff, and plan a feature. Across 88 tool calls in 4 child sessions the skill tool was invoked 0 times. The tool schema actually offered to the child was:

bash, edit, glob, grep, mcp_invoke, read, tool_search, web_fetch, web_search, website_deploy, write

The only way a skill procedure reached a child was the child reading the SKILL.md file by hand, after tool_search for a skill loader returned {"hits":[],"total":0} — i.e. it went around the platform instead of through it. That works, but it is luck: it depends on the child happening to guess that the file exists, and the child never learns that the native loader exists.

Worth noting: packages/agent-tools/src/desktop/canonical-tool-policy.ts does not mention skill at all (the file is 80 lines and contains no occurrence of the string), so the policy layer is not what blocks it. The only gate is the per-role tools: list, so this looks like a one-line-per-role change rather than a policy decision.

The same gap applies to skills: [] on explore and verifier: even if the skill tool were listed, an explicit empty skills: array means there is no catalog to load from.

Desired behavior
  • A delegated child session can load a skill with the native skill tool, exactly like the root mavis session can.
  • skills: [] in explore/agent.md / verifier/agent.md either exposes the catalog, or is replaced by an explicit opt-out mechanism, so a delegated verifier can run a shared review procedure instead of improvising one.
  • Acceptance criteria: a delegated worker assigned a task that is covered by an installed skill invokes skill({ name }) for it without reading the file path by hand, and the returned SKILL.md content is visible in the child's context.
Platform

Desktop app 3.1.7.195 on Windows 11 x64. Source references are against upstream commit 50448abe (2026-10-29).

Reporter MMX UID: 500063342928973827

Alternatives and additional context

I worked around this today by creating three custom roles under agents/<name>/agent.md that add skill to tools: and drop skills: [], and delegating to those instead of the built-ins. It works, but every user has to re-create the built-in roles to get skill support, and the workaround is not discoverable from the product or from the built-in role descriptions.

Related, and worth checking in the same area: the official plugin packages that are published for MiniMax Code drop the upstream hooks/ directory, so a plugin that relies on a SessionStart hook can never fire in the desktop app. I filed that separately since it is a packaging problem rather than an agent-configuration one.

主要言語
TypeScript
スター
2.1k
フォーク
271
平均マージ
14時間 23分
マージ済み PR（30日）
35

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

MiniMax-AI/minimax-code のほかの issue

MiniMax-AI/minimax-code の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。