@rse/ase 0.0.49 → 0.0.50

package/dst/ase-hook.js

@@ -147,6 +147,7 @@ export default class HookCommand {
         const taskId = process.env.ASE_TASK_ID ?? "default";
         if (hasSession)
             cfg.lock(() => {
+                cfg.read();
                 cfg.set("agent.task", taskId);
                 cfg.write();
             });

package/dst/ase-statusline.js

@@ -191,8 +191,8 @@ export default class StatuslineCommand {
             .option("-m, --margin <n>", "reduce maximum used terminal width by <n> characters on each side", parseInteger("--margin"), 2)
             .option("--no-icons", "disable icons in placeholder rendering")
             .option("--no-labels", "disable labels in front of bold values")
-            .argument("[lines...]", "one or more template lines with %u %p %T %s %m %e %t %P %c %C %L %N %a %r " +
-            "%S %D %W %Q %H %X %b %g %G %d %M %V %o placeholders and <color>...</color> markup " +
+            .argument("[lines...]", "one or more template lines with %u %p %T %s %m %e %t %O %P %c %C %a %r " +
+            "%S %D %W %Q %H %X %b %g %G %d %M %V placeholders and <color>...</color> markup " +
             "(color: black, red, green, yellow, blue, magenta, cyan, white, default) " +
             "(default: single line \"%m %e %t\")")
             .action(async (lines, opts) => {

package/package.json

@@ -6,7 +6,7 @@
     "homepage":                             "http://github.com/rse/ase",
     "repository":                           { "url": "git+https://github.com/rse/ase.git", "type": "git" },
     "bugs":                                 { "url": "http://github.com/rse/ase/issues" },
-    "version":                              "0.0.49",
+    "version":                              "0.0.50",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

package/plugin/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
     "name":        "ase",
-    "version":     "0.0.49",
+    "version":     "0.0.50",
     "description": "Agentic Software Engineering (ASE)",
     "keywords":    [ "agentic", "software", "engineering" ],
     "homepage":    "https://ase.tools",

package/plugin/.github/plugin/plugin.json

@@ -1,6 +1,6 @@
 {
     "name":        "ase",
-    "version":     "0.0.49",
+    "version":     "0.0.50",
     "description": "Agentic Software Engineering (ASE)",
     "keywords":    [ "agentic", "software", "engineering" ],
     "homepage":    "https://ase.tools",

package/plugin/agents/ase-meta-chat.md

@@ -1,10 +1,43 @@
 ---
 name: ase-meta-chat
-description: "Query Foreign LLM for Chat"
-model: haiku
+description: "Query Foreign LLM for Chat via MCP Tool"
+effort: low
+tools:
+    - "mcp__chat-openai-chatgpt__chat-with-openai-chatgpt"
+    - "mcp__chat-google-gemini__chat-with-google-gemini"
+    - "mcp__chat-deepseek__chat-with-deepseek"
+    - "mcp__chat-xai-grok__chat-with-xai-grok"
 ---
 
-With a corresponding *MCP server* named `ase-chat-xxx`,
-just perform the given *queries*,
-and give back the *plain responses without any modifications*.
+1.  **Determine LLM and Query**:
+
+    Set <llm>$ARGUMENTS[0]</llm>.
+    Set <query/> to the second and following tokens in `$ARGUMENTS`.
+    You *MUST* *NOT* output anything related to this step.
+
+2.  **Determine MCP Tool**:
+
+    Use the <llm/> to determine the corresponding MCP tool <tool/>, from
+    the following list of potentially available MCP tool:
+
+    - **OpenAI ChatGPT** (<llm/> `chatgpt`): MCP <tool/> `chat-with-openai-chatgpt`
+    - **Google Gemini** (<llm/> `gemini`):   MCP <tool/> `chat-with-google-gemini`
+    - **DeepSeek** (<llm/> `deepseek`):      MCP <tool/> `chat-with-deepseek`
+    - **xAI Grok** (<llm/> `grok`):          MCP <tool/> `chat-with-xai-grok`
+
+    You *MUST* *NOT* output anything related to this step, except if the
+    MCP tool <tool/> cannot be determined (because the corresponding
+    MCP server is not available or currently disabled), just output the
+    following <template/> and immediately *STOP* processing:
+
+    <template>
+    ERROR: LLM `<llm/>` required MCP tool `<tool/>`, but this is (currently) not available.
+    </template>
+
+3.  **Call MCP Tool**:
+
+    Else, call the MCP tool with `<tool/>(content: <query/>)` and
+    then return its result *verbatim* and *without any modifications*.
+    Especially, do *NOT* add or remove any text from the agent response
+    on your own and do not interpret the result in any way.
 

package/plugin/agents/ase-meta-diagram.md

@@ -0,0 +1,60 @@
+---
+name: ase-meta-diagram
+description: "Diagram Rendering"
+tools:
+    - "mcp__plugin_ase_ase__diagram"
+effort: low
+---
+
+Your role is to render a *single* diagram, with *deterministic* and
+*clean* output. Your objective is to produce a beautifully rendered
+diagram, derived from the *Mermaid* diagram specification passed in
+`$ARGUMENTS`, which is rendered with the `diagram` tool of the `ase`
+MCP service. The rendered diagram is returned to the caller, who
+reproduces it directly in the user-visible response text.
+
+Rules
+-----
+
+-   INPUT:
+    The `$ARGUMENTS` *MUST* be treated as a *Mermaid* diagram
+    specification!
+
+    The renderer supports the following Mermaid diagram types only:
+
+    -   *structure / layout / components / dependencies* → `flowchart`
+    -   *control flow / branching / concurrency*         → `flowchart`
+    -   *state machine / states / transitions*           → `stateDiagram-v2`
+    -   *data flow / actors / messages / protocols*      → `sequenceDiagram`
+    -   *data structure / classes / methods*             → `classDiagram`
+    -   *data model / entities / relationships*          → `erDiagram`
+    -   *metrics / distributions / time series*          → `xychart-beta`
+
+    Other Mermaid diagram types are *not* supported by the renderer.
+
+-   RENDER:
+    You *MUST* always use the `diagram` tool from the `ase` MCP service
+    to render the diagram!
+
+    Pass the Mermaid diagram specification from `$ARGUMENTS` in the
+    `diagram` field, and pass a `colorMode` of `none` to always get
+    monochrome renderings. You *MUST* *NEVER* hand-draw diagrams under
+    any circumstances! Box-drawing characters (`┌`, `│`, `└`, `┐`,
+    `┘`, `─`, `┼`, `├`, `┤`, `┬`, `┴`, `╭`, `╰`), ASCII surrogates
+    (`+`, `-`, `|`), or any other attempt to draw a framed shape
+    token-by-token are *forbidden* as your own output.
+
+-   OUTPUT:
+    You *MUST* return *exclusively* the `text` output of the `diagram`
+    tool, reproduced *verbatim* into a single Markdown-fenced code block
+    (triple backticks). Do *not* return any other output, especially no
+    prose, no preamble, no summary, and no Mermaid specification.
+
+        ```
+        <text-output-of-diagram-tool/>
+        ```
+
+    The caller copies this returned block directly into the user-visible
+    response text. Returning anything other than the fenced rendered
+    block is a defect: the diagram is then effectively invisible or
+    polluted with extraneous text.

package/plugin/agents/ase-meta-search.md

@@ -1,16 +1,14 @@
 ---
 name: ase-meta-search
-description: Use the `ase-meta-search` agent to find answers to your questions!
+description: Query the Web
 tools:
     - "mcp__perplexity__perplexity_search"
     - "mcp__brave__brave_web_search"
     - "WebSearch"
-    - "WebFetch"
 model: sonnet
 effort: low
 ---
 
-Just perform the given *query*
-and give back the *plain responses*
-without any modifications.
+Just perform the given *query* `$ARGUMENTS` and
+give back the *plain responses* without any modifications.
 

package/plugin/meta/ase-skill.md

@@ -34,11 +34,13 @@ Skill Output
 
 -   *IMPORTANT*: For *Diagrams*: whenever the response needs a
     diagram (structural, control-flow, state, sequence, class,
-    entity-relationship, or metrics), you *MUST* invoke the
-    `ase-meta-diagram` skill via the `Skill` tool and follow its rules.
-    All hand-drawn ASCII frames, raw Mermaid source as a
-    substitute for a rendered block, and missing stdout
-    reproduction are defects defined by that skill.
+    entity-relationship, or metrics), you *MUST* build a Mermaid
+    specification and dispatch its rendering to the `ase-meta-diagram`
+    sub-agent via the `Agent` tool (`subagent_type: "ase:ase-meta-diagram"`),
+    then reproduce its returned fenced code block verbatim in the
+    response text. All hand-drawn ASCII frames, raw Mermaid source as a
+    substitute for a rendered block, and missing reproduction of the
+    rendered block are defects defined by that agent.
 
 -   *IMPORTANT*: For Markdown *Tables*:
 

package/plugin/package.json

@@ -6,7 +6,7 @@
     "homepage":                             "http://github.com/rse/ase",
     "repository":                           { "url": "git+https://github.com/rse/ase.git", "type": "git" },
     "bugs":                                 { "url": "http://github.com/rse/ase/issues" },
-    "version":                              "0.0.49",
+    "version":                              "0.0.50",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

package/plugin/skills/ase-arch-analyze/SKILL.md

@@ -304,11 +304,12 @@ interface quality, quality attributes, and architecture governance.
 
     - For <rendered-diagram-as-fenced-code-block/>, build a Mermaid
       specification <mermaid-spec/> for a `flowchart TB` of the
-      high-level component or layer structure and invoke the
-      `ase-meta-diagram` skill by calling the tool `Skill(skill:
-      "ase:ase-meta-diagram", args: <mermaid-spec/>)` to render it.
-      Show layers / slices / major components and their dependency
-      direction.
+      high-level component or layer structure and dispatch the rendering
+      to the `ase-meta-diagram` sub-agent by calling the tool
+      `Agent(name: "ase:ase-meta-diagram", description: "Diagram Rendering",
+      subagent_type: "ase:ase-meta-diagram", prompt: <mermaid-spec/>)`,
+      using its returned fenced code block verbatim. Show layers /
+      slices / major components and their dependency direction.
 
     - Mark detected *anomalies* directly in the Mermaid source.
       Because `!` and `?` are Mermaid special characters, *always

package/plugin/skills/ase-code-craft/SKILL.md

@@ -9,6 +9,7 @@ disable-model-invocation: false
 effort: high
 allowed-tools:
     - "Skill"
+    - "Agent"
 ---
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
@@ -222,14 +223,17 @@ permitted way to persist artifacts is via `task_save(...)`.
             it with an optional diagram <optional-diagram/> by building
             a Mermaid specification <mermaid-spec/> (e.g. `flowchart
             TB`, `stateDiagram-v2`, `sequenceDiagram`, `classDiagram`,
-            or `erDiagram`, depending on intent) and invoking the
-            `ase-meta-diagram` skill by calling the tool `Skill(skill:
-            "ase:ase-meta-diagram", args: <mermaid-spec/>)`. For
-            *current vs. proposed* comparisons, render each side as
-            a *separate* `ase-meta-diagram` invocation and stack the
-            rendered blocks *vertically* (labels `**Before:**` /
-            `**After:**`); never side-by-side. Omit <optional-diagram/>
-            entirely for simple or purely local situations.
+            or `erDiagram`, depending on intent) and dispatching the
+            rendering to the `ase-meta-diagram` sub-agent by calling
+            the tool `Agent(name: "ase:ase-meta-diagram", description:
+            "Diagram Rendering", subagent_type: "ase:ase-meta-diagram",
+            prompt: <mermaid-spec/>)`, reproducing its returned fenced
+            code block verbatim. For *current vs. proposed* comparisons,
+            render each side as a *separate* `ase-meta-diagram`
+            invocation and stack the rendered blocks *vertically*
+            (labels `**Before:**` / `**After:**`); never side-by-side.
+            Omit <optional-diagram/> entirely for simple or purely local
+            situations.
 
     6.  Indicate end of reporting by showing the following <template/>:
 

package/plugin/skills/ase-code-explain/SKILL.md

@@ -75,10 +75,12 @@ code and *explain* it in a *brief*, *standardized*, and *concise* way.
     Build a Mermaid specification <mermaid-spec/>, choosing the Mermaid
     diagram type per intent: `classDiagram` for class/method structure,
     `sequenceDiagram` for actor/message flow, or `flowchart TB` for
-    boxes-and-lines component layouts. Then invoke the
-    `ase-meta-diagram` skill by calling the tool `Skill(skill:
-    "ase:ase-meta-diagram", args: <mermaid-spec/>)` to render the
-    diagram. Do *not* hand-draw.
+    boxes-and-lines component layouts. Then dispatch the rendering to
+    the `ase-meta-diagram` sub-agent by calling the tool `Agent(name:
+    "ase:ase-meta-diagram", description: "Diagram Rendering", subagent_type:
+    "ase:ase-meta-diagram", prompt: <mermaid-spec/>)` and reproduce its
+    returned fenced code block verbatim in the response text. Do *not*
+    hand-draw.
 
     Keep your explanation *brief* and *concise*.
     Output the result with the following <template/>:

package/plugin/skills/ase-code-insight/SKILL.md

@@ -12,6 +12,7 @@ allowed-tools:
     - "Bash(uniq)"
     - "Bash(head)"
     - "Skill"
+    - "Agent"
 ---
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
@@ -93,10 +94,12 @@ Give *insights* into the project through the source code of $ARGUMENTS.
     Find all modules (or OOP classes) and build a Mermaid specification
     <mermaid-spec/> for a `flowchart TB` diagram with all modules as
     boxes and the imports between modules as the directed edges. Then
-    invoke the `ase-meta-diagram` skill by calling the tool
-    `Skill(skill: "ase:ase-meta-diagram", args: <mermaid-spec/>)`
-    to render the diagram. Do not display any further explanation except
-    for this diagram.
+    dispatch the rendering to the `ase-meta-diagram` sub-agent by
+    calling the tool `Agent(name: "ase:ase-meta-diagram", description:
+    "Diagram Rendering", subagent_type: "ase:ase-meta-diagram", prompt:
+    <mermaid-spec/>)` and reproduce its returned fenced code block
+    verbatim in the response text. Do not display any further
+    explanation except for this diagram.
     </step>
 </flow>
 

package/plugin/skills/ase-code-lint/SKILL.md

@@ -56,9 +56,9 @@ related to a set of code quality aspects.
 
     ```text
         Agent(
-            name:          "ase-code-lint",
+            name:          "ase:ase-code-lint",
             description:   "Lint Investigation",
-            subagent_type: "ase-code-lint",
+            subagent_type: "ase:ase-code-lint",
             mode:          "plan",
             prompt:        <getopt-arguments/>
         )

package/plugin/skills/ase-code-refactor/SKILL.md

@@ -9,6 +9,7 @@ disable-model-invocation: false
 effort: high
 allowed-tools:
     - "Skill"
+    - "Agent"
 ---
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
@@ -213,13 +214,16 @@ permitted way to persist artifacts is via `task_save(...)`.
             by building a Mermaid specification <mermaid-spec/>
             (e.g. `flowchart TB`, `stateDiagram-v2`, `sequenceDiagram`,
             `classDiagram`, or `erDiagram`, depending on intent) and
-            invoking the `ase-meta-diagram` skill by calling the tool
-            `Skill(skill: "ase:ase-meta-diagram", args: <mermaid-spec/>)`.
-            For *current vs. proposed* comparisons, render each side as
-            a *separate* `ase-meta-diagram` invocation and stack the
-            rendered blocks *vertically* (labels `**Before:**` /
-            `**After:**`); never side-by-side. Omit <optional-diagram/>
-            entirely for simple or purely local situations.
+            dispatching the rendering to the `ase-meta-diagram`
+            sub-agent by calling the tool `Agent(name: "ase:ase-meta-diagram",
+            description: "Diagram Rendering", subagent_type:
+            "ase:ase-meta-diagram", prompt: <mermaid-spec/>)`, reproducing
+            its returned fenced code block verbatim. For *current
+            vs. proposed* comparisons, render each side as a *separate*
+            `ase-meta-diagram` invocation and stack the rendered blocks
+            *vertically* (labels `**Before:**` / `**After:**`); never
+            side-by-side. Omit <optional-diagram/> entirely for simple
+            or purely local situations.
 
     6.  Indicate end of reporting by showing the following <template/>:
 

package/plugin/skills/ase-code-resolve/SKILL.md

@@ -9,6 +9,7 @@ disable-model-invocation: false
 effort: high
 allowed-tools:
     - "Skill"
+    - "Agent"
 ---
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
@@ -152,10 +153,13 @@ permitted way to persist artifacts is via `task_save(...)`.
           visualize it with an optional diagram <optional-diagram/> by
           building a Mermaid specification <mermaid-spec/> (e.g. `flowchart
           TB`, `stateDiagram-v2`, `sequenceDiagram`, `classDiagram`, or
-          `erDiagram`, depending on intent) and invoking the
-          `ase-meta-diagram` skill by calling the tool `Skill(skill:
-          "ase:ase-meta-diagram", args: <mermaid-spec/>)`. Omit
-          <optional-diagram/> entirely for simple or purely local situations.
+          `erDiagram`, depending on intent) and dispatching the rendering
+          to the `ase-meta-diagram` sub-agent by calling the tool
+          `Agent(name: "ase:ase-meta-diagram", description: "Diagram
+          Rendering", subagent_type: "ase:ase-meta-diagram", prompt:
+          <mermaid-spec/>)`, reproducing its returned fenced code block
+          verbatim. Omit <optional-diagram/> entirely for simple or
+          purely local situations.
 
 2.  **Investigate Code Base**:
 
@@ -259,13 +263,16 @@ permitted way to persist artifacts is via `task_save(...)`.
             by building a Mermaid specification <mermaid-spec/>
             (e.g. `flowchart TB`, `stateDiagram-v2`, `sequenceDiagram`,
             `classDiagram`, or `erDiagram`, depending on intent) and
-            invoking the `ase-meta-diagram` skill by calling the tool
-            `Skill(skill: "ase:ase-meta-diagram", args: <mermaid-spec/>)`.
-            For *current vs. proposed* comparisons, render each side as
-            a *separate* `ase-meta-diagram` invocation and stack the
-            rendered blocks *vertically* (labels `**Before:**` /
-            `**After:**`); never side-by-side. Omit <optional-diagram/>
-            entirely for simple or purely local situations.
+            dispatching the rendering to the `ase-meta-diagram`
+            sub-agent by calling the tool `Agent(name: "ase:ase-meta-diagram",
+            description: "Diagram Rendering", subagent_type:
+            "ase:ase-meta-diagram", prompt: <mermaid-spec/>)`, reproducing
+            its returned fenced code block verbatim. For *current
+            vs. proposed* comparisons, render each side as a *separate*
+            `ase-meta-diagram` invocation and stack the rendered blocks
+            *vertically* (labels `**Before:**` / `**After:**`); never
+            side-by-side. Omit <optional-diagram/> entirely for simple
+            or purely local situations.
 
     6.  Indicate end of reporting by showing the following <template/>:
 

package/plugin/skills/ase-docs-proofread/SKILL.md

@@ -57,9 +57,9 @@ documents.
 
     ```text
         Agent(
-            name:          "ase-docs-proofread",
+            name:          "ase:ase-docs-proofread",
             description:   "Proofread Investigation",
-            subagent_type: "ase-docs-proofread",
+            subagent_type: "ase:ase-docs-proofread",
             mode:          "plan",
             prompt:        <getopt-arguments/>
         )

package/plugin/skills/ase-meta-chat/SKILL.md

@@ -2,64 +2,48 @@
 name: ase-meta-chat
 argument-hint: "<llm> <query>"
 description: >
-    Query foreign LLM for Chat.
+    Query foreign LLM for chat.
     Use this skill if a foreign LLM like OpenAI ChatGPT, Google Gemini,
     DeepSeek or xAI Grok should be queried with a single chat message.
 user-invocable: true
 disable-model-invocation: false
-context: fork
 effort: low
 allowed-tools:
-    - "mcp__chat-openai-chatgpt"
-    - "mcp__chat-google-gemini"
-    - "mcp__chat-deepseek"
-    - "mcp__chat-xai-grok"
-    - "Task"
     - "Agent"
 ---
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Query Foreign LLMs for Chat
-===========================
+Query Foreign LLM for Chat
+==========================
 
 <skill name="ase-meta-chat">
-Query Foreign LLMs for Chat
+Query Foreign LLM for Chat
 </skill>
 
+<role>
 Your role is to act as a proxy to query a foreign LLM for a single chat message.
+</role>
 
 <objective>
 Query foreign LLM for: <query>$ARGUMENTS</query>
 </objective>
 
-<flow>
-
-1.  <step id="STEP 1: Select LLMs">
-    Use the *first word* of the following <query/> for selecting the
-    foreign LLMs to query, and their corresponding MCP servers, from the
-    following list:
-
-    - **OpenAI ChatGPT**: via MCP server `chat-openai-chatgpt`
-    - **Google Gemini**:  via MCP server `chat-google-gemini`
-    - **DeepSeek**:       via MCP server `chat-deepseek`
-    - **xAI Grok**:       via MCP server `chat-xai-grok`
-    </step>
-
-2.  <step id="STEP 2: Spawn Agents">
-    Spawn a *sub-task* with the companion `ase-meta-chat` *agent* (and
-    not this *skill*, but the agent of the same name) for the selected
-    foreign LLMs, and pass the *second and all remaining* words of the
-    following <query/> as the query for the selected LLM.
-    </step>
-
-3.  <step id="STEP 3: Return Responses">
-    Return the *plain response* of the `ase-meta-chat` agent 1:1 and
-    *without any modifications*. Especially, do *NOT* add or remove any
-    text from the agent response on your own and do not interpret the
-    result in any way.
-    </step>
-
-</flow>
+1.  You *MUST* *NOT* output anything in this step.
+    Just call the underlying agent with the following tool:
+
+    ```text
+        Agent(
+            name:          "ase:ase-meta-chat",
+            description:   "Query Foreign LLM for Chat",
+            subagent_type: "ase:ase-meta-chat",
+            prompt:        <query/>
+        )
+    ```
+
+2.  Output the *plain response* of the `ase:ase-meta-chat` agent
+    *verbatim* and *without any modifications*. Especially, do *NOT* add or
+    remove any text from the agent response on your own and do not interpret
+    the result in any way.
 

package/plugin/skills/ase-meta-quorum/SKILL.md

@@ -21,7 +21,9 @@ Query Multiple AIs for Quorum Answer
 Query Multiple AIs for Quorum Answer
 </skill>
 
+<role>
 Your role is an *expert-level assistant*.
+</role>
 
 <objective>
 Find a *quorum answer* on an arbitrary question,
@@ -29,11 +31,12 @@ by querying *multiple* AIs for an *optimal consensus*.
 </objective>
 
 <flow>
-1.  <step id="STEP 1: Determine Own Answer">
-    Determine your own answer.
-    For yourself (Anthropic Claude), first answer the following <query/> in advance:
 
-    <query>
+1.  <step id="STEP 1: Preview Own Answer">
+
+    Prepare the LLM query by setting <query/> to the following <template/>:
+
+    <template>
     $ARGUMENTS.
     Please respond with facts and very concise and brief only,
     usually with just 1 to 7 corresponding bullet points and with short sentences.
@@ -41,40 +44,60 @@ by querying *multiple* AIs for an *optimal consensus*.
     Beside bullet points, do not provide any additional explanations.
     Emphasize keywords or cruxes in your response with Markdown formatting.
     Format code parts with Markdown formatting.
-    </query>
-    </step>
+    </template>
 
-2.  <step id="STEP 2: Preview Own Answer">
-    Show your own answer as a sneak preview.
-    For this, use the following output <template/>:
+    For yourself (Anthropic Claude), first answer this <query/> in
+    advance yourself by showing your own answer to the query as a sneak
+    preview. For this, output the following <template/>:
 
     <template>
     **Anthropic Claude** (sneak preview in advance):
     - [...]
     - [...]
     </template>
+
     </step>
 
-3.  <step id="STEP 3: Query Foreign AIs">
-    For each of the following foreign AIs and their potentially
-    available, given, corresponding MCP servers, use a *sub-task* and
-    the `ase-meta-chat` *agent* to perform the above same <query/> zero
-    or more times and in *parallel* again:
+2.  <step id="STEP 2: Query Foreign AIs">
+
+    <define name="agent">
+    Call the `Agent` tool:
+
+    ```text
+        Agent(
+            name:          "ase:ase-meta-chat",
+            description:   "Query Foreign LLM: <arg1/>",
+            subagent_type: "ase:ase-meta-chat",
+            prompt:        "<arg2/> <query/>"
+        )
+    ```
+
+    </define>
+
+    <expand name="agent" arg1="OpenAI ChatGPT" arg2="chatgpt"></expand>
+    <expand name="agent" arg1="Google Gemini"  arg2="gemini"></expand>
+    <expand name="agent" arg1="DeepSeek"       arg2="deepseek"></expand>
+    <expand name="agent" arg1="xAI Grok"       arg2="grok"></expand>
 
-    - OpenAI ChatGPT: `chat-openai-chatgpt`
-    - Google Gemini:  `chat-google-gemini`
-    - DeepSeek:       `chat-deepseek`
-    - xAI Grok:       `chat-xai-grok`
+    You *MUST* *NOT* output anything in this step.
 
-    Silently skip those AIs where the corresponding MCP server is not available.
     </step>
 
-4.  <step id="STEP 4: Summarize Responses">
-    Summarize all responses, of both yourself and all available MCP servers,
-    with just 1 to 7 corresponding bullet points and with short sentences.
+3.  <step id="STEP 3: Summarize Responses">
+
+    Agents which returned a response with an `ERROR:` prefix are
+    silently skipped and are treatd as not available.
+
+    Summarize all responses, of both yourself and all available agents
+    with just 1 to 7 corresponding bullet points and with short
+    sentences.
+
+    You *MUST* *NOT* output anything in this step.
+
     </step>
 
-5.  <step id="STEP 5: Determine Consensus Rating">
+4.  <step id="STEP 4: Determine Consensus Rating">
+
     Determine, on a Likert scale of 0..<n/>, the amount of the overall
     consensus <c/> of all the responses. The <n/> is the *total number of
     responders* (yourself plus all available foreign AIs above).
@@ -85,11 +108,16 @@ by querying *multiple* AIs for an *optimal consensus*.
     formatted as `(disagreement: <ai/>, <ai/>, [...])` where <ai/> is a
     name of an AI which disagreed with the consensus. Else, if all AIs
     agree, set <disagreement></disagreement>.
+
+    You *MUST* *NOT* output anything in this step.
+
     </step>
 
-6.  <step id="STEP 6: Show Results">
-    Finally show the summary, the consensus and the complete and unmodified responses
-    of yourself and each of the MCP servers, based on the following output <template/>:
+5.  <step id="STEP 5: Show Results">
+
+    Finally show the summary, the consensus and the complete and
+    unmodified responses of yourself and each of the MCP servers, based
+    on the following output <template/>:
 
     <template>
     **QUESTION**:
@@ -123,6 +151,9 @@ by querying *multiple* AIs for an *optimal consensus*.
     </template>
 
     In this output, remove the sections of those AIs which were not available.
+    You *MUST* *NOT* output any further explanations yourself.
+
     </step>
+
 </flow>
 

package/plugin/skills/ase-meta-search/SKILL.md

@@ -10,9 +10,7 @@ effort: low
 allowed-tools:
     - "mcp__perplexity__perplexity_search"
     - "mcp__brave__brave_web_search"
-    - "WebSearch"
-    - "WebFetch"
-    - "Task"
+    - "Agent"
 ---
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
@@ -25,7 +23,9 @@ Search the Internet/Web
 Search the Internet/Web
 </skill>
 
+<role>
 Your role is an expert-level *web specialist*.
+</role>
 
 <objective>
 Your objective is to *search* the *Internet*/*Web* for the following query:
@@ -33,20 +33,46 @@ Your objective is to *search* the *Internet*/*Web* for the following query:
 </objective>
 
 <flow>
-1.  <step id="STEP 1: QUERY SERVICES">
-    If the MCP tool `mcp__perplexity__perplexity_search` is available, send <query/> to it
-    via a first *sub-task* and our companion `ase-meta-search` *agent*.
 
-    If the MCP tool `mcp__brave__brave_web_search` is available, send <query/> to it
-    via a second *sub-task* and our companion `ase-meta-search` *agent*.
+1.  <step id="STEP 1: Query Search Services">
+
+    <define name="agent">
+    ```text
+        Agent(
+            name:          "ase:ase-meta-search",
+            description:   "Query Web Search Service",
+            subagent_type: "ase:ase-meta-search",
+            prompt:        <content/>
+        )
+    ```
+    </define>
+
+    If the MCP tool `mcp__perplexity__perplexity_search` is available, call:
+    <expand name="agent">
+        Call the MCP tool `mcp__perplexity__perplexity_search(query: "<query/>")`
+    </expand>
+
+    If the MCP tool `mcp__brave__brave_web_search` is available, call:
+    <expand name="agent">
+        Call the MCP tool `mcp__brave__brave_web_search(query: "<query/>")`
+    </expand>
+
+    <expand name="agent">
+        Call the tool `WebSearch(query: "<query/>")`
+    </expand>
 
-    Send <query/> to the built-in tool `WebSearch`
-    via a third *sub-task* and our companion `ase-meta-search` *agent*.
     </step>
 
-2.  <step id="STEP 2: CONSOLIDATE ANSWERS">
-    Consolidate all responses from the `ase-meta-search` *agents*
-    into a single response and output it without giving any further explanations.
+2.  <step id="STEP 2: Consolidate Search Answers">
+
+    Consolidate all responses from the `ase:ase-meta-search` agents
+    calls above into a single response and output it without giving any
+    further explanations.
+
+    For the consolidation, do *NOT* remove any orginal information,
+    just *MERGE* all overlapping information.
+
     </step>
+
 </flow>
 

package/plugin/skills/ase-meta-diagram/SKILL.md

@@ -1,101 +0,0 @@
----
-name: ase-meta-diagram
-description: >
-    Render diagrams via the `diagram` tool of the `ase` MCP service.
-    *Always use* when you have to *visualize*
-    structure/layout/components/dependencies as Flowchart,
-    control-flow/branching/concurrency as Flowchart,
-    state-machine/states/transitions as a UML State Diagram,
-    data-flow/actors/messages/protocols as a UML Sequence Diagram,
-    data-structure/classes/methods as a UML Class Diagram,
-    data-model/entities/relationships as an ER Diagram, or
-    metrics/distributions/time-series as XY-Charts.
-user-invocable: false
-disable-model-invocation: false
-effort: low
-allowed-tools:
-    - "mcp__plugin_ase_ase__diagram"
----
-
-Render Diagrams
-===============
-
-Your role is to render *every* diagram in the current session, with
-*deterministic* and *clean* output. For this, your objective is to
-produce a beautifully rendered diagram that the user can read directly
-in the response text, derived from a *Mermaid* diagram specification,
-which is rendered with the `diagram` tool of the `ase` MCP service.
-
-Rules
------
-
--   WHEN NOT:
-    You *MUST* *NEVER* hand-draw diagrams under any circumstances!
-
-    Box-drawing characters (`┌`, `│`, `└`, `┐`, `┘`, `─`, `┼`, `├`,
-    `┤`, `┬`, `┴`, `╭`, `╰`), ASCII surrogates (`+`, `-`, `|`), or any
-    other attempt to draw a framed shape token-by-token are *forbidden*
-    as your own diagram output.
-
--   WHEN:
-    You *MUST* always use the `diagram` tool from the `ase` MCP service,
-    whenever a diagram should be drawn!
-
-    Every diagram in the output *MUST* originate from a `diagram`
-    MCP tool call, with Mermaid diagram specification passed in the
-    `diagram` field, made in the *same* session response turn. Also,
-    pass a `colorMode` of `none` to always get monochrome renderings.
-
--   INPUT:
-    For describing the diagrams, you *MUST* use the *Mermaid* diagram
-    specification language!
-
-    Use the following Mermaid diagram types per intent:
-
-    -   *structure / layout / components / dependencies* → `flowchart`
-    -   *control flow / branching / concurrency*         → `flowchart`
-    -   *state machine / states / transitions*           → `stateDiagram-v2`
-    -   *data flow / actors / messages / protocols*      → `sequenceDiagram`
-    -   *data structure / classes / methods*             → `classDiagram`
-    -   *data model / entities / relationships*          → `erDiagram`
-    -   *metrics / distributions / time series*          → `xychart-beta`
-
-    Other Mermaid diagram types are *not* supported by the renderer
-    and hence should *not* be specified!
-
--   OUTPUT:
-    You *MUST* reproduce the `text` output of the `diagram` tool from
-    the `ase` MCP service in the response text! Do not produce any other
-    output, especially no explanations.
-
-    In other words, after the `diagram` tool call completes, the
-    skill *MUST* copy the tool's `text` result *verbatim* into a
-    Markdown-fenced code block (triple backticks), directly placed
-    in the response text immediately after the MCP tool call — the
-    user reads the Markdown fenced block in the response, not the
-    (truncated) tool call display. Emitting only the tool call without
-    the reproduction of the `text` output is a defect: the diagram is
-    then effectively invisible.
-
--   NOTICE 1:
-    You *MUST* *NEVER* emit the plain Mermaid diagram specification, as
-    it is just an intermediate format for driving the rendering process!
-
--   NOTICE 2:
-    You *SHOULD* keep diagrams narrow!
-
-    The renderer's horizontal extent scales with siblings per row, node
-    label lengths, and inter-node padding. Limit *≤6 siblings per row*
-    and group further items into nested `subgraph` hierarchies; keep
-    *node labels* *≤20 chars* (abbreviate long names, drop adjectives).
-
--   NOTICE 3:
-    You *SHOULD* stack diagrams vertically!
-
-    For *comparison diagrams* (e.g., *current vs. proposed*, *before
-    vs. after*), render each side as a *separate* Mermaid diagram
-    specification via the `diagram` tool from the `ase` MCP service, and
-    then stack the two rendered blocks *vertically* — each preceded by
-    a bold label (`**BEFORE:**` / `**AFTER:**`, or similar). Do *not*
-    attempt side-by-side layout.
-