@rse/ase 0.0.56 → 0.0.57

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

@@ -1,6 +1,6 @@
 ---
 name: ase-meta-persona
-argument-hint: "[<persona>]"
+argument-hint: "[--help|-h] [<persona>]"
 description: >
     Adjust communication style in four intensity levels of token usage.
     The <persona> can be either the decorative, eloquent, and explaining "writer",
@@ -16,8 +16,14 @@ effort: medium
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
+<skill name="ase-meta-persona">
 Persona Configuration
-=====================
+</skill>
+
+<objective>
+*Configure* the *persona style* of the agent to adjust the communication
+style and token usage intensity.
+</objective>
 
 1.  Determine request:
     <request>$ARGUMENTS</request>

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

@@ -0,0 +1,50 @@
+
+##  NAME
+
+`ase-meta-persona` - Persona Configuration
+
+##  SYNOPSIS
+
+`ase-meta-persona`
+    [`--help`|`-h`]
+    [*persona*]
+
+##  DESCRIPTION
+
+The `ase-meta-persona` skill gets or sets the active *communication
+style* (persona) of the assistant. Four intensity levels of token
+usage are supported, from most verbose to most terse:
+
+-   `writer`: decorative, eloquent, and explaining
+-   `engineer`: concise, factual, and accurate (default)
+-   `telegrapher`: brief, factual, and abbreviating
+-   `caveman`: terse, rough, and stuttering
+
+Without arguments, the skill reports the currently active persona.
+With a *persona* argument, it switches to that persona via the
+`ase_persona` MCP tool.
+
+##  ARGUMENTS
+
+*persona*:
+    The persona to activate; one of `writer`, `engineer`,
+    `telegrapher`, or `caveman`. If omitted, the currently active
+    persona is reported.
+
+##  EXAMPLES
+
+Show the currently active persona:
+
+```text
+❯ /ase-meta-persona
+```
+
+Switch to the telegrapher persona:
+
+```text
+❯ /ase-meta-persona telegrapher
+```
+
+##  SEE ALSO
+
+`ase-task-id`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-meta-quorum
-argument-hint: "<question>"
+argument-hint: "[--help|-h] <question>"
 description: >
     Query Multiple AIs for Quorum Answer.
 user-invocable: true
@@ -14,17 +14,10 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Query Multiple AIs for Quorum Answer
-====================================
-
 <skill name="ase-meta-quorum">
 Query Multiple AIs for Quorum Answer
 </skill>
 
-<role>
-Your role is an *expert-level assistant*.
-</role>
-
 <objective>
 Find a *quorum answer* on an arbitrary question,
 by querying *multiple* AIs for an *optimal consensus*.

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

@@ -0,0 +1,41 @@
+
+##  NAME
+
+`ase-meta-quorum` - Query Multiple AIs for Quorum Answer
+
+##  SYNOPSIS
+
+`ase-meta-quorum`
+    [`--help`|`-h`]
+    *question*
+
+##  DESCRIPTION
+
+The `ase-meta-quorum` skill finds a *quorum answer* on an arbitrary
+question by querying *multiple* AIs (Anthropic Claude itself plus
+OpenAI ChatGPT, Google Gemini, DeepSeek, xAI Grok, Z.AI GLM, and
+Alibaba Qwen) for an *optimal consensus*.
+
+The skill first previews its own answer, then dispatches the same
+query to each available foreign LLM via the `ase:ase-meta-chat`
+sub-agent, summarizes all responses, derives a *consensus rate* on
+a Likert scale of `0..N` (where `N` is the number of available
+responders), and reports the consensus answer alongside the
+complete, unmodified individual responses.
+
+##  ARGUMENTS
+
+*question*:
+    The question to ask all available AIs.
+
+##  EXAMPLES
+
+Ask the quorum a factual question:
+
+```text
+❯ /ase-meta-quorum What are the most common causes of memory leaks in Node.js?
+```
+
+##  SEE ALSO
+
+`ase-meta-chat`, `ase-meta-search`, `ase-meta-evaluate`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-meta-search
-argument-hint: "<query>"
+argument-hint: "[--help|-h] <query>"
 description: >
     Search the Internet/Web with a query.
     Prefer this skill before using Perplexity, Brave and WebSearch.
@@ -18,17 +18,10 @@ allowed-tools:
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Search the Internet/Web
-=======================
-
 <skill name="ase-meta-search">
 Search the Internet/Web
 </skill>
 
-<role>
-Your role is an expert-level *web specialist*.
-</role>
-
 <objective>
 Your objective is to *search* the *Internet*/*Web* for the following query:
 <query>$ARGUMENTS</query>

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

@@ -0,0 +1,39 @@
+
+##  NAME
+
+`ase-meta-search` - Search the Internet/Web
+
+##  SYNOPSIS
+
+`ase-meta-search`
+    [`--help`|`-h`]
+    *query*
+
+##  DESCRIPTION
+
+The `ase-meta-search` skill searches the *Internet*/*Web* for the
+given *query*. It dispatches the query in parallel to all available
+search services (Perplexity, Brave, Exa, and Claude's built-in
+`WebSearch`) via the `ase:ase-meta-search` sub-agent and consolidates
+all responses into a single answer without removing original
+information.
+
+This skill should be preferred over directly invoking Perplexity,
+Brave, or `WebSearch` individually.
+
+##  ARGUMENTS
+
+*query*:
+    The search query to dispatch to the search services.
+
+##  EXAMPLES
+
+Search the Web for a topic:
+
+```text
+❯ /ase-meta-search latest stable release of TypeScript and release notes
+```
+
+##  SEE ALSO
+
+`ase-meta-chat`, `ase-meta-quorum`, `ase-arch-discover`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-meta-why
-argument-hint: "<fact>"
+argument-hint: "[--help|-h] <fact>"
 description: >
     Five-Whys Root-Cause Analysis.
 user-invocable: true
@@ -11,17 +11,10 @@ effort: medium
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Five-Whys Root-Cause Analysis
-=============================
-
 <skill name="ase-meta-why">
 Five-Whys Root-Cause Analysis
 </skill>
 
-<role>
-Your role is an *expert-level assistant*.
-</role>
-
 <objective>
 Apply the *Five-Whys* *root-cause analysis* technique to investigate
 the following problem:

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

@@ -0,0 +1,39 @@
+
+##  NAME
+
+`ase-meta-why` - Five-Whys Root-Cause Analysis
+
+##  SYNOPSIS
+
+`ase-meta-why`
+    [`--help`|`-h`]
+    *fact*
+
+##  DESCRIPTION
+
+The `ase-meta-why` skill applies the *Five-Whys* *root-cause
+analysis* technique to the supplied *fact*. The skill iteratively
+asks "why" — up to five times — to drill down from surface symptoms
+to the underlying root cause, considering technical, domain-specific,
+process-related, and organizational causes. After identifying the
+root cause it proposes a *SOLUTION* that addresses it, optionally
+including concrete source code changes.
+
+##  ARGUMENTS
+
+*fact*:
+    The observed *fact* (symptom, problem, or surprising outcome)
+    whose root cause should be investigated. The skill implicitly
+    prepends "Why" to form the initial question.
+
+##  EXAMPLES
+
+Investigate the root cause of a build failure:
+
+```text
+❯ /ase-meta-why the CI build is intermittently failing on macOS runners
+```
+
+##  SEE ALSO
+
+`ase-code-analyze`, `ase-code-resolve`, `ase-arch-analyze`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-delete
-argument-hint: "[<id>]"
+argument-hint: "[--help|-h] [<id>]"
 description: >
     Delete the current or given task plan.
     Use when the user calls to "delete", "remove" or "clear" the
@@ -13,17 +13,13 @@ effort: low
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Delete a Task Plan
-==================
-
 <skill name="ase-task-delete">
 Delete a Task Plan
 </skill>
 
-<role>
-Your role is an experienced, *expert-level assistant*.
-</role>
+<objective>
 *Delete* the task plan.
+</objective>
 
 Procedure
 ---------

package/plugin/skills/ase-task-delete/help.md

@@ -0,0 +1,47 @@
+
+##  NAME
+
+`ase-task-delete` - Delete a Task Plan
+
+##  SYNOPSIS
+
+`ase-task-delete`
+    [`--help`|`-h`]
+    [*id*]
+
+##  DESCRIPTION
+
+The `ase-task-delete` skill deletes the *task plan* identified by
+*id*. If *id* is omitted, the *current* task id (inherited from the
+session context) is used. When the deleted task is the current task
+and not the `default` task, the current task id is automatically
+switched back to `default`.
+
+The task plan is stored in `.ase/tasks/`*id*`/plan.md` files of the
+project and can be alternatively deleted with the
+"`ase task delete` *id*" command from outside the agent tool.
+
+##  ARGUMENTS
+
+*id*:
+    The unique identifier of the task plan to delete. If omitted,
+    the current task id is used.
+
+##  EXAMPLES
+
+Delete the current task plan:
+
+```text
+❯ /ase-task-delete
+```
+
+Delete a specific task plan:
+
+```text
+❯ /ase-task-delete hello
+```
+
+##  SEE ALSO
+
+`ase-task-edit`, `ase-task-list`, `ase-task-view`,
+`ase-task-rename`, `ase-task-reboot`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-edit
-argument-hint: "[<id> | <id>: <instruction> | <instruction>]"
+argument-hint: "[--help|-h] [--plan|-p <option>] [--next|-n <option>] [<id> | <id>: <instruction> | <instruction>]"
 description: >
     Iteratively edit and refine a named plan for a task through a
     conversational loop. Each round, the current plan is shown and the
@@ -17,9 +17,6 @@ effort: high
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Iteratively Edit a Task Plan
-============================
-
 <skill name="ase-task-edit">
 Iteratively Edit a Task Plan
 </skill>
@@ -30,16 +27,12 @@ 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>
-
+<objective>
 Establish and refine the *task plan* purely through a *chat-driven
-loop*. The user steers each round via interactive dialog that offers
+loop*. The user steers each round via an interactive dialog that offers
 continued refinement, finalization, or hand-off to implementation or
 preflight.
+</objective>
 
 @${CLAUDE_SKILL_DIR}/../../meta/ase-plan.md
 

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

@@ -0,0 +1,75 @@
+
+##  NAME
+
+`ase-task-edit` - Iteratively Edit a Task Plan
+
+##  SYNOPSIS
+
+`ase-task-edit`
+    [`--help`|`-h`]
+    [`--plan`|`-p` *option*]
+    [`--next`|`-n` *option*]
+    [*id* | *id*: *instruction* | *instruction*]
+
+##  DESCRIPTION
+
+The `ase-task-edit` skill establishes and refines a *task plan* purely
+through a *chat-driven loop*. The user steers each round via an
+interactive dialog that offers continued refinement, finalization, or
+hand-off to implementation or preflight.
+
+The task plan is stored in `.ase/tasks/`*id*`/plan.md` files of the
+project and can be alternatively edited with the "`ase task edit` *id*"
+command from outside the agent tool.
+
+##  OPTIONS
+
+`--plan`|`-p` *option*:
+    Automatically answer the user dialog for the plan refinement
+    with *option*, which can be either `none` (default, interactive
+    answer required), `OVERWRITE` (overwrite an existing plan
+    with *instruction*), `REFINE` (refine the existing plan with
+    *instruction*), or `PRESERVE` (preserve the existing plan by
+    ignoring *instruction* and stopping skill processing).
+
+`--next`|`-n` *option*:
+    Automatically answer the user dialog for the next step (at the end
+    of this skill) with *option*, which can be either `none` (default,
+    interactive answer required), `DONE` (no next step), `IMPLEMENT`
+    (hand-over to `ase-task-implement`), `PREFLIGHT` (hand-over to
+    `ase-task-preflight`), or `REFINE` (refine the plan with subsequent
+    instruction).
+
+##  ARGUMENTS
+
+*id* | *id*: *instruction* | *instruction*:
+    Edit the task with the unique identifier *id* (default: `default`).
+    Optionally, *instruction* either gives instructions for creating a
+    new task or gives instructions for refining an existing task.
+
+##  EXAMPLES
+
+Edit the current task:
+
+```text
+❯ /ase-task-edit
+```
+
+Create a new task under id `hello`:
+
+```text
+❯ /ase-task-delete hello
+❯ /ase-task-edit hello: new "ase hello" CLI command which prints
+  a nice "Hello World!" to the terminal in color blue.
+```
+
+Further refine the task under id `hello`:
+
+```text
+❯ /ase-task-edit hello: change the color to red.
+```
+
+##  SEE ALSO
+
+`ase-task-reboot`, `ase-task-preflight`, `ase-task-implement`,
+`ase-task-view`, `ase-task-list`, `ase-task-rename`, `ase-task-delete`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-id
-argument-hint: "[<id>]"
+argument-hint: "[--help|-h] [<id>]"
 description: >
     Get or set unique task id <id>.
     Use when user requests to work on a certain task
@@ -13,13 +13,14 @@ effort: low
 @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 
-Task Configuration
-==================
-
 <skill name="ase-task-id">
 Configure Task Id
 </skill>
 
+<objective>
+*Get* or *set* the unique *task id* of the current session.
+</objective>
+
 1.  Determine request:
     <request>$ARGUMENTS</request>
 

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

@@ -0,0 +1,42 @@
+
+##  NAME
+
+`ase-task-id` - Configure Task Id
+
+##  SYNOPSIS
+
+`ase-task-id`
+    [`--help`|`-h`]
+    [*id*]
+
+##  DESCRIPTION
+
+The `ase-task-id` skill gets or sets the unique *task id* for the
+current session. Without arguments, it reports the currently active
+task id. With an *id* argument, it switches the session to that
+task id via the `ase_task_id` MCP tool.
+
+##  ARGUMENTS
+
+*id*:
+    The new task id to activate. If omitted, the currently active
+    task id is reported.
+
+##  EXAMPLES
+
+Show the current task id:
+
+```text
+❯ /ase-task-id
+```
+
+Switch to a specific task:
+
+```text
+❯ /ase-task-id hello
+```
+
+##  SEE ALSO
+
+`ase-task-list`, `ase-task-edit`, `ase-task-view`,
+`ase-task-rename`, `ase-task-delete`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-implement
-argument-hint: "[<id>]"
+argument-hint: "[--help|-h] [--next|-n <option>] [<id>]"
 description: >
     Implement current or given task plan.
     Use when the user calls to "implement", "realize" or "apply" the
@@ -15,9 +15,6 @@ effort: xhigh
 @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Implement a Task Plan
-=====================
-
 <skill name="ase-task-implement">
 Implement a Task Plan
 </skill>
@@ -28,13 +25,10 @@ Implement a Task Plan
     $ARGUMENTS
 </expand>
 
-<role>
-Your role is an experienced, *expert-level assistant*,
-specialized in the *implementation* of changes.
-</role>
-
+<objective>
 *Implement* the task plan by modifying the *artifacts*
 with a corresponding, complete *change set*.
+</objective>
 
 Procedure
 ---------

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

@@ -0,0 +1,56 @@
+
+##  NAME
+
+`ase-task-implement` - Implement a Task Plan
+
+##  SYNOPSIS
+
+`ase-task-implement`
+    [`--help`|`-h`]
+    [`--next`|`-n` *option*]
+    [*id*]
+
+##  DESCRIPTION
+
+The `ase-task-implement` skill performs the *final implementation*
+of a task plan by modifying the corresponding *artifacts* with a
+complete *change set*. The plan is loaded from
+`.ase/tasks/`*id*`/plan.md`, and any optional `IMPLEMENTATION DRAFT`
+section produced by `ase-task-preflight` is used as a hint — the
+plain plan content always overrules the draft.
+
+After implementation, the user is asked whether to preserve or
+delete the task plan, unless `--next` pre-selects this choice.
+
+##  OPTIONS
+
+`--next`|`-n` *option*:
+    Automatically answer the user dialog for the next step with
+    *option*, which can be either `none` (default, interactive
+    answer required), `DONE` (preserve task plan and stop), or
+    `DELETE` (hand off to `ase-task-delete`).
+
+##  ARGUMENTS
+
+*id*:
+    The unique identifier of the task whose plan should be
+    implemented. If omitted, the *current* task id is used.
+
+##  EXAMPLES
+
+Implement the current task plan:
+
+```text
+❯ /ase-task-implement
+```
+
+Implement a specific task and delete the plan when done:
+
+```text
+❯ /ase-task-implement --next DELETE hello
+```
+
+##  SEE ALSO
+
+`ase-task-edit`, `ase-task-preflight`, `ase-task-reboot`,
+`ase-task-view`, `ase-task-delete`.

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

@@ -1,6 +1,6 @@
 ---
 name: ase-task-list
-argument-hint: "[-v|--verbose]"
+argument-hint: "[--help|-h] [--verbose|-v]"
 description: >
     List all available task ids.
     Use when user wants to see all tasks.
@@ -13,9 +13,6 @@ effort: low
 @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
 @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
 
-Task List
-=========
-
 <skill name="ase-task-list">
 List Task Plans
 </skill>
@@ -26,6 +23,10 @@ List Task Plans
     $ARGUMENTS
 </expand>
 
+<objective>
+*List* all available *task plans* of the current project.
+</objective>
+
 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

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

@@ -0,0 +1,43 @@
+
+##  NAME
+
+`ase-task-list` - List Task Plans
+
+##  SYNOPSIS
+
+`ase-task-list`
+    [`--help`|`-h`]
+    [`--verbose`|`-v`]
+
+##  DESCRIPTION
+
+The `ase-task-list` skill lists all available *task ids* in the
+current project by calling the `ase_task_list` MCP tool. In the
+default mode, only the task ids are rendered as a single-column
+Markdown table. In verbose mode, the last-modified timestamp of
+each task plan is rendered as an additional column.
+
+##  OPTIONS
+
+`--verbose`|`-v`:
+    Render an additional `Last Modified` column with the
+    `YYYY-MM-DD HH:MM` timestamp of each task plan.
+
+##  EXAMPLES
+
+List all task ids:
+
+```text
+❯ /ase-task-list
+```
+
+List all task ids together with their last-modified timestamps:
+
+```text
+❯ /ase-task-list --verbose
+```
+
+##  SEE ALSO
+
+`ase-task-id`, `ase-task-view`, `ase-task-edit`,
+`ase-task-rename`, `ase-task-delete`.