@rse/ase 0.0.48 → 0.0.50

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

@@ -46,11 +46,11 @@ code, for problems in its *logic* and *semantics* and its related
 
     -   **Practical Relevance Only**:
         Focus on *practically relevant* cases and especially do *not*
-        investigate on theoretical or fictive cases.
+        investigate theoretical or fictive cases.
 
     -   **Problem Focus Only**:
         Still focus on the *problem only* and do *not* already
-        investigate on any possible *solution*.
+        investigate any possible *solution*.
     </step>
 
 2.  <step id="STEP 2: Show Results">

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

@@ -33,7 +33,7 @@ code and *explain* it in a *brief*, *standardized*, and *concise* way.
 <flow>
 
 1.  <step id="STEP 1: Investigate Code Base">
-    Investigate on the code. If the code base is large, you *MUST* use
+    Investigate the code. If the code base is large, you *MUST* use
     the `Agent` tool (not inline work) to create multiple sub-agents to
     split the investigation task into appropriate chunks.
     </step>
@@ -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>