@rse/ase 0.9.45 → 0.9.47

package/plugin/skills/ase-help-skill/SKILL.md

@@ -0,0 +1,203 @@
+---
+name: ase-help-skill
+argument-hint: "[--help|-h] [<skill-name>]"
+description: >
+    Show the manual page of an ASE skill, addressed by its full name, by
+    any abbreviation of it, or by a description of its purpose, and list
+    the entire skill catalog when no name is given. Use when the user
+    wants the "manual", "man page", "manpage", or "help" of a particular
+    ASE skill, or asks what a certain `ase-xxx-xxx` skill does.
+user-invocable: true
+disable-model-invocation: false
+effort: medium
+allowed-tools:
+    - "Read"
+---
+
+@${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-help-skill">
+Show the Manual Page of an ASE Skill
+</skill>
+
+<expand name="getopt"
+    arg1="ase-help-skill"
+    arg2="">
+    $ARGUMENTS
+</expand>
+
+<objective>
+*Show* the *manual page* of the ASE skill addressed by the following
+skill name, abbreviation of it, or description of its purpose:
+<skill-ref><getopt-arguments/></skill-ref>
+</objective>
+
+The following <catalog/> is index of all ASE skills -- one
+`⎈ **<group/>**` entry per skill group and one
+``○ `<name/>`: <purpose/>`` entry per skill -- and this is
+the *sole* index <skill-ref/> is resolved against:
+
+<catalog>
+@${CLAUDE_SKILL_DIR}/catalog.md
+</catalog>
+
+<flow>
+
+1.  <step id="STEP 1: Resolve Skill Name">
+
+    1.  <if condition="<skill-ref/> is empty">
+        No particular skill was addressed, so render the *entire*
+        <catalog/> as a browsable list with the following <template/>
+        -- one list entry per catalog entry, in catalog order, where
+        <name/> and <purpose/> are the two fields of the entry (and
+        <name-padded/> is <name/>, padded to 22 characters with
+        spaces on the right) -- and then immediately *STOP* processing
+        the entire current skill:
+
+        <template>
+        <ase-tpl-head title="SKILL CATALOG"/>
+
+        <catalog/>
+
+        <ase-tpl-foot title="SKILL CATALOG"/>
+
+        ⧉ **ASE**: ✪ skill: **ase-help-skill**, ▶ hint: **run `/ase-help-skill ase-xxx-xxx` for manual page of individual skill**
+        </template>
+        </if>
+
+    2.  Set <skill-ref-raw/> to <skill-ref/> with only its leading and
+        trailing whitespace stripped, as the *verbatim* wording of the
+        user is required later on.
+
+        *Normalize* <skill-ref/> by stripping all leading and trailing
+        whitespace and then, repeatedly, any leading `/` and `ase:`
+        prefix, so that `ase-code-lint`, `/ase-code-lint`,
+        `ase:ase-code-lint`, and `/ase:ase-code-lint` all normalize to
+        `ase-code-lint`. Do not output anything.
+
+    3.  Resolve the normalized <skill-ref/> against <catalog/> in *three*
+        tiers and store the outcome in <candidates/>. Each tier is tried
+        only if all preceding tiers yielded *no* candidate at all:
+
+        1.  *Exact Name Tier*:
+
+            If a catalog *name* is *equal* to <skill-ref/>, set
+            <candidates/> to exactly that *single* name.
+
+        2.  *Substring Name Tier*:
+
+            Set <candidates/> to *all* catalog *names* *containing*
+            <skill-ref/> as a substring, in alphabetical order.
+
+        3.  *Fuzzy Purpose Tier*:
+
+            Set <candidates/> to *all* catalog names whose *purpose* --
+            the part *after* the colon of the catalog entry -- *fuzzily*
+            matches <skill-ref-raw/>, in *descending* order of match
+            quality. Match against <skill-ref-raw/>, and *not* against
+            <skill-ref/>, as this tier matches free-text wording, which
+            the normalization of sub-step 2 would distort.
+
+            A purpose matches fuzzily if it shares the topic, the
+            wording, or evident synonyms with <skill-ref-raw/>, so
+            that e.g. `manpage` matches `Show the Manual Page of an
+            ASE Skill` and `root cause` matches `Five-Whys Root-Cause
+            Analysis`. Include *plausible* matches only -- if none is
+            plausible, leave <candidates/> empty.
+
+        Set <count/> to the number of entries in <candidates/>.
+        Do not output anything.
+
+    </step>
+
+2.  <step id="STEP 2: Dispatch Resolution">
+
+    1.  <if condition="<count/> is equal 0">
+        Only output the following <template/> and then immediately
+        *STOP* processing the entire current skill:
+
+        <template>
+        ⧉ **ASE**: ✪ skill: **ase-help-skill**, ▶ ERROR: unknown skill: **<skill-ref-raw/>**
+        </template>
+        </if>
+
+    2.  <elseif condition="<count/> is equal 1">
+        Set <name/> to the single entry of <candidates/> and continue
+        processing. Do not output anything.
+        </elseif>
+
+    3.  <else>
+        The abbreviation is *ambiguous*, so let the user pick the
+        intended skill.
+
+        Set <shown/> to the *first* 9 entries of <candidates/>, as the
+        dialog renders at most *nine* answer lines.
+
+        <if condition="<count/> is greater than 9">
+            Set <truncation> (showing 9 of <count/> candidates)</truncation>
+        </if>
+        <else>
+            Set <truncation></truncation> (set to empty)
+        </else>
+
+        In the following, you *MUST* *NOT* use your built-in
+        <user-dialog-tool/> tool! Instead, you *MUST* just show a custom
+        dialog according to the expanded `custom-dialog` definition. You
+        *MUST* closely follow this definition.
+
+        Let the user select the intended skill by raising a question
+        with the following custom dialog, where each answer line
+        corresponds to one entry of <shown/>, using the catalog *name*
+        as the label and its catalog *purpose* as the description:
+
+        <expand name="custom-dialog" arg1="--no-other">
+            Ambiguous Skill: Which skill's manual page should be shown?<truncation/>
+            <name/>: <purpose/>
+            [...]
+        </expand>
+
+        Check the <result/> and dispatch accordingly:
+
+        -   If <result/> is `CANCEL`:
+            *STOP* processing without any further output.
+
+        -   Otherwise: Set <name/> to the selected skill name and
+            continue processing.
+        </else>
+
+    </step>
+
+3.  <step id="STEP 3: Render Manual Page">
+
+    1.  Use the `Read` tool to read the manual page of the resolved
+        skill <name/> and set <manual/> to its content. The file path is
+        formed by joining <ase-plugin-root/> and `skills/<name/>/help.md`
+        with exactly *one* `/` separator, as <ase-plugin-root/> may or
+        may not carry a trailing `/`. Do not output anything related to
+        this tool call.
+
+    2.  <if condition="<manual/> is empty or could not be read">
+        Only output the following <template/> and then immediately
+        *STOP* processing the entire current skill:
+
+        <template>
+        ⧉ **ASE**: ✪ skill: **ase-help-skill**, ▶ ERROR: unreadable manual page: **<name/>**
+        </template>
+        </if>
+
+    3.  Treat <manual/> as *verbatim* Markdown. You *MUST* *NOT*
+        truncate, summarize, reformat, or partially show it. Only output
+        the following <template/>:
+
+        <template>
+        <ase-tpl-head title="MANUAL PAGE: <name/>"/>
+        <manual/>
+        <ase-tpl-foot title="MANUAL PAGE: <name/>"/>
+        </template>
+
+    </step>
+
+</flow>

package/plugin/skills/ase-help-skill/catalog.md

@@ -0,0 +1,60 @@
+
+⎈   **HELP**
+○   `ase-help-skill`:      Show the Manual Page of an ASE Skill
+○   `ase-help-intent`:     Match an Intent to an ASE Command
+
+⎈   **RESEARCH**
+○   `ase-meta-search`:     Search the Internet/Web
+○   `ase-meta-proximity`:  Determine the Conceptual Proximity of a Topic
+○   `ase-meta-brainstorm`: Collaboratively Brainstorm a Topic
+○   `ase-meta-chat`:       Query Foreign LLM for Chat
+○   `ase-meta-quorum`:     Query Multiple AIs for Quorum Answer
+○   `ase-meta-diaboli`:    Play "Devil's Advocate" (Latin: "Advocatus Diaboli")
+○   `ase-meta-steelman`:   Build the "Steelman" Argument
+○   `ase-meta-eli5`:       Explain a Topic Like I'm 5
+○   `ase-meta-why`:        Five-Whys Root-Cause Analysis
+○   `ase-meta-evaluate`:   Evaluate Alternatives
+
+⎈   **ARCHITECTURE**
+○   `ase-arch-analyze`:    Review Software Architecture
+○   `ase-arch-discover`:   Discover Components
+
+⎈   **CODING**
+○   `ase-code-analyze`:    Analyze Source Code
+○   `ase-code-lint`:       Lint Source Code
+○   `ase-code-explain`:    Explain Source Code
+○   `ase-code-insight`:    Project Insight
+○   `ase-code-craft`:      Craft Source Code
+○   `ase-code-refactor`:   Refactor Artifacts
+○   `ase-code-resolve`:    Resolve Problem
+○   `ase-sync-import`:     Import Foreign Sources into Artifact Set
+○   `ase-sync-reconcile`:  Reconcile Artifact Set to Artifact Set
+○   `ase-sync-export`:     Export Artifact Set to Side-by-Side Files
+
+⎈   **DOCUMENTATION**
+○   `ase-docs-distill`:    Distill Document Key Points
+○   `ase-docs-proofread`:  Proofread Documents
+
+⎈   **VERSION CONTROL**
+○   `ase-meta-changelog`:  Update ChangeLog Entries
+○   `ase-meta-commit`:     Git Commit Message
+○   `ase-meta-diff`:       Summarize Diff
+○   `ase-meta-review`:     Review Staged Changes
+
+⎈   **TASK MANAGEMENT**
+○   `ase-task-id`:         Configure Task Id
+○   `ase-task-list`:       List Task Plans
+○   `ase-task-view`:       View a Task Plan
+○   `ase-task-edit`:       Iteratively Edit a Task Plan
+○   `ase-task-grill`:      Iteratively Grill a Task Plan
+○   `ase-task-condense`:   Condense a Task Plan
+○   `ase-task-reboot`:     Reboot a Task Plan
+○   `ase-task-preflight`:  Preflight a Task Plan
+○   `ase-task-implement`:  Implement a Task Plan
+○   `ase-task-rename`:     Rename a Task Plan
+○   `ase-task-delete`:     Delete a Task Plan
+
+⎈   **OTHER SKILLS**
+○   `ase-meta-persona`:    Persona Configuration
+○   `ase-meta-compat`:     Self-Test ASE Compatibility
+

package/plugin/skills/ase-help-skill/help.md

@@ -0,0 +1,83 @@
+
+##  NAME
+
+`ase-help-skill` - Show the Manual Page of an ASE Skill
+
+##  SYNOPSIS
+
+`ase-help-skill`
+    [`--help`|`-h`]
+    [*skill-name*]
+
+##  DESCRIPTION
+
+The `ase-help-skill` skill renders the *manual page* (`help.md`) of the
+ASE skill addressed by *skill-name*. The page is emitted verbatim,
+framed between a `( HELP )` header and footer rule.
+
+The *skill-name* is resolved against a *catalog* of all ASE skills --
+one `name: purpose` entry per skill, generated into
+`skills/ase-help-skill/data.md` by `npm start build` in `plugin/`.
+Before resolving, any leading `/` and `ase:` prefix is stripped, so
+`ase-code-lint`, `/ase-code-lint`, and `ase:ase-code-lint` are
+equivalent. Resolution then proceeds in three tiers, each tried only if
+all preceding ones found nothing: an *exact* match on the full skill
+name wins outright, otherwise *every* skill name containing
+*skill-name* as a substring becomes a candidate, and otherwise
+*skill-name* is *fuzzily* matched against the skill *purposes* -- so
+a topical phrase such as `root cause` still finds `ase-meta-why` --
+with the candidates ordered by descending match quality.
+
+A *skill-name* matching no skill in any tier is reported as an error. A
+*skill-name* matching more than one skill opens an interactive dialog
+listing the candidates with their purposes; as the dialog renders at
+most nine answer lines, a broader abbreviation such as `task` shows the
+first nine candidates and states how many exist in total.
+
+If *skill-name* is omitted, the whole catalog is rendered as a
+browsable `Skill`/`Purpose` table instead.
+
+The skill exposes *no* option flags beyond `--help`/`-h`.
+
+##  ARGUMENTS
+
+*skill-name*:
+    The full name of the ASE skill, any abbreviation of it, or a
+    description of its purpose. If omitted, the entire skill catalog is
+    listed.
+
+##  EXAMPLES
+
+Show the manual page of `ase-code-lint` via its shortest abbreviation:
+
+```text
+❯ /ase-help-skill lint
+```
+
+Show the same manual page via its full, plugin-qualified name:
+
+```text
+❯ /ase-help-skill ase:ase-code-lint
+```
+
+Pick a manual page from the candidates of an ambiguous abbreviation:
+
+```text
+❯ /ase-help-skill analyze
+```
+
+Find a manual page by the purpose of the skill instead of its name:
+
+```text
+❯ /ase-help-skill root cause
+```
+
+List the entire skill catalog:
+
+```text
+❯ /ase-help-skill
+```
+
+##  SEE ALSO
+
+[`ase-help-intent`](../ase-help-intent/help.md), [`ase-meta-proximity`](../ase-meta-proximity/help.md).

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

@@ -0,0 +1,116 @@
+---
+name: ase-meta-eli5
+argument-hint: "[--help|-h] [--ground|-g] <topic>"
+description: >
+    Explain a topic in "Explain Like I'm 5" (ELI5) style, optionally
+    grounded in Internet/Web facts. Use when the user wants a topic
+    explained in a very simple, child-friendly way, or mentions "eli5"
+    or "explain like I'm 5".
+user-invocable: true
+disable-model-invocation: false
+effort: high
+allowed-tools:
+    - "Agent"
+---
+
+@${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-eli5">
+Explain a Topic Like I'm 5
+</skill>
+
+<expand name="getopt"
+    arg1="ase-meta-eli5"
+    arg2="--ground|-g">
+    $ARGUMENTS
+</expand>
+
+<objective>
+*Explain* the following topic in "Explain Like I'm 5" (ELI5) style,
+so that even a five year old child could understand it:
+<topic><getopt-arguments/></topic>
+</objective>
+
+<flow>
+
+1.  <step id="STEP 1: Check Topic">
+
+    <if condition="<topic/> is empty">
+    Only output the following <template/> and then immediately *STOP*
+    processing the entire current skill:
+
+    <template>
+    ⧉ **ASE**: ✪ skill: **ase-meta-eli5**, ▶ ERROR: expected a `<topic>` argument
+    </template>
+    </if>
+
+    Set <facts></facts> (set to empty)
+
+    </step>
+
+2.  <step id="STEP 2: Ground Topic" condition="<getopt-option-ground/> is equal `true`">
+
+    Use the `ase-meta-search` skill in a sub-agent to gather facts
+    about the <topic/>: call the tool...
+
+    `Agent(
+        description: "Query Web Search Service",
+        subagent_type: "ase:ase-meta-search",
+        prompt: "Search the Internet/Web and gather facts about the following topic: <topic/>",
+        run_in_background: false
+    )`
+
+    ...and store the returned facts in <facts/>.
+
+    <if condition="<facts/> contains no usable facts about <topic/>">
+
+    Set <facts></facts> (set facts to empty), so the explanation below
+    falls back to model knowledge, and output the following <template/>:
+
+    <template>
+    <ase-tpl-bullet-secondary/> **WARNING**: grounding found no usable facts -- falling back to model knowledge.
+    </template>
+
+    </if>
+
+    </step>
+
+3.  <step id="STEP 3: Explain Topic">
+
+    Explain the <topic/> in "Explain Like I'm 5" (ELI5) style: use
+    *simple*, *jargon-free* wording a five year old child could
+    understand -- short sentences, everyday words, and familiar images.
+    Do *not* use technical terms without immediately putting them into
+    child-friendly words.
+
+    <if condition="<facts/> is not empty">
+    Ground the explanation in the facts of <facts/> and do not
+    contradict them.
+    </if>
+
+    For this, first, explain *WHAT* the topic is and store it in
+    <what/>. Second, give an *ANALOGY* by comparing the topic to
+    something from the everyday life of a child and store this in
+    <analogy/>. Third, explain *WHY* the topic matters and store this in
+    <why/>.
+
+    Ensure that each of <what/>, <analogy/>, and <why/> is a *very
+    brief* and *concise* single text paragraph.
+
+    Output the result with the following <template/>:
+
+    <template>
+    <ase-tpl-bullet-secondary/> **TOPIC**: **<topic/>**
+
+    <ase-tpl-bullet-normal/> **WHAT**: <what/>.
+
+    <ase-tpl-bullet-normal/> **ANALOGY**: <analogy/>.
+
+    <ase-tpl-bullet-signal/> **WHY**: <why/>.
+    </template>
+
+    </step>
+
+</flow>

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

@@ -0,0 +1,61 @@
+
+##  NAME
+
+`ase-meta-eli5` - Explain a Topic Like I'm 5
+
+##  SYNOPSIS
+
+`ase-meta-eli5`
+    [`--help`|`-h`]
+    [`--ground`|`-g`]
+    *topic*
+
+##  DESCRIPTION
+
+The `ase-meta-eli5` skill explains the supplied *topic* in "Explain
+Like I'm 5" (ELI5) style, so that even a five year old child could
+understand it. The explanation uses simple, jargon-free wording --
+short sentences, everyday words, and familiar images -- and is
+structured into three labeled blocks: *WHAT* (a plain-words summary),
+*ANALOGY* (a concrete everyday-life comparison), and *WHY* (why the
+topic matters), each kept brief with 1-3 bullet points.
+
+By default the explanation is derived from model knowledge only. With
+the `--ground`/`-g` option, the skill first searches the Internet/Web
+for facts about the topic via the `ase-meta-search` skill (dispatched
+in a sub-agent, querying all available search backends) and grounds
+the explanation in the found facts. If the grounding yields no usable
+facts, a warning is emitted and the explanation falls back to model
+knowledge.
+
+##  OPTIONS
+
+`--ground`|`-g`:
+    Ground the explanation in Internet/Web facts gathered via the
+    `ase-meta-search` skill before explaining. Without this option,
+    the explanation is derived from model knowledge only.
+
+##  ARGUMENTS
+
+*topic*:
+    The topic to be explained. It may be a technical concept, a
+    phenomenon, or any other subject; the skill explains it in a
+    child-friendly way.
+
+##  EXAMPLES
+
+Explain a technical concept from model knowledge:
+
+```text
+❯ /ase-meta-eli5 What is a Fourier transform?
+```
+
+Explain a recent topic grounded in Internet/Web facts:
+
+```text
+❯ /ase-meta-eli5 --ground What is Agentic Software Engineering?
+```
+
+##  SEE ALSO
+
+[`ase-code-explain`](../ase-code-explain/help.md), [`ase-meta-search`](../ase-meta-search/help.md), [`ase-docs-distill`](../ase-docs-distill/help.md).