@rse/ase 0.9.7 → 0.9.9

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

@@ -89,9 +89,12 @@ Analyze documents for spelling, punctuation, or grammar errors
 
 3.  <step id="STEP 3: Correction">
 
-    1.  You *MUST* call the MCP tool `ase_config_set(key: "agent.skill", val:
-        "ase-docs-proofread", scope: "session:<ase-session-id/>")` of the
-        `ase` MCP server.
+    1.  *Mark this skill as the active edit-capable skill* so that the
+        ASE `pre-tool-use` hook auto-approves the subsequent `Edit`
+        invocations on *any* invocation path (slash command *or* `Skill`
+        tool). Call the `ase_config_set(key: "agent.skill", val:
+        "ase-docs-proofread", scope: "session:<ase-session-id/>")` tool
+        from the `ase` MCP server. Do not output anything in this substep.
 
     2.  Iterate over all problems:
 
@@ -116,8 +119,8 @@ Analyze documents for spelling, punctuation, or grammar errors
 
         3.  <if condition="<getopt-option-auto/> is not 'true'">
 
-            Render the proposed correction as a *unified diff* with *one*
-            line of context in a fenced block based on the following <template/>:
+            Render the proposed correction as a *unified diff* with *up to
+            two* lines of context in a fenced block based on the following <template/>:
 
             <template>
 
@@ -126,7 +129,7 @@ Analyze documents for spelling, punctuation, or grammar errors
             ```diff
             --- <file/> (original)
             +++ <file/> (corrected)
-            @@ -<line/>,<n/> +<line/>,<m/> @@
+            @@ -<old-start/>,<n/> +<new-start/>,<m/> @@
              <context-before/>
             -<old-text/>
             +<new-text/>
@@ -136,16 +139,26 @@ Analyze documents for spelling, punctuation, or grammar errors
             </template>
 
             Hints:
-            -   The <n/> is the number of lines in <old-text/>.
-            -   The <m/> is the number of lines in <new-text/>.
+            -   The <old-start/> is the line of the first hunk line, i.e.,
+                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 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 number of lines in <context-before/>, <new-text/>, and
+                <context-after/> combined.
 
             </if>
 
         4.  <if condition="<getopt-option-auto/> is not 'true'">
 
-            Ask the user how to proceed via an interactive user dialog:
+            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="user-dialog">
+            <expand name="custom-dialog">
                 CORRECTION: How would you like to proceed with this proposed correction?
                 ACCEPT: Apply the proposed correction.
                 REJECT: Skip this proposed correction.
@@ -153,19 +166,20 @@ Analyze documents for spelling, punctuation, or grammar errors
 
             </if>
 
-            <if condition="<getopt-option-auto/> is 'true'">
+            <else>
 
             Set <result>ACCEPT</result>.
 
-            </if>
+            </else>
 
         5.  Check <result/> and dispatch accordingly:
 
             -   <if condition="<result/> is 'ACCEPT'">
 
-                Invoke the `Edit` tool to apply the change exactly as shown
-                in the diff. The operation will be auto-approved because of
-                the active proofread marker, so *no* interactive permission
+                Invoke the `Edit` tool to apply the change by replacing
+                <old-text/> with <new-text/> at <file/>:<line/>. The operation
+                will be auto-approved by the ASE `pre-tool-use` hook (which
+                tracks the active skill), so *no* interactive permission
                 prompt will appear. Then continue with the next <item/>.
 
                 </if>
@@ -174,8 +188,8 @@ 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 loop back to substep 2 of
-                this iteration. There is *no* cap on refinement rounds -
+                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`.
 
                 </if>
@@ -193,8 +207,11 @@ Analyze documents for spelling, punctuation, or grammar errors
 
         </for>
 
-    3.  You *MUST* call the MCP tool `ase_config_delete(key: "agent.skill",
-        scope: "session:<ase-session-id/>")` of the `ase` MCP server.
+    3.  *Clear the active edit-capable skill marker* now that all `Edit`
+        invocations are done, so a later unrelated `Edit` is *not*
+        auto-approved. Call the `ase_config_delete(key: "agent.skill",
+        scope: "session:<ase-session-id/>")` tool from the `ase` MCP
+        server. Do not output anything in this substep.
 
     4.  You *MUST* *NOT* output any further additional explanations or
         summaries at the end of this skill processing, except for the

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

@@ -51,4 +51,4 @@ Proofread an entire documentation directory automatically:
 
 ##  SEE ALSO
 
-`ase-code-lint`, `ase-meta-changelog`.
+[`ase-code-lint`](../ase-code-lint/help.md), [`ase-meta-changelog`](../ase-meta-changelog/help.md).

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

@@ -78,7 +78,7 @@ Honor the following tenets throughout the brainstorming:
 
 1.  <step id="STEP 1: Restate Topic">
 
-    Restate the topic to be brainstormed by output the following <template/>:
+    Restate the topic to be brainstormed by outputting the following <template/>:
 
     <template>
     <ase-tpl-bullet-secondary/> **TOPIC**: <topic/>
@@ -113,17 +113,19 @@ Honor the following tenets throughout the brainstorming:
             <ase-tpl-bullet-signal/> FACET <M/>/<m/>: **<facet-M/>**, QUESTION: **<question-M/>**
             </template>
 
-        2.  Determine *up to 4* grounded candidate answers
+        2.  Determine *2 to 4* grounded candidate answers
             <answer-M-K/> (K={1,2,3,4}) from the code base, the documented
             context, and your world knowledge.
 
         3.  Use an interactive user dialog with header <facet-M/> and
             question <question-M/>, and let the user select the
-            <answer-M/> out of the candidate answers <answer-M-K/> (just
-            leave out all answers in case you have determined less than
-            4 potential answers)
+            <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":
 
-            <expand name="user-dialog">
+            <expand name="custom-dialog">
                 <facet-M/>: <question-M/>
                 <answer-M-1/>: (first grounded candidate answer)
                 <answer-M-2/>: (second grounded candidate answer)
@@ -131,7 +133,26 @@ Honor the following tenets throughout the brainstorming:
                 <answer-M-4/>: (fourth grounded candidate answer)
             </expand>
 
-        4.  Output the following <template/>:
+        4.  Dispatch on the dialog <result/>:
+
+            -   If <result/> is `CANCEL`:
+                Skip the remaining sub-steps of this iteration cycle and
+                continue directly with sub-step 2 below (cancellation handling).
+
+            -   If <result/> starts with `ERROR:`:
+                Ask the user interactively, without a special tool, the
+                question <question-M/> directly and set <answer-M/> to the
+                response of the user.
+
+            -   If <result/> matches `OTHER: <text/>`:
+                Set <answer-M><text/></answer-M> (take the user's free-text answer).
+
+            -   Otherwise:
+                Set <answer-M><result/></answer-M> (take the selected candidate answer).
+
+            Do not output anything in this sub-step.
+
+        5.  Output the following <template/>:
 
             <template>
             <ase-tpl-bullet-normal/> FACET <M/>/<m/>: **<facet-M/>**, ANSWER: **<answer-M/>**
@@ -182,7 +203,7 @@ Honor the following tenets throughout the brainstorming:
     set and finally into a recommendation.
 
     1.  *Cluster*: group the candidate ideas into <c/> coherent clusters
-        <cluster-C/> (a short 1-4 word label, C=1...</c>), collapsing
+        <cluster-C/> (a short 1-4 word label, C=1...<c/>), collapsing
         near-duplicates and discarding ideas pruned by *You Aren't Gonna
         Need It (YAGNI)* (speculative, out-of-scope, or contradicting
         documented context).

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

@@ -7,10 +7,10 @@
 
 `ase-meta-brainstorm`
     [`--help`|`-h`]
-    [`--max-clarify=3`]
+    [`--max-clarify`|`-c=3`]
     [`--min-ideas`|`-i=12`]
-    [`--min-rank=7`]
-    [`--max-shortlist=4`]
+    [`--min-rank`|`-r=7`]
+    [`--max-shortlist`|`-s=4`]
     *topic*
 
 ##  DESCRIPTION
@@ -33,13 +33,9 @@ default 7, or higher). Finally it distills a *shortlist* of the top
 wherever possible - and derives a single *RECOMMENDATION*, being either
 the highest-ranked option or a principled synthesis of the shortlist.
 
-On completion the skill offers a *next step*: stop, or hand the
-recommended direction off to the `ase-task-edit`, `ase-code-craft`, or
-`ase-task-preflight` skills.
-
 ##  OPTIONS
 
-`--max-clarify=3`:
+`--max-clarify`|`-c=3`:
     The *maximum* number of essential-unknown clarification questions
     asked in the *clarify intent* phase (default: 3). Lower it for a
     faster, leaner intake, raise it for more upfront grounding.
@@ -49,12 +45,12 @@ recommended direction off to the `ase-task-edit`, `ase-code-craft`, or
     phase before converging (default: 12). Raise it for a broader idea
     space, lower it for a quicker, narrower session.
 
-`--min-rank=7`:
+`--min-rank`|`-r=7`:
     The *minimum* 0-10 fit rank an idea must score to survive the
     *converge* phase (default: 7). Raise it for a stricter filter, lower
     it to retain more ideas.
 
-`--max-shortlist=4`:
+`--max-shortlist`|`-s=4`:
     The *maximum* number of distilled options on the final *shortlist*
     (default: 4). Lower it for a sharper focus, raise it for more
     finalists.
@@ -88,4 +84,4 @@ and a tighter shortlist:
 
 ##  SEE ALSO
 
-`ase-meta-evaluate`, `ase-meta-quorum`, `ase-meta-diaboli`
+[`ase-meta-evaluate`](../ase-meta-evaluate/help.md), [`ase-meta-quorum`](../ase-meta-quorum/help.md), [`ase-meta-diaboli`](../ase-meta-diaboli/help.md)

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

@@ -30,4 +30,4 @@ Update the most recent ChangeLog section:
 
 ##  SEE ALSO
 
-`ase-meta-commit`, `ase-docs-proofread`.
+[`ase-meta-commit`](../ase-meta-commit/help.md), [`ase-docs-proofread`](../ase-docs-proofread/help.md).

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

@@ -42,4 +42,4 @@ Ask Gemini for a brief comparison:
 
 ##  SEE ALSO
 
-`ase-meta-quorum`, `ase-meta-search`.
+[`ase-meta-quorum`](../ase-meta-quorum/help.md), [`ase-meta-search`](../ase-meta-search/help.md).

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

@@ -28,4 +28,4 @@ Craft a commit message for the currently staged changes:
 
 ##  SEE ALSO
 
-`ase-meta-changelog`.
+[`ase-meta-changelog`](../ase-meta-changelog/help.md).

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

@@ -73,6 +73,6 @@ Surface at least fifteen anti-theses:
 
 ##  SEE ALSO
 
-`ase-meta-why`, `ase-meta-evaluate`, `ase-meta-quorum`,
-`ase-meta-persona`.
+[`ase-meta-why`](../ase-meta-why/help.md), [`ase-meta-evaluate`](../ase-meta-evaluate/help.md), [`ase-meta-quorum`](../ase-meta-quorum/help.md),
+[`ase-meta-persona`](../ase-meta-persona/help.md).
 

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

@@ -11,9 +11,9 @@ disable-model-invocation: false
 effort: high
 allowed-tools:
     - "Bash(git diff *)"
-    - "Bash(git grep:*)"
-    - "Bash(git ls-files:*)"
-    - "Bash(grep:*)"
+    - "Bash(git grep *)"
+    - "Bash(git ls-files *)"
+    - "Bash(grep *)"
     - "Agent"
 ---
 
@@ -98,7 +98,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
             </template>
 
-        2.  Render a *two-column table* with one row per discovered
+        2.  Render a *three-column table* with one row per discovered
             *intent group* present in the <diff/>. Output the following
             table header <template/>:
 
@@ -169,7 +169,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
         Judge overall *coherence* from the flagged hunks: the diff
         is `COHERENT` when there are *no* `SCOPE-CREEP` and *no*
         `STRAY-DEBUG` deviations, otherwise it is `INCOHERENT`. Store
-        the result is <verdict/>.
+        the result in <verdict/>.
 
     4.  Emit the following header <template/>:
 
@@ -205,6 +205,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
         | **<deviation/>** | <location/> | <reason/>                         |
 
         </template>
+        </if>
     </step>
 
 4.  <step id="STEP 4: Score Against Risk Rubric"

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

@@ -17,24 +17,23 @@ The `ase-meta-diff` skill turns a raw Git diff into a *concise*,
 *human-readable* narrative of what changed and why, *grouped by
 intent* (such as *Feature*, *Improvement*, *Bugfix*, *Update*,
 *Cleanup*, or *Refactor*) rather than by file. It inspects the
-*staged* changes (`git diff --cached HEAD`). The result is a short
-bullet list, one bullet per intent group, each naming the affected
-files with their per-file `[+N/-M]` line counts - giving you the
-essence of the changes at a glance.
+*staged* changes (`git diff --cached HEAD`). The result is a compact
+table, one row per intent group, each naming the affected files
+with their per-file `[+N/-M]` line counts - giving you the essence
+of the changes at a glance.
 
 With `--coherence`, the skill additionally *reconstructs the single
 intended change* the diff is trying to accomplish - phrased as one crisp
 *thesis* sentence - and then walks *every* hunk to *flag those that do
 not serve it*: **scope creep** (an unrelated feature or drive-by refactor
-riding along), **stray debug** (leftover prints, commented-out code, or
-disabled tests), and **ripple** (mechanical fallout edits forced by the
-core change). It emits an overall **COHERENT** / **INCOHERENT** verdict
+riding along) and **stray debug** (leftover prints, commented-out code, or
+disabled tests). It emits an overall **COHERENT** / **INCOHERENT** verdict
 plus a table of the flagged hunks with what to do with each - keeping the
 diff to a *single logical and coherent change* before it is committed.
 
 With `--risk`, the skill additionally *scores* the same diff against a
 four-axis **coupling-criticality-coverage-reversibility** rubric and
-emits a *graded risk report* - one bullet per axis (each scored *1*-*5*
+emits a *graded risk report* - one table row per axis (each scored *1*-*5*
 with a one-line evidence justification drawn from the actual hunks), an
 overall risk band (**LOW**, **MODERATE**, **HIGH**, or **CRITICAL**),
 and one actionable *mitigation* per high-risk axis. The axes combine
@@ -57,9 +56,9 @@ giving a visual sense of *what a diff endangers* before a deeper review.
 `--coherence`, `-c`:
     In addition to the intent-grouped summary, reconstruct the diff's
     *single intended change* as one crisp *thesis* sentence and flag
-    *every* hunk that does *not* serve it - *scope creep*, *stray debug*,
-    or *ripple* fallout - then emit an overall **COHERENT** /
-    **INCOHERENT** verdict with a table of the flagged hunks.
+    *every* hunk that does *not* serve it - *scope creep* or *stray
+    debug* - then emit an overall **COHERENT** / **INCOHERENT** verdict
+    with a table of the flagged hunks.
 
 `--risk`, `-r`:
     In addition to the intent-grouped summary, score the diff against
@@ -102,4 +101,4 @@ Summarize the staged changes and append a blast-radius map:
 
 ##  SEE ALSO
 
-`ase-meta-commit`, `ase-meta-changelog`, `ase-arch-analyze`.
+[`ase-meta-commit`](../ase-meta-commit/help.md), [`ase-meta-changelog`](../ase-meta-changelog/help.md), [`ase-arch-analyze`](../ase-arch-analyze/help.md).

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

@@ -193,15 +193,16 @@ multi-*criteria* decision matrix.
 
     -   Determine rating distance percentage <percentage/> between
         <alternative-K/> and <alternative-X/> from their *raw,
-        unrounded* ratings by calculating: <percentage/> = <distance/> /
-        abs(<rating-K/>). Do not output anything.
-
-    -   If <rating-K/> is exactly zero, skip the division entirely
-        and treat <percentage/> as if it were equal to <distance/>
-        (so a true zero tie with <distance/> = 0 falls into the
-        *MULTIPLE BEST* branch below, and a non-zero gap with zero
-        best falls into the *small distance* branch below).
-        Do not output anything.
+        unrounded* ratings as follows. If <rating-K/> is exactly zero,
+        skip the division entirely and treat <percentage/> as if it
+        were equal to <distance/> (so a true zero tie with <distance/>
+        = 0 falls into the *MULTIPLE BEST* branch below, while a non-zero
+        gap with zero best is routed by the magnitude of <distance/>
+        through the same thresholds as <percentage/> otherwise). Do not
+        output anything.
+
+    -   Otherwise (<rating-K/> is non-zero), calculate: <percentage/> =
+        <distance/> / abs(<rating-K/>). Do not output anything.
 
     -   By construction, <rating-K/> is the maximum rating across
         all alternatives, so <distance/> >= 0 always holds; using

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

@@ -48,5 +48,5 @@ Evaluate database options with hinted criteria:
 
 ##  SEE ALSO
 
-`ase-meta-quorum`, `ase-meta-search`, `ase-arch-discover`,
-`ase-meta-why`.
+[`ase-meta-quorum`](../ase-meta-quorum/help.md), [`ase-meta-search`](../ase-meta-search/help.md), [`ase-arch-discover`](../ase-arch-discover/help.md),
+[`ase-meta-why`](../ase-meta-why/help.md).

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

@@ -47,4 +47,4 @@ Switch to the telegrapher persona:
 
 ##  SEE ALSO
 
-`ase-task-id`.
+[`ase-task-id`](../ase-task-id/help.md).

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

@@ -62,9 +62,19 @@ by querying *multiple* AIs for an *optimal consensus*.
 
     The user-selectable foreign models are restricted by the
     `--models`/`-m` option, parsed into <getopt-option-models/>
-    as a comma-separated list of model tokens. The default is
-    the single token `all`. If <getopt-option-models/> contains
-    the token `all`, you *MUST* treat it as the full list
+    as a comma-separated list of model tokens. The getopt parser
+    validates only the *first* token, so you *MUST* validate each
+    remaining token yourself against the allowed set `all`, `chatgpt`,
+    `gemini`, `deepseek`, `grok`, `glm`, `qwen`. If any token is *not*
+    in this set, only output the following <template/> and then
+    immediately *STOP* processing the entire current skill:
+
+    <template>
+    ⧉ **ASE**: ✪ skill: **ase-meta-quorum**, ▶ ERROR: invalid `--models` token: **<token/>**
+    </template>
+
+    The default is the single token `all`. If <getopt-option-models/>
+    contains the token `all`, you *MUST* treat it as the full list
     `chatgpt,gemini,deepseek,grok,glm,qwen` (all models). Anthropic
     Claude (yourself) is *always* included, independent of this option.
 
@@ -142,8 +152,8 @@ by querying *multiple* AIs for an *optimal consensus*.
 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/>:
+    unmodified responses of yourself and each of the queried foreign
+    AIs, based on the following output <template/>:
 
     <template>
     **QUESTION**:

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

@@ -56,4 +56,4 @@ Ask only a subset of the foreign models:
 
 ##  SEE ALSO
 
-`ase-meta-chat`, `ase-meta-search`, `ase-meta-evaluate`.
+[`ase-meta-chat`](../ase-meta-chat/help.md), [`ase-meta-search`](../ase-meta-search/help.md), [`ase-meta-evaluate`](../ase-meta-evaluate/help.md).

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

@@ -17,7 +17,6 @@ allowed-tools:
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
-@${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
 <skill name="ase-meta-review">
@@ -107,8 +106,8 @@ explicitly requested by this procedure via outputs based on a <template/>!
     <verdict/> to `REJECT - DEMANDS CHANGES` if *any* finding in
     <findings/> has a `severity` field of `HIGH`; otherwise set
     <verdict/> to `APPROVE`. The verdict is derived *before* the
-    severity floor below, so a suppressed `HIGH` finding still drives the
-    verdict.
+    severity floor below, so the floor only affects which findings are
+    *rendered*, never the verdict.
 
     Then *apply the severity floor* selected via <getopt-option-severity/>
     (default `LOW`): define the ordinal rank `LOW`=1, `MEDIUM`=2,
@@ -135,7 +134,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
         </template>
 
-        You *MUST* *NOT* output anything else in this STEP 3.
+        You *MUST* *NOT* output anything else in this STEP 3.1.
 
     2.  <if condition="<findings/> is empty">
         Only output the following <template/> and then *SKIP* the

package/plugin/skills/ase-meta-review/help.md

@@ -59,9 +59,9 @@ before it is committed.
     Set the *severity floor* (default `LOW`): findings below the chosen
     threshold are silently suppressed, ordered `LOW` < `MEDIUM` <
     `HIGH`. The default `LOW` keeps all findings; `ACCEPTED` findings are
-    never suppressed. The floor only affects the rendered findings table;
-    the overall *verdict* is still derived from all findings, so a
-    suppressed `HIGH` finding still yields a *REJECT* verdict.
+    never suppressed. The floor only affects the rendered findings table,
+    not the overall *verdict*, which is always derived from all findings
+    before the floor is applied.
 
 ##  ARGUMENTS
 
@@ -84,5 +84,5 @@ Review the staged changes, reporting only `MEDIUM` and `HIGH` findings:
 
 ##  SEE ALSO
 
-`ase-meta-diff`, `ase-meta-commit`, `ase-code-lint`, `ase-code-analyze`,
-`ase-meta-diaboli`.
+[`ase-meta-diff`](../ase-meta-diff/help.md), [`ase-meta-commit`](../ase-meta-commit/help.md), [`ase-code-lint`](../ase-code-lint/help.md), [`ase-code-analyze`](../ase-code-analyze/help.md),
+[`ase-meta-diaboli`](../ase-meta-diaboli/help.md).

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

@@ -41,8 +41,8 @@ Your objective is to *search* the *Internet*/*Web* for the following query:
     <define name="agent">
     ```text
         Agent(
-            name:          "ase-meta-search",
-            description:   "Query Web Search Service",
+            name:          "ase-meta-search-<arg1/>",
+            description:   "Query Web Search Service: <arg1/>",
             subagent_type: "ase:ase-meta-search",
             prompt:        <content/>
         )
@@ -53,8 +53,9 @@ Your objective is to *search* the *Internet*/*Web* for the following query:
     *backend tokens*. The getopt parser validates only the *first*
     token, so you *MUST* validate each remaining token yourself against
     the allowed set `all`, `perplexity`, `brave`, `exa`, `websearch`. If
-    any token is *not* in this set, only output the following <template/>
-    and then immediately *STOP* processing the entire current skill:
+    any token is *not* in this set, bind <token/> to that offending
+    token, then only output the following <template/> and then
+    immediately *STOP* processing the entire current skill:
 
     <template>
     ⧉ **ASE**: ✪ skill: **ase-meta-search**, ▶ ERROR: invalid `--services` token: **<token/>**
@@ -66,7 +67,7 @@ Your objective is to *search* the *Internet*/*Web* for the following query:
     If the `perplexity` backend is *selected* and the MCP tool
     `perplexity_search` from the MCP server `search-perplexity` is available:
 
-    <expand name="agent">
+    <expand name="agent" arg1="perplexity">
         Call the MCP tool `perplexity_search(query: "<query/>")`
         from the MCP server `search-perplexity`.
     </expand>
@@ -74,7 +75,7 @@ Your objective is to *search* the *Internet*/*Web* for the following query:
     If the `brave` backend is *selected* and the MCP tool
     `brave_web_search` from the MCP server `search-brave` is available:
 
-    <expand name="agent">
+    <expand name="agent" arg1="brave">
         Call the MCP tool `brave_web_search(query: "<query/>")`
         from the MCP server `search-brave`.
     </expand>
@@ -82,14 +83,14 @@ Your objective is to *search* the *Internet*/*Web* for the following query:
     If the `exa` backend is *selected* and the MCP tool
     `web_search_exa` from the MCP server `search-exa` is available:
 
-    <expand name="agent">
+    <expand name="agent" arg1="exa">
         Call the MCP tool `web_search_exa(query: "<query/>")`
         from the MCP server `search-exa`.
     </expand>
 
     If the `websearch` backend is *selected*:
 
-    <expand name="agent">
+    <expand name="agent" arg1="websearch">
         Call the tool `WebSearch(query: "<query/>")`.
     </expand>
 

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

@@ -48,4 +48,4 @@ Search the Web using only the Brave and Exa backends:
 
 ##  SEE ALSO
 
-`ase-meta-chat`, `ase-meta-quorum`, `ase-arch-discover`.
+[`ase-meta-chat`](../ase-meta-chat/help.md), [`ase-meta-quorum`](../ase-meta-quorum/help.md), [`ase-arch-discover`](../ase-arch-discover/help.md).

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

@@ -197,7 +197,7 @@ to <getopt-option-count/>; if <getopt-option-count/> is *non-numeric* or
     Carry the result forward to the next round: set
     <thesis><fortification/></thesis> (the fortification becomes the
     thesis to be strengthened next), set <i/> to <i/> + 1 (increment the
-    round counter), and then *CONTINUE* the *LOOP* at **STEP 1**!
+    round counter), and then *REPEAT* the operation at **STEP 1**!
     </if>
 
     <if condition="<i/> is greater than or equal to <rounds/>">

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

@@ -88,5 +88,5 @@ Strengthen across five iterative rounds:
 
 ##  SEE ALSO
 
-`ase-meta-diaboli`, `ase-meta-why`, `ase-meta-evaluate`,
-`ase-meta-quorum`.
+[`ase-meta-diaboli`](../ase-meta-diaboli/help.md), [`ase-meta-why`](../ase-meta-why/help.md), [`ase-meta-evaluate`](../ase-meta-evaluate/help.md),
+[`ase-meta-quorum`](../ase-meta-quorum/help.md).