@rse/ase 0.0.52 → 0.0.54

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

@@ -30,9 +30,11 @@ Iteratively Edit a Task Plan
     $ARGUMENTS
 </expand>
 
+<role>
 Your role is an experienced, *expert-level assistant*,
 specialized in the *planning* of changes
 through *iterative conversational refinement*.
+</role>
 
 Establish and refine the *task plan* purely through a *chat-driven
 loop*. The user steers each round via interactive dialog that offers
@@ -63,9 +65,9 @@ explicitly requested by this procedure via outputs based on a <template/>!
             ">
             Set <ase-task-id><instruction/></ase-task-id> (set task
             id to instruction) and <instruction></instruction> (set
-            instruction empty), call the `task_id(id: <ase-task-id/>,
+            instruction empty), call the `ase_task_id(id: <ase-task-id/>,
             session: <ase-session-id/>)` tool from the `ase` MCP
-            service to switch the task, and then only output the
+            server to switch the task, and then only output the
             following <template/>:
 
             <template>
@@ -80,8 +82,8 @@ explicitly requested by this procedure via outputs based on a <template/>!
             ">
             Set <instruction></instruction> (set instruction to empty)
             and <ase-task-id><id/></ase-task-id> (set task id to
-            id) and call the `task_id(id: <ase-task-id/>, session:
-            <ase-session-id/>)` tool from the `ase` MCP service to
+            id) and call the `ase_task_id(id: <ase-task-id/>, session:
+            <ase-session-id/>)` tool from the `ase` MCP server to
             switch the task, and then only output the following
             <template/>:
 
@@ -97,8 +99,8 @@ explicitly requested by this procedure via outputs based on a <template/>!
             ">
             Set <instruction><text/></instruction> (set instruction to
             text) and <ase-task-id><id/></ase-task-id> (set task id
-            to id) and call the `task_id(id: <ase-task-id/>, session:
-            <ase-session-id/>)` tool from the `ase` MCP service to
+            to id) and call the `ase_task_id(id: <ase-task-id/>, session:
+            <ase-session-id/>)` tool from the `ase` MCP server to
             switch the task, and then only output the following
             <template/>:
 
@@ -131,9 +133,9 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 2.  **Determine Plan:**
 
-    1.  Call the `task_load(id: <ase-task-id/>)` tool of the `ase` MCP
-        service to load any existing plan content and set <text/> to
-        the `text` output field of this `task_load` tool call.
+    1.  Call the `ase_task_load(id: <ase-task-id/>)` tool of the `ase` MCP
+        server to load any existing plan content and set <text/> to
+        the `text` output field of this `ase_task_load` tool call.
         Do not output anything related to this MCP tool call.
         Set <content-dirty>false</content-dirty>.
 
@@ -204,8 +206,8 @@ explicitly requested by this procedure via outputs based on a <template/>!
             the <instruction/> and all decisions you derived from the
             <instruction/>.
 
-            Call the `timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
-            `ase` MCP service and use the `text` field of its response
+            Call the `ase_timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
+            `ase` MCP server and use the `text` field of its response
             for fresh <timestamp-created/> and <timestamp-modified/>
             information. Then insert the current <ase-task-id/>,
             <timestamp-created/>, and <timestamp-modified/> information
@@ -253,8 +255,8 @@ explicitly requested by this procedure via outputs based on a <template/>!
         the <instruction/> and all decisions you derived from the
         <instruction/>.
 
-        Call the `timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
-        `ase` MCP service and use the `text` field of its response
+        Call the `ase_timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
+        `ase` MCP server and use the `text` field of its response
         for fresh <timestamp-created/> and <timestamp-modified/>
         information. Then insert the current <ase-task-id/>,
         <timestamp-created/>, and <timestamp-modified/> information
@@ -279,16 +281,16 @@ explicitly requested by this procedure via outputs based on a <template/>!
         <if condition="<content/> contains '✎ modified:' AND <content-dirty/> is 'true'">
         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
+        `ase_timestamp(format: "yyyy-LL-dd HH:mm")` tool of the `ase`
+        MCP server and use the `text` field of its response. Update
         <content/> with the new `✎ modified: **<timestamp-modified/>**`.
         Do not output anything.
         </if>
 
     2.  *Persist plan*:
         <if condition="<content-dirty/> is 'true'">
-        Call the `task_save(id: <ase-task-id/>, text: <content/>)` tool
-        of the `ase` MCP service to persist the current plan, and then
+        Call the `ase_task_save(id: <ase-task-id/>, text: <content/>)` tool
+        of the `ase` MCP server to persist the current plan, and then
         set <content-dirty>false</content-dirty> again. Calculate the
         number of words <words/> of <content/>. Do not output anything
         related to this MCP tool call except the following <template/>:

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

@@ -24,8 +24,8 @@ Configure Task Id
     <request>$ARGUMENTS</request>
 
 2.  <if condition="<request/> is empty">
-    -   Call the `task_id(session: <ase-session-id/>)`
-        tool from the `ase` MCP service and set
+    -   Call the `ase_task_id(session: <ase-session-id/>)`
+        tool from the `ase` MCP server and set
         <ase-task-id/> to its `text` output.
 
     -   Output:
@@ -36,8 +36,8 @@ Configure Task Id
 
 3.  <if condition="<request/> is NOT empty">
     -   Set <ase-task-id><request/></ase-task-id> and
-        call the `task_id(id: <ase-task-id/>, session: <ase-session-id/>)`
-        tool from the `ase` MCP service.
+        call the `ase_task_id(id: <ase-task-id/>, session: <ase-session-id/>)`
+        tool from the `ase` MCP server.
 
     -   Output:
         <template>

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

@@ -28,8 +28,10 @@ Implement a Task Plan
     $ARGUMENTS
 </expand>
 
+<role>
 Your role is an experienced, *expert-level assistant*,
 specialized in the *implementation* of changes.
+</role>
 
 *Implement* the task plan by modifying the *artifacts*
 with a corresponding, complete *change set*.
@@ -57,9 +59,9 @@ explicitly requested by this procedure via outputs based on a <template/>!
             ">
             Set <ase-task-id><instruction/></ase-task-id> (set task
             id to instruction) and <instruction></instruction> (set
-            instruction empty), call the `task_id(id: <ase-task-id/>,
+            instruction empty), call the `ase_task_id(id: <ase-task-id/>,
             session: <ase-session-id/>)` tool from the `ase` MCP
-            service to switch the task, and then only output the
+            server to switch the task, and then only output the
             following <template/>:
 
             <template>
@@ -74,8 +76,8 @@ explicitly requested by this procedure via outputs based on a <template/>!
             ">
             Set <instruction></instruction> (set instruction to empty)
             and <ase-task-id><id/></ase-task-id> (set task id to
-            id) and call the `task_id(id: <ase-task-id/>, session:
-            <ase-session-id/>)` tool from the `ase` MCP service to
+            id) and call the `ase_task_id(id: <ase-task-id/>, session:
+            <ase-session-id/>)` tool from the `ase` MCP server to
             switch the task, and then only output the following
             <template/>:
 
@@ -86,9 +88,9 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 2.  **Determine Operation**:
 
-    1.  Call the `task_load(id: <ase-task-id/>)` tool of the `ase` MCP
-        service to load the current task plan content and set <content/> to
-        the `text` output field of the `task_load` tool call.
+    1.  Call the `ase_task_load(id: <ase-task-id/>)` tool of the `ase` MCP
+        server to load the current task plan content and set <content/> to
+        the `text` output field of the `ase_task_load` tool call.
 
         Calculate the number of words <words/> of <content/>.
 

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

@@ -26,8 +26,8 @@ List Task Plans
     $ARGUMENTS
 </expand>
 
-1.  Call the `task_list(verbose: <getopt-option-verbose/>)` tool from
-    the `ase` MCP service. The result is a structured object with a
+1.  Call the `ase_task_list(verbose: <getopt-option-verbose/>)` tool from
+    the `ase` MCP server. The result is a structured object with a
     `tasks` array where each entry has an `id` field, and -- if
     <getopt-option-verbose/> is `true` -- additionally an `mtime` field
     (formatted as `YYYY-MM-DD HH:MM`).

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

@@ -28,8 +28,10 @@ Preflight a Task Plan
     $ARGUMENTS
 </expand>
 
+<role>
 Your role is an experienced, *expert-level assistant*,
 specialized in the *implementation* of changes.
+</role>
 
 *Preflight* the implementation of a task plan by creating a draft
 for a corresponding, *complete source code change set*.
@@ -57,9 +59,9 @@ explicitly requested by this procedure via outputs based on a <template/>!
             ">
             Set <ase-task-id><instruction/></ase-task-id> (set task
             id to instruction) and <instruction></instruction> (set
-            instruction empty), call the `task_id(id: <ase-task-id/>,
+            instruction empty), call the `ase_task_id(id: <ase-task-id/>,
             session: <ase-session-id/>)` tool from the `ase` MCP
-            service to switch the task, and then only output the
+            server to switch the task, and then only output the
             following <template/>:
 
             <template>
@@ -74,8 +76,8 @@ explicitly requested by this procedure via outputs based on a <template/>!
             ">
             Set <instruction></instruction> (set instruction to empty)
             and <ase-task-id><id/></ase-task-id> (set task id to
-            id) and call the `task_id(id: <ase-task-id/>, session:
-            <ase-session-id/>)` tool from the `ase` MCP service to
+            id) and call the `ase_task_id(id: <ase-task-id/>, session:
+            <ase-session-id/>)` tool from the `ase` MCP server to
             switch the task, and then only output the following
             <template/>:
 
@@ -86,9 +88,9 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 2.  **Determine Operation:**
 
-    1.  Call the `task_load(id: <ase-task-id/>)` tool of the `ase` MCP
-        service to load the current task plan content and set <content/> to
-        the `text` output field of the `task_load` tool call.
+    1.  Call the `ase_task_load(id: <ase-task-id/>)` tool of the `ase` MCP
+        server to load the current task plan content and set <content/> to
+        the `text` output field of the `ase_task_load` tool call.
 
         Calculate the number of words <words/> of <content/>.
 
@@ -128,14 +130,14 @@ explicitly requested by this procedure via outputs based on a <template/>!
     3.  <if condition="<content/> contains '✎ modified:'">
         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
+        `ase_timestamp(format: "yyyy-LL-dd HH:mm")` tool of the `ase`
+        MCP server and use the `text` field of its response. Update
         <content/> with the new `✎ modified: **<timestamp-modified/>**`.
         Do not output anything.
         </if>
 
-    4.  Finally, call the `task_save(id: <ase-task-id/>,
-        text: <content/>)` of the `ase` MCP service to save the updated
+    4.  Finally, call the `ase_task_save(id: <ase-task-id/>,
+        text: <content/>)` of the `ase` MCP server to save the updated
         task plan content. Calculate the number of words <words/> of
         <content/>. Do not output anything related to this MCP tool call
         except the following <template/>:

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

@@ -7,7 +7,7 @@ description: >
     the "task", "plan", "spec", or "specification".
 user-invocable: true
 disable-model-invocation: false
-effort: xhigh
+effort: high
 ---
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
@@ -28,8 +28,10 @@ Reboot a Task Plan
     $ARGUMENTS
 </expand>
 
+<role>
 Your role is an experienced, *expert-level assistant*,
 specialized in the *planning* of changes.
+</role>
 
 *Reboot* the task plan by crafting it from scratch,
 based on the existing *WHAT* and *WHY*.
@@ -59,9 +61,9 @@ explicitly requested by this procedure via outputs based on a <template/>!
         ">
         Set <ase-task-id><instruction/></ase-task-id> (set task
         id to instruction) and <instruction></instruction> (set
-        instruction empty), call the `task_id(id: <ase-task-id/>,
+        instruction empty), call the `ase_task_id(id: <ase-task-id/>,
         session: <ase-session-id/>)` tool from the `ase` MCP
-        service to switch the task, and then only output the
+        server to switch the task, and then only output the
         following <template/>:
 
         <template>
@@ -71,9 +73,9 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 2.  **Determine Operation:**
 
-    1.  Call the `task_load(id: <ase-task-id/>)` tool of the `ase` MCP
-        service to load the current task plan content and set <content/> to
-        the `text` output field of the `task_load` tool call.
+    1.  Call the `ase_task_load(id: <ase-task-id/>)` tool of the `ase` MCP
+        server to load the current task plan content and set <content/> to
+        the `text` output field of the `ase_task_load` tool call.
 
         Calculate the number of words <words/> of <content/>.
 
@@ -118,15 +120,15 @@ explicitly requested by this procedure via outputs based on a <template/>!
         the <instruction/> and all decisions you derived from the
         <instruction/>.
 
-    7.  Call the `timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
-        `ase` MCP service and use the `text` field of its response for
+    7.  Call the `ase_timestamp(format: "yyyy-LL-dd HH:mm")` tool of the
+        `ase` MCP server and use the `text` field of its response for
         <timestamp-modified/> information. Then insert the current
         <ase-task-id/>, previous <timestamp-created/>, and refreshed
         <timestamp-modified/> information and calculate the number of
         words <words/> of <content/>.
 
-    8.  Call the `task_save(id: <ase-task-id/>,
-        text: <content/>)` of the `ase` MCP service to save the updated
+    8.  Call the `ase_task_save(id: <ase-task-id/>,
+        text: <content/>)` of the `ase` MCP server to save the updated
         task plan content. Do not output anything related to this MCP
         call.
 

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

@@ -20,7 +20,10 @@ Rename a Task Plan
 Rename a Task Plan
 </skill>
 
+<role>
 Your role is an experienced, *expert-level assistant*.
+</role>
+
 *Rename* the task plan.
 
 Procedure
@@ -61,9 +64,9 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 2.  **Perform Operation**:
 
-    1.  Call the `task_rename(old: <old/>, new: <new/>)` tool of the
-        `ase` MCP service to rename the task plan and set <text/> to the
-        `text` output field of this `task_rename` tool call. Do not
+    1.  Call the `ase_task_rename(old: <old/>, new: <new/>)` tool of the
+        `ase` MCP server to rename the task plan and set <text/> to the
+        `text` output field of this `ase_task_rename` tool call. Do not
         output anything related to this MCP tool call.
 
         -   If <text/> starts with `ERROR:` or `WARNING:`:
@@ -81,9 +84,9 @@ explicitly requested by this procedure via outputs based on a <template/>!
             </template>
 
     2.  <if condition="<old/> is equal <ase-task-id/>">
-        Set <ase-task-id><new/></ase-task-id>. Call the `task_id(id:
+        Set <ase-task-id><new/></ase-task-id>. Call the `ase_task_id(id:
         <ase-task-id/>, session: <ase-session-id/>)` tool from the `ase`
-        MCP service to switch the task to the renamed task. Only output
+        MCP server to switch the task to the renamed task. Only output
         the following <template/>:
 
         <template>

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

@@ -20,7 +20,9 @@ View a Task Plan
 View a Task Plan
 </skill>
 
+<role>
 Your role is an experienced, *expert-level assistant*.
+</role>
 *View* the task plan.
 
 Procedure
@@ -45,9 +47,9 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
 2.  **Perform Operation**:
 
-    1.  Call the `task_load(id: <id/>)` tool of the `ase` MCP
-        service to load the task plan content and set <text/> to the
-        `text` output field of this `task_load` tool call. Do not
+    1.  Call the `ase_task_load(id: <id/>)` tool of the `ase` MCP
+        server to load the task plan content and set <text/> to the
+        `text` output field of this `ase_task_load` tool call. Do not
         output anything related to this MCP tool call.
 
         -   If <text/> starts with `ERROR:` or `WARNING:`:

package/plugin/commands/ase-code-lint/complete.md

@@ -1,9 +0,0 @@
----
-argument-hint: ""
-description: "During Lint: Complete Code Change"
----
-
-Sorry, your last proposed code change set seems to be not really *complete*,
-as some code changes seem to be missing.
-Please *re-assess* and propose the *entire necessary change set*, all *at once*.
-

package/plugin/commands/ase-code-lint/explain.md

@@ -1,9 +0,0 @@
----
-argument-hint: "<issue>"
-description: "During Lint: Improve Explanation"
----
-
-I am still *musing* on your last proposed code change.
-$ARGUMENTS.
-Please *improve your explanation* and *propose it again*.
-

package/plugin/commands/ase-code-lint/nope.md

@@ -1,11 +0,0 @@
----
-argument-hint: ""
-description: "During Lint: Reject Change and Continue"
----
-
-I *reject* your last proposed code change.
-
-Do *NOT apply* your last code change to the code.
-But please *continue* your plan and *continue*
-to propose further code changes.
-

package/plugin/commands/ase-code-lint/reassess.md

@@ -1,15 +0,0 @@
----
-argument-hint: "<question>"
-description: "During Lint: Re-Assess Last Change"
----
-
-Are you *really sure*? $ARGUMENTS
-
-Please *re-assess* and *reason* on your last proposed code change!
-
-Then, if you are still sure that it is correct, please *propose the code
-change once again* before continuing with your plan.
-
-Otherwise, if you are unsure, be transparent and tell me your new
-reasoned concerns and continue with your plan immediately.
-

package/plugin/commands/ase-code-lint/recheck.md

@@ -1,9 +0,0 @@
----
-argument-hint: ""
-description: "During Lint: Recheck Change"
----
-
-The source code was *updated externally*.
-Please update your last code change against the latest source code
-and *propose the code change again* before you continue following your review.
-

package/plugin/commands/ase-code-lint/refine.md

@@ -1,9 +0,0 @@
----
-argument-hint: "<hint>"
-description: "During Lint: Refine Change"
----
-
-Please *refine* your last proposed code change: $ARGUMENTS.
-Then please propose the refined code change again before
-you continue following your review.
-