@rse/ase 0.9.9 → 0.9.11

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

@@ -209,10 +209,10 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         anything else in this step:
 
         <template>
-        ●   **APPROACH A<n/>**<annotation/>: *<summary/>*
+        ●   **APPROACH A<n/>**<annotation/>: **<summary/>**
         ○   [...]
-        ⊕   **PRO**: [...]
-        ⊖   **CON**: [...]
+        ⊕   *PRO*: [...]
+        ⊖   *CON*: [...]
         </template>
 
         Hints:
@@ -230,18 +230,19 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
 
     7.  <if condition="<getopt-option-auto/> is not `true`">
 
-        You *MUST* use the custom `custom-dialog` and *NOT* the
-        `AskUserQuestion`-based `user-dialog` to let the *user
-        interactively choose* the preferred approach A<n/>.
+        In the following, you *MUST* *NOT* use the <user-dialog-tool/>
+        tool! Instead, you *MUST* just show a custom output, let the
+        user enter input, and then you set the result accordingly.
 
-        Per approach A<n/>, use the option `A<n/>: <short-summary/>`
-        where <short-summary/> is an ultra brief summary of the approach
-        A<n/>. For your recommended approach, use
-        `A<n/>: ⚝ **RECOMMENDATION** ⚝: <short-summary/>` instead.
+        Let the user choose the preferred approach A<n/> by raising
+        a question with the following custom dialog, where per
+        approach A<n/>, you determine an ultra brief summary
+        <short-summary/> and then use the answer option `A<n/>:
+        ⚝ **RECOMMENDATION** ⚝: <short-summary/>` for your
+        recommended approach plus zero or more answer options `A<n/>:
+        <short-summary/>` for all other approaches:
 
-        Now raise the user dialog:
-
-        <expand name="custom-dialog">
+        <expand name="custom-dialog" arg1="--no-other">
             Select Approach: Select your preferred refactoring approach to follow?
             A<n/>: <short-summary/>
             [...]
@@ -331,18 +332,21 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             Hand off to `ase-task-edit`.
             <if condition="<head/> is equal `EDIT`">
                 Consume the head: set <getopt-option-next/> to the remaining
-                tokens (joined back with `,`, or `none` if empty).
+                tokens (joined back with `,`, or `none` if empty). `EDIT`
+                is this skill's own dispatch token, *not* part of
+                `ase-task-edit`'s `--next` vocabulary, so it must be
+                stripped here rather than forwarded.
             </if>
             All remaining tokens are `ase-task-edit`'s own vocabulary
             and are forwarded verbatim, so `ase-task-edit` consumes its
-            head itself.
+            own head itself.
             <if condition="<getopt-option-next/> is not equal `none`">
                 Set <args><args/> --next <getopt-option-next/></args>
             </if>
             Then call the tool `Skill(skill: "ase:ase-task-edit", args: "<args/>")`.
             </else>
 
-    <step>
+    </step>
 
 </flow>
 

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

@@ -60,14 +60,15 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
     1.  If <problem/> matches the regexp `^[PT]\d+$` (i.e. a bare issue
         identifier like `P1`, `P2`, `T1`, `T2`, ...),
         set <problem-id><problem/></problem-id> and
-        <ase-task-id><problem/></ase-task-id>, call the `ase_task_id(id:
-        "<ase-task-id/>", session: "<ase-session-id/>")` tool from the
-        `ase` MCP server to implicitly switch the task, and then
-        call the `ase_kv_get(key: "ase-issue-<problem-id/>")` tool of
+        <ase-task-id><problem/></ase-task-id>, then call the
+        `ase_kv_get(key: "ase-issue-<problem-id/>")` tool of
         the `ase` MCP server to retrieve the previously persisted
         problem description. If the returned `text` is non-empty, set
-        <problem><text/></problem>, otherwise complain to the user that
-        no analyzer result exists for <problem-id/> and stop processing.
+        <problem><text/></problem> and call the `ase_task_id(id:
+        "<ase-task-id/>", session: "<ase-session-id/>")` tool from the
+        `ase` MCP server to implicitly switch the task, otherwise
+        complain to the user that no analyzer result exists for
+        <problem-id/> and stop processing.
 
     2.  <if condition="
             <problem/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$`
@@ -259,10 +260,10 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
         anything else in this step:
 
         <template>
-        ●   **APPROACH A<n/>**<annotation/>: *<summary/>*
+        ●   **APPROACH A<n/>**<annotation/>: **<summary/>**
         ○   [...]
-        ⊕   **PRO**: [...]
-        ⊖   **CON**: [...]
+        ⊕   *PRO*: [...]
+        ⊖   *CON*: [...]
         </template>
 
         Hints:
@@ -280,18 +281,19 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
 
     7.  <if condition="<getopt-option-auto/> is not `true`">
 
-        You *MUST* use the custom `custom-dialog` and *NOT* the
-        `AskUserQuestion`-based `user-dialog` to let the *user
-        interactively choose* the preferred approach A<n/>.
+        In the following, you *MUST* *NOT* use the <user-dialog-tool/>
+        tool! Instead, you *MUST* just show a custom output, let the
+        user enter input, and then you set the result accordingly.
 
-        Per approach A<n/>, use the option `A<n/>: <short-summary/>`
-        where <short-summary/> is an ultra brief summary of the approach
-        A<n/>. For your recommended approach, use
-        `A<n/>: ⚝ **RECOMMENDATION** ⚝: <short-summary/>` instead.
+        Let the user choose the preferred approach A<n/> by raising
+        a question with the following custom dialog, where per
+        approach A<n/>, you determine an ultra brief summary
+        <short-summary/> and then use the answer option `A<n/>:
+        ⚝ **RECOMMENDATION** ⚝: <short-summary/>` for your
+        recommended approach plus zero or more answer options `A<n/>:
+        <short-summary/>` for all other approaches:
 
-        Now raise the user dialog:
-
-        <expand name="custom-dialog">
+        <expand name="custom-dialog" arg1="--no-other">
             Select Approach: Select your preferred resolution approach to follow?
             A<n/>: <short-summary/>
             [...]
@@ -388,18 +390,21 @@ permitted way to persist artifacts is via `ase_task_save(...)`.
             Hand off to `ase-task-edit`.
             <if condition="<head/> is equal `EDIT`">
                 Consume the head: set <getopt-option-next/> to the remaining
-                tokens (joined back with `,`, or `none` if empty).
+                tokens (joined back with `,`, or `none` if empty). `EDIT`
+                is this skill's own dispatch token, *not* part of
+                `ase-task-edit`'s `--next` vocabulary, so it must be
+                stripped here rather than forwarded.
             </if>
             All remaining tokens are `ase-task-edit`'s own vocabulary
             and are forwarded verbatim, so `ase-task-edit` consumes its
-            head itself.
+            own head itself.
             <if condition="<getopt-option-next/> is not equal `none`">
                 Set <args><args/> --next <getopt-option-next/></args>
             </if>
             Then call the tool `Skill(skill: "ase:ase-task-edit", args: "<args/>")`.
             </else>
 
-    <step>
+    </step>
 
 </flow>
 

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

@@ -129,7 +129,7 @@ Analyze documents for spelling, punctuation, or grammar errors
             ```diff
             --- <file/> (original)
             +++ <file/> (corrected)
-            @@ -<old-start/>,<n/> +<new-start/>,<m/> @@
+            @@ -<old-start/>,<old-count/> +<new-start/>,<new-count/> @@
              <context-before/>
             -<old-text/>
             +<new-text/>
@@ -143,10 +143,10 @@ Analyze documents for spelling, punctuation, or grammar errors
                 the line of <context-before/> (one before <line/>).
             -   The <new-start/> is the same as <old-start/> (the unchanged
                 <context-before/> line shares the same start in both files).
-            -   The <n/> is the total number of old-side hunk lines, i.e.,
+            -   The <old-count/> is the total number of old-side hunk lines, i.e.,
                 the number of lines in <context-before/>, <old-text/>, and
                 <context-after/> combined.
-            -   The <m/> is the total number of new-side hunk lines, i.e.,
+            -   The <new-count/> is the total number of new-side hunk lines, i.e.,
                 the number of lines in <context-before/>, <new-text/>, and
                 <context-after/> combined.
 
@@ -154,11 +154,11 @@ Analyze documents for spelling, punctuation, or grammar errors
 
         4.  <if condition="<getopt-option-auto/> is not 'true'">
 
-            Let the *user interactively choose* what to do as the next
-            step. For this you *MUST* use the custom `custom-dialog` and
-            not the `AskUserQuestion` based `user-dialog`:
+            In the following, you *MUST* *NOT* use the <user-dialog-tool/>
+            tool! Instead, you *MUST* just show a custom output, let the
+            user enter input, and then you set the result accordingly.
 
-            <expand name="custom-dialog">
+            <expand name="custom-dialog" arg1="--other">
                 CORRECTION: How would you like to proceed with this proposed correction?
                 ACCEPT: Apply the proposed correction.
                 REJECT: Skip this proposed correction.
@@ -188,9 +188,15 @@ Analyze documents for spelling, punctuation, or grammar errors
 
                 Generate a *new* proposal for the *same* <item/>,
                 incorporating the user's free-text hint from <result/>
-                after the "OTHER:" prefix, and *go back* to substep 2 of
-                this `for`-iteration. There is *no* cap on refinement rounds -
-                keep refining until the user picks `ACCEPT` or `REJECT`.
+                after the "OTHER:" prefix. *Reassign* <description/>,
+                <old-text/>, and <new-text/> to reflect this refined
+                proposal (<old-text/> stays anchored to the existing text
+                at <file/>:<line/>; <new-text/> and <description/> carry the
+                refinement) so the subsequent rendering and any `Edit` use
+                the new proposal rather than the original. Then *go back* to
+                substep 2 of this `for`-iteration. There is *no* cap on
+                refinement rounds - keep refining until the user picks
+                `ACCEPT` or `REJECT`.
 
                 </if>
 

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

@@ -1,6 +1,6 @@
 ---
 name: ase-meta-brainstorm
-argument-hint: "[--help|-h] [--max-clarify|-c=3] [--min-ideas|-i=12] [--min-rank|-r=7] [--max-shortlist|-s=4] <topic>"
+argument-hint: "[--help|-h] [--max-clarify|-c <num>] [--min-ideas|-i <num>] [--min-rank|-r <num>] [--max-shortlist|-s <num>] <topic>"
 description: >
     Collaboratively brainstorm a topic by diverging on ideas, converging
     through clustering and scoring, and distilling a shortlist with
@@ -121,16 +121,17 @@ Honor the following tenets throughout the brainstorming:
             question <question-M/>, and let the user select the
             <answer-M/> out of the candidate answers <answer-M-K/> (leave
             out the answer lines of those candidate answers you have
-            not determined). For this you *MUST* use the custom
-            `custom-dialog` and *NOT* the `AskUserQuestion` based
-            "user-dialog":
+            not determined).
 
-            <expand name="custom-dialog">
+            In the following, you *MUST* *NOT* use the <user-dialog-tool/>
+            tool! Instead, you *MUST* just show a custom output, let the
+            user enter input, and then you set the result accordingly.
+
+            <expand name="custom-dialog" arg1="--other">
                 <facet-M/>: <question-M/>
-                <answer-M-1/>: (first grounded candidate answer)
-                <answer-M-2/>: (second grounded candidate answer)
-                <answer-M-3/>: (third grounded candidate answer)
-                <answer-M-4/>: (fourth grounded candidate answer)
+                <answer-M-1/>: (grounded candidate answer 1)
+                <answer-M-2/>: (grounded candidate answer 2)
+                [...]
             </expand>
 
         4.  Dispatch on the dialog <result/>:
@@ -214,15 +215,30 @@ Honor the following tenets throughout the brainstorming:
 
         <template>
         <ase-tpl-bullet-secondary/> **IDEA CLUSTER <C/>/<c/>**: <cluster-C/> - <cluster-summary-C/>,
-        **IDEAS**: <N/>, <M/>[, ...]
+        **IDEAS**: <idea-index-C/>
         </template>
 
+        Here, <idea-index-C/> is the comma-separated list of the indices
+        <N/> of those retained ideas <idea-N/> that belong to cluster
+        <cluster-C/> (e.g. `2, 5, 9`).
+
     2.  *Score*: for each retained idea <idea-N/> in the clusters, rank its *fit* against the
         purpose and constraints on a Likert scale of 0 (poor) to 10
         (excellent), considering *value*, *uniqueness*, *risk*, and
         *alignment with the existing code base*. Keep only ideas in the
         clusters with a rank of at least <getopt-option-min-rank/>.
 
+        If *no* idea meets the <getopt-option-min-rank/> floor, the floor
+        filter would empty the set and leave the downstream steps without
+        any options. In this case, *disregard* the floor and instead keep
+        the up-to-<getopt-option-max-shortlist/> highest-ranked ideas, and
+        output the following <template/> to flag that even the strongest
+        ideas fall below the bar:
+
+        <template>
+        <ase-tpl-bullet-signal/> **NOTICE**: no idea reached the minimum rank of <getopt-option-min-rank/>/10 - shortlisting the highest-ranked ideas regardless.
+        </template>
+
     3.  From the scored ideas <idea-N/>, distill a *shortlist* of the top
         <getopt-option-max-shortlist/> options, sorted by rank from highest to lowest.
 

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

@@ -16,11 +16,16 @@ allowed-tools:
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-meta-changelog">
 Update ChangeLog Entries
 </skill>
 
+<expand name="getopt" arg1="ase-meta-changelog">
+    $ARGUMENTS
+</expand>
+
 <objective>
 Help to complete, consolidate and sort *ChangeLog* entries of the most
 recent *ChangeLog* section, based on underlying *Git* commits and staged
@@ -81,11 +86,17 @@ Processing
     the Git *commits* plus the currently already staged changes in the Git
     *index*, but *ignore* the Git *stash* and still unstaged changes.
 
-    For finding the corresponding Git *commits*, use the `N.M.K` from the
-    *second* level-2 header in the *ChangeLog* file as the corresponding
-    Git tag and then check all Git commits between `HEAD` and this tag
-    with the command `git log N.M.K..HEAD --numstat --pretty=format:'%h:
-    %s'`.
+    For finding the corresponding Git *commits*, first determine the
+    correct baseline Git tag. Take the `N.M.K` from the *first* (most
+    recent) level-2 header in the *ChangeLog* file and check whether a
+    corresponding Git tag already exists with the command `git tag --list
+    N.M.K`. If this command produces *no* output, the first section is
+    still in-progress/untagged, so use the `N.M.K` from the *second*
+    level-2 header as the baseline tag instead. If this command *does*
+    produce output, the first section is already released/tagged, so use
+    the `N.M.K` from the *first* level-2 header as the baseline tag. Then
+    check all Git commits between `HEAD` and this baseline tag with the
+    command `git log N.M.K..HEAD --numstat --pretty=format:'%h: %s'`.
 
     For finding the corresponding staged Git *changes* in the Git
     *index*, use the command `git diff --cached --numstat`, but silently

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

@@ -14,13 +14,18 @@ allowed-tools:
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-meta-chat">
 Query Foreign LLM for Chat
 </skill>
 
+<expand name="getopt" arg1="ase-meta-chat">
+    $ARGUMENTS
+</expand>
+
 <objective>
-Query foreign LLM for: <query>$ARGUMENTS</query>
+Query foreign LLM for: <query><getopt-arguments/></query>
 </objective>
 
 1.  You *MUST* *NOT* output anything in this step.

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

@@ -12,11 +12,16 @@ allowed-tools:
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-meta-commit">
 Git Commit
 </skill>
 
+<expand name="getopt" arg1="ase-meta-commit">
+    $ARGUMENTS
+</expand>
+
 <objective>
 Help to *craft* a *concise commit message* for the
 currently staged Git changes.

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

@@ -2,7 +2,7 @@
 name: ase-meta-diaboli
 argument-hint: "[--help|-h] [--count|-c <count>] <thesis>"
 description: >
-    Challenge a thesis by playing "Devil’s Advocate" (latin: "Advocatus
+    Challenge a thesis by playing "Devil’s Advocate" (Latin: "Advocatus
     Diaboli"). Use when the user wants a thesis or statement
     relentlessly challenged or criticised.
 user-invocable: true
@@ -25,7 +25,7 @@ effort: xhigh
 </expand>
 
 <objective>
-    Play "Devil’s Advocate" (latin: "Advocatus Diaboli") by relentlessly
+    Play "Devil’s Advocate" (Latin: "Advocatus Diaboli") by relentlessly
     challenging or criticising the thesis: <thesis><getopt-arguments/></thesis>
 </objective>
 
@@ -48,7 +48,7 @@ to <getopt-option-count/>; if <getopt-option-count/> is *non-numeric* or
 2.  <step id="STEP 2: Determine Anti-Theses">
 
     Reason on the thesis in <thesis/> by playing *Devil's Advocate*
-    (latin: *Advocatus Diaboli*) by relentlessly challenging or
+    (Latin: *Advocatus Diaboli*) by relentlessly challenging or
     criticising it with the help of the following tenets:
 
     -   **Steelmanning**:
@@ -88,7 +88,7 @@ to <getopt-option-count/>; if <getopt-option-count/> is *non-numeric* or
 
     -   **Push the Logic to its Conclusion**:
         Ask "If we accept this, then what?" and apply "Reduction to
-        Absurdity" (latin: "Reductio Ad Absurdum"), because this disproves
+        Absurdity" (Latin: "Reductio Ad Absurdum"), because this disproves
         the thesis by showing that accepting it leads to a logically
         absurd, contradictory, or impossible conclusion.
 
@@ -120,7 +120,11 @@ to <getopt-option-count/>; if <getopt-option-count/> is *non-numeric* or
     Anti-Theses or Counter-Arguments until you EITHER have found at
     least <count/> Anti-Theses or Counter-Arguments with at least a rank
     of 7 OR you have already checked a total of <count/> x 5 Anti-Theses
-    or Counter-Arguments.
+    or Counter-Arguments. If the second condition is reached first and
+    fewer than <count/> Anti-Theses or Counter-Arguments reached a rank
+    of at least 7, nevertheless surface the <count/> highest-ranked ones
+    found so far, because <count/> is the *minimum* number of
+    Anti-Theses to surface.
 
     Then, for the top-<count/> highest-ranked Anti-Theses or
     Counter-Arguments, sort them by their rank from highest to lowest,

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

@@ -109,7 +109,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
         3.  For each discovered *intent group*, emit the following row
             <template/>, where <intent/> is the intent label, <changes/>
-            is the total number of lines changes per feature in format
+            is the total number of lines changed per intent group in format
             `+N/-M`, <files/> is the list of affected file references,
             and <description/> is a *brief* one-to-two-sentence
             narrative of what changed and why:

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

@@ -13,11 +13,16 @@ effort: high
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-meta-evaluate">
 Evaluate Alternatives
 </skill>
 
+<expand name="getopt" arg1="ase-meta-evaluate">
+    $ARGUMENTS
+</expand>
+
 <objective>
 *Evaluate* *alternatives* through a weighted
 multi-*criteria* decision matrix.
@@ -25,7 +30,7 @@ multi-*criteria* decision matrix.
 
 <flow>
 1.  <step id="STEP 1: Determine Reason">
-    -   From the <request>$ARGUMENTS</request>, try to derive the overall
+    -   From the <request><getopt-arguments/></request>, try to derive the overall
         reason <reason/> for the evaluation. If no such reason can be
         derived, assume <reason>generic comparison</reason>.
 
@@ -38,7 +43,7 @@ multi-*criteria* decision matrix.
     </step>
 
 2.  <step id="STEP 2: Determine Alternatives">
-    -   From the <request>$ARGUMENTS</request> derive the two or more
+    -   From the <request><getopt-arguments/></request> derive the two or more
         alternatives <alternative-K/> (K=1-N) the user wants to be
         evaluated. Do not output anything.
 
@@ -105,7 +110,7 @@ multi-*criteria* decision matrix.
     </step>
 
 3.  <step id="STEP 3: Derive Criteria">
-    -   From the <request>$ARGUMENTS</request>, try to derive the criteria
+    -   From the <request><getopt-arguments/></request>, try to derive the criteria
         <criteria-L/> (L=1-M) for the evaluation. Do not output anything.
 
     -   For each criterion <criteria-L/> (L=1-M), decide on its <weight-L/>
@@ -222,23 +227,26 @@ multi-*criteria* decision matrix.
         ⚠ *Please give some hints on the criteria to ensure a single best alternative!*
         </template>
 
-    -   Otherwise, if <percentage/> is less than 0.10, stop the flow after
-        you output just the following <template/> and do not output anything
-        else:
+    -   Otherwise, if <rating-K/> is less than zero (i.e. all alternatives
+        rate negatively and the "best" is merely the least-bad), stop the
+        flow after you output just the following <template/> and do not
+        output anything else. This all-negative check is evaluated *before*
+        the small-distance check below, so that an all-negative alternative
+        set with a small winning gap surfaces the all-negative warning rather
+        than being masked by the small-distance branch:
 
         <template>
         <ase-tpl-bullet-signal/> **BEST ALTERNATIVE**: ⚑ **<alternative-K/>**
-        ⚠ *ATTENTION: small distance to second best alternative!*
+        ⚠ *ATTENTION: all alternatives rate negatively; this is the least-bad choice, not a strong winner!*
         </template>
 
-    -   Otherwise, if <rating-K/> is less than zero (i.e. all alternatives
-        rate negatively and the "best" is merely the least-bad), stop the
-        flow after you output just the following <template/> and do not
-        output anything else:
+    -   Otherwise, if <percentage/> is less than 0.10, stop the flow after
+        you output just the following <template/> and do not output anything
+        else:
 
         <template>
         <ase-tpl-bullet-signal/> **BEST ALTERNATIVE**: ⚑ **<alternative-K/>**
-        ⚠ *ATTENTION: all alternatives rate negatively; this is the least-bad choice, not a strong winner!*
+        ⚠ *ATTENTION: small distance to second best alternative!*
         </template>
 
     -   Otherwise (<percentage/> is greater than or equal to 0.10), output

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

@@ -15,18 +15,23 @@ effort: high
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-meta-persona">
 Persona Configuration
 </skill>
 
+<expand name="getopt" arg1="ase-meta-persona">
+    $ARGUMENTS
+</expand>
+
 <objective>
 *Configure* the *persona style* of the agent to adjust the communication
 style and token usage intensity.
 </objective>
 
 1.  Determine request:
-    <request>$ARGUMENTS</request>
+    <request><getopt-arguments/></request>
     Do not output anything.
 
 2.  <if condition="<request/> is empty">

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

@@ -134,9 +134,17 @@ by querying *multiple* AIs for an *optimal consensus*.
 
 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).
+    First, count the number of *available foreign AIs* (those queried in
+    STEP 2 which did *not* return an `ERROR:` response). If this count is
+    *zero* -- i.e., every foreign AI errored out or none were reachable
+    and only yourself (Anthropic Claude) remains -- a quorum is *not*
+    possible. In this case, set <c></c> and <n></n> to empty and instead
+    set <disagreement/> to `(no quorum: no foreign AIs were available)`,
+    then skip the rest of this step.
+
+    Otherwise, 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).
     If all responses disagree, the consensus <c/> is zero.
     If all responses agree, <c/> is <n/>.
 
@@ -165,6 +173,10 @@ by querying *multiple* AIs for an *optimal consensus*.
 
     **CONSENSUS RATE**: **<c/>/<n/>** <disagreement/>
 
+    When a quorum was *not* possible (see STEP 4), render this line
+    instead as just `**CONSENSUS RATE**: *n/a* <disagreement/>` (omitting
+    the `<c/>/<n/>` fraction), as a single AI cannot form a consensus.
+
     &#x25CB; **Anthropic Claude**:
     - [...]
     - [...]

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

@@ -88,12 +88,20 @@ Your objective is to *search* the *Internet*/*Web* for the following query:
         from the MCP server `search-exa`.
     </expand>
 
-    If the `websearch` backend is *selected*:
+    If the `websearch` backend is *selected* and the tool
+    `WebSearch` is available:
 
     <expand name="agent" arg1="websearch">
         Call the tool `WebSearch(query: "<query/>")`.
     </expand>
 
+    If the `websearch` backend is *selected* and the tool `web_search` is
+    available and the tool `WebSearch` is not available:
+
+    <expand name="agent" arg1="websearch">
+        Call the tool `web_search(query: "<query/>")`.
+    </expand>
+
     </step>
 
 2.  <step id="STEP 2: Consolidate Search Answers">

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

@@ -142,7 +142,11 @@ to <getopt-option-count/>; if <getopt-option-count/> is *non-numeric* or
     more Pro-Theses or Supporting-Arguments until you EITHER have found
     at least <count/> Pro-Theses or Supporting-Arguments with at least a
     rank of 7 OR you have already checked a total of <count/> x 5
-    Pro-Theses or Supporting-Arguments.
+    Pro-Theses or Supporting-Arguments. If the second condition is
+    reached first and fewer than <count/> Pro-Theses or
+    Supporting-Arguments reached a rank of at least 7, nevertheless
+    surface the <count/> highest-ranked ones found so far, because
+    <count/> is the *minimum* number of Pro-Theses to surface.
 
     Then, for the top-<count/> highest-ranked Pro-Theses or
     Supporting-Arguments, sort them by their rank from highest to lowest,

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

@@ -123,10 +123,12 @@ addressing surface-level symptoms.
 
             Then choose, among the <answer-k/>, the *most causally-significant*
             candidate -- the one most likely to lead to the true root-cause --
-            and *justify* the choice in one line (state explicitly *why* it
-            beats the other candidates, e.g. it alone also explains the timing,
-            scope, or magnitude of the level's fact). A bare "most significant"
-            is *not* sufficient; if no candidate clearly dominates, say so.
+            set <chosen-k/> to its candidate index (the <k/> of the chosen
+            <answer-k/>), and *justify* the choice in one line (state explicitly
+            *why* it beats the other candidates, e.g. it alone also explains the
+            timing, scope, or magnitude of the level's fact). A bare "most
+            significant" is *not* sufficient; if no candidate clearly dominates,
+            say so.
 
             <template>
             <ase-tpl-bullet-secondary/> **WHY <n/> → chosen <n/>.<chosen-k/>**: <justification/>

package/plugin/skills/ase-task-condense/SKILL.md

@@ -203,11 +203,12 @@ explicitly requested by this procedure via outputs based on a <template/>!
                 </template>
 
         -   If <getopt-option-next/> is equal to `none`:
-            Let the *user interactively choose* what to do as the next
-            step. For this you *MUST* use the custom `custom-dialog` and
-            *NOT* the `AskUserQuestion` based "user-dialog":
 
-            <expand name="custom-dialog">
+            In the following, you *MUST* *NOT* use the <user-dialog-tool/>
+            tool! Instead, you *MUST* just show a custom output, let the
+            user enter input, and then you set the result accordingly.
+
+            <expand name="custom-dialog" arg1="--no-other">
                 Next Step: How would you like to proceed with the plan?
                 DONE: Stop processing.
                 EDIT: Hand off plan to editing.