@rse/ase 0.0.44 → 0.0.48

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

@@ -5,9 +5,9 @@ description: >
     *Always use* when you have to *visualize*
     structure/layout/components/dependencies as Flowchart,
     control-flow/branching/concurrency as Flowchart,
-    state-machine/states/transitions as an UML State Diagram,
-    data-flow/actors/messages/protocols as an UML Sequence Diagram,
-    data-structure/classes/methods as an UML Class Diagram
+    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
@@ -71,7 +71,7 @@ Rules
     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
+    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
@@ -95,7 +95,7 @@ Rules
     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
+    then stack the two rendered blocks *vertically* — each preceded by
     a bold label (`**BEFORE:**` / `**AFTER:**`, or similar). Do *not*
     attempt side-by-side layout.
 

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

@@ -116,12 +116,12 @@ multi-*criteria* decision matrix.
     -   From the <request>$ARGUMENTS</request>, try to derive the criteria
         <criteria-L/> (L=1-M) for the evaluation. Do not output anything.
 
-    -   For each criteria <criteria-L/> (L=1-M), decide on its <weight-L/>
+    -   For each criterion <criteria-L/> (L=1-M), decide on its <weight-L/>
         from the value set { 4.00, 2.00, 1.00, 0.50, 0.25 } (from most
         important, over normal, to less important). Do not output anything.
 
     -   Ensure the final number of criteria is always within the range of
-        minimum 8 and maximum 12: if less than 8 criteria were requested,
+        minimum 8 and maximum 12: if fewer than 8 criteria were requested,
         use the set of alternatives to decide on additional criteria
         which potentially allow best to triage the alternatives, take the
         <reason/> into account, and use the `ase-meta-search` skill (drawing from
@@ -146,9 +146,9 @@ multi-*criteria* decision matrix.
     </step>
 
 4.  <step id="STEP 4: Evaluate Alternatives against Criteria">
-    -   For each alternative <alternative-K/> (K=1-N) and each criteria
+    -   For each alternative <alternative-K/> (K=1-N) and each criterion
         <criteria-L/> (L=1-M), decide on the evaluation <eval-K-L/>, which
-        means how good the alternative meets the criteria on a Likert-scale
+        means how well the alternative meets the criterion on a Likert-scale
         from { -2, -1, 0, +1, +2 } (from worst, over neutral, to best). Do
         not output anything.
 

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

@@ -2,7 +2,7 @@
 name: ase-meta-persona
 argument-hint: "[<persona>]"
 description: >
-    Adjust communication style in four intensivity levels of token usage.
+    Adjust communication style in four intensity levels of token usage.
     The <persona> can be either the decorative, eloquent, and explaining "writer",
     the concise, factual, and accurate "engineer" (default),
     the brief, factual, and abbreviating "telegrapher",

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

@@ -83,7 +83,7 @@ by querying *multiple* AIs for an *optimal consensus*.
 
     If not all AIs agree, determine a <disagreement/> information,
     formatted as `(disagreement: <ai/>, <ai/>, [...])` where <ai/> is a
-    name of an AI which disagreed from the consensus. Else, if all AIs
+    name of an AI which disagreed with the consensus. Else, if all AIs
     agree, set <disagreement></disagreement>.
     </step>
 

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

@@ -22,7 +22,7 @@ Your role is an *expert-level assistant*.
 
 <objective>
 Apply the *Five-Whys* *root-cause analysis* technique to investigate
-on the following problem:
+the following problem:
 
 <problem>Why $ARGUMENTS?</problem>
 
@@ -48,7 +48,7 @@ addressing surface-level symptoms.
         Ask <question/> and document the answer in <answer/> with the following template:
         Don't stop at symptoms, keep digging for systemic issues.
         Multiple root-causes may exist -- explore different branches.
-        Consider both technical, domain-specific, process-related or organizational causes.
+        Consider technical, domain-specific, process-related, or organizational causes.
 
         <template>
         &#x26AA; **WHY <item/>**: <answer/>

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

@@ -277,7 +277,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
     1.  *Update timestamp*:
         <if condition="<content/> contains '✎ modified:' AND <content-dirty/> is 'true'">
-        Set update <timestamp-modified/> with the current time in
+        Update <timestamp-modified/> with the current time in
         ISO-style format, which has to be determined by calling the
         `timestamp(format: "yyyy-LL-dd HH:mm")` tool of the `ase`
         MCP service and use the `text` field of its response. Update

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

@@ -126,7 +126,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
         </template>
 
     3.  <if condition="<content/> contains '✎ modified:'">
-        Set update <timestamp-modified/> with the current time in
+        Update <timestamp-modified/> with the current time in
         ISO-style format, which has to be determined by calling the
         `timestamp(format: "yyyy-LL-dd HH:mm")` tool of the `ase`
         MCP service and use the `text` field of its response. Update

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

@@ -71,7 +71,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
         *Render plan*: Only output the following <template/>, so the user
         can read the plan and react to it. Do *not* truncate, summarize,
         or partially show the plan -- always show the complete plan
-        <content/> here:.
+        <content/> here.
 
         <template>
         ⧉ **ASE**: ┈┈┈┈┈┈┈┈────────━━━━━━━━**(** `TASK-PLAN-BEGIN` **)**━━━━━━━━────────┈┈┈┈┈┈┈┈