@rse/ase 0.9.64 → 0.9.66

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

@@ -35,29 +35,29 @@ the highest-ranked option or a principled synthesis of the shortlist.
 
 ##  OPTIONS
 
-`--max-clarify`|`-c=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.
 
-`--min-ideas`|`-i=12`:
+-   `--min-ideas`|`-i=12`:
     The *minimum* number of candidate ideas to generate in the *diverge*
     phase before converging (default: 12). Raise it for a broader idea
     space, lower it for a quicker, narrower session.
 
-`--min-rank`|`-r=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`|`-s=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.
 
 ##  ARGUMENTS
 
-*topic*:
+-   *topic*:
     The subject to brainstorm - a feature, component, behavior, or
     design question to explore *what* to build before *how*.
 

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

@@ -19,11 +19,11 @@ without any further interpretation.
 
 ##  ARGUMENTS
 
-*llm*:
+-   *llm*:
     Identifier of the foreign LLM to query, e.g. `chatgpt`,
     `gemini`, `deepseek`, `grok`, `glm`, or `qwen`.
 
-*query*:
+-   *query*:
     The chat message to send to the foreign LLM.
 
 ##  SCENARIOS

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

@@ -73,7 +73,7 @@ preset-bootstrapping operation that stays a shell concern next to
 
 ##  OPTIONS
 
-`--scope`|`-s` *scope*:
+-   `--scope`|`-s` *scope*:
     The scope chain to operate on, given as a comma-separated list of
     `user`, `project`, `task:`*id*, and/or `session:`*id* terms, in any
     order and at most one term per kind. The `user` term is always
@@ -87,10 +87,10 @@ preset-bootstrapping operation that stays a shell concern next to
 
 ##  ARGUMENTS
 
-*operation*:
+-   *operation*:
     The operation to perform; one of `list`, `get`, `set`, or `delete`.
 
-*args*:
+-   *args*:
     The operands of the operation: none for `list`, a dotted *key* for
     `get` and `delete`, and a dotted *key* plus a *value* for `set`.
 

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

@@ -41,12 +41,12 @@ contrarian.
 
 ##  ARGUMENTS
 
-`--count`, `-c` *count*:
+-   `--count`, `-c` *count*:
     Surface at least *count* strong anti-theses (default *10*) before
     sorting and reporting the top *count* and deriving the *SYNTHESIS*. An
     invalid or non-positive *count* reverts to the default *10*.
 
-*thesis*:
+-   *thesis*:
     The statement, claim, or position to be relentlessly challenged.
     It may be technical, factual, or opinion-based; the skill attacks
     its strongest ("steelman") interpretation.

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

@@ -53,21 +53,21 @@ giving a visual sense of *what a diff endangers* before a deeper review.
 
 ##  ARGUMENTS
 
-`--coherence`, `-c`:
+-   `--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* or *stray
     debug* - then emit an overall **COHERENT** / **INCOHERENT** verdict
     with a table of the flagged hunks.
 
-`--risk`, `-r`:
+-   `--risk`, `-r`:
     In addition to the intent-grouped summary, score the diff against
     the *coupling-criticality-coverage-reversibility* rubric and emit a
     *graded risk report* with an overall risk band and per-axis
     *mitigations*. Scores are equal-weighted, evidence-backed, and
     deliberately untuned to the project.
 
-`--blast`, `-b`:
+-   `--blast`, `-b`:
     In addition to the intent-grouped summary, render a *blast-radius
     map* - a Mermaid `flowchart` of the *touched modules* and their
     *reverse dependencies* - plus a *brief impact summary* of what

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

@@ -30,14 +30,14 @@ knowledge.
 
 ##  OPTIONS
 
-`--ground`|`-g`:
+-   `--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*:
+-   *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.

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

@@ -27,7 +27,7 @@ all alternatives rate negatively.
 
 ##  ARGUMENTS
 
-*request*:
+-   *request*:
     A description of what should be evaluated, including the
     alternatives and, optionally, the criteria to consider.
 

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

@@ -0,0 +1,157 @@
+---
+name: ase-meta-mint
+argument-hint: "[--help|-h] [--type|-t uuid|sha1|const|var|class|func|path|name] [--count|-c <count>] [<hint>]"
+description: >
+    Mint an identifier or a name of a requested type out of a free-text
+    hint: a UUID, a SHA-1 digest, a constant, variable, function, or
+    class identifier, a path component, or a product-like name. Use when
+    the user wants an identifier, id, symbol, slug, or name "minted",
+    "coined", "derived", or "generated" from a description.
+user-invocable: true
+disable-model-invocation: false
+effort: high
+---
+
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
+
+<purpose name="ase-meta-mint">
+Mint an Identifier or Name
+</purpose>
+
+<expand name="getopt"
+    arg1="ase-meta-mint"
+    arg2="--type|-t=(uuid|sha1|const|var|class|func|path|name) --count|-c=1">
+    $ARGUMENTS
+</expand>
+
+<objective>
+*Mint* an identifier or a name of the requested type out of the
+following hint:
+<hint><getopt-arguments/></hint>
+</objective>
+
+<flow>
+
+1.  <step id="STEP 1: Sanity Check Usage">
+
+    1.  Set <type><getopt-option-type/></type> and set <hint/> to
+        <getopt-arguments/> with any leading and trailing whitespace
+        stripped.
+
+    2.  Determine the number of identifiers to mint: set <count/> to
+        <getopt-option-count/>; if <getopt-option-count/> is
+        *non-numeric*, *less than 1*, or *greater than 100*, use the
+        default *1* instead.
+
+    3.  <if condition="<hint/> is empty AND <type/> is NOT `uuid`">
+        Only output the following <template/> and then immediately *STOP*
+        processing the entire current skill -- every type except `uuid`
+        needs a hint to derive anything from:
+
+        <template>
+        ⧉ **ASE**: ✪ skill: **ase-meta-mint**, ▶ ERROR: expected a `<hint>` argument for type **<type/>**
+        </template>
+        </if>
+
+    4.  Set <results></results> and <warning></warning> (set both to empty).
+
+    </step>
+
+2.  <step id="STEP 2: Mint Hash-Derived Identifiers" condition="<type/> is `uuid` or `sha1`">
+
+    1.  Call the `ase_mint(type: "<type/>", hint: "<hint/>", count:
+        <count/>)` tool of the `ase` MCP server and set <results/> to
+        the returned lines of its `text` output, one identifier per
+        line. You *MUST* *NOT* derive a UUID or a SHA-1 digest yourself
+        -- only the tool hashes correctly and reproducibly.
+
+    2.  <if condition="a line of the `text` output starts with `WARNING:`">
+        Remove that line from <results/> and set <warning/> to its text
+        with the leading `WARNING:` stripped -- hashing a non-empty
+        hint is deterministic, so <count/> was clamped to *1*.
+        </if>
+
+    </step>
+
+3.  <step id="STEP 3: Derive Linguistic Identifiers" condition="<type/> is `const`, `var`, `class`, `func`, `path`, or `name`">
+
+    1.  Distill <hint/> into its *essential words*: drop filler words,
+        articles, and prepositions, keep the two to four words which
+        carry the actual meaning, and order them from the most general
+        to the most specific one. Prefer established terminology of the
+        surrounding domain over invented wording. Do not output
+        anything.
+
+    2.  Assemble <count/> *distinct* candidates from these words,
+        ordered best-first, honoring the rules of <type/>:
+
+        -   `const`: an `UPPER_SNAKE_CASE` constant identifier such as
+            `FOO_BAR_QUUX` -- upper-case ASCII words joined by `_`,
+            never starting with a digit.
+
+        -   `var`: a `lowerCamelCase` variable identifier such as
+            `fooBarQuux` -- the *last* part *MUST* be a *substantive*
+            (`Quux`) naming *what the value is*, never a verb, as a
+            variable holds a thing and not an action.
+
+        -   `func`: a `lowerCamelCase` function identifier such as
+            `fooBarQuux` -- the *first* part *MUST* be a *verb* (`foo`)
+            naming *what the function does*, as a function performs an
+            action and does not hold a thing.
+
+        -   `class`: an `UpperCamelCase` class identifier such as
+            `FooBarQuux` -- a substantive phrase naming the modeled
+            entity, in singular form and without a `The` prefix.
+
+        -   `path`: a `kebab-case` path component such as
+            `foo-bar-quux` -- lower-case ASCII letters, digits, and `-`
+            only, never starting or ending with `-`.
+
+        -   `name`: an `UpperCamelCase` *product name* such as
+            `FooBarQuux` -- optimize for a *brand*, not for a
+            description: short (preferably two to three syllables),
+            pronounceable, memorable, and distinctive. Coinages,
+            blends, and evocative metaphors are explicitly welcome
+            here, and a plain concatenation of the hint words is
+            explicitly not.
+
+        Store the candidates in <results/>. Do not output anything.
+
+    </step>
+
+4.  <step id="STEP 4: Render Result">
+
+    1.  <if condition="<hint/> is empty">
+        Set <hint-shown>*(none -- random UUID)*</hint-shown>.
+        </if>
+        <else>
+        Set <hint-shown><hint/></hint-shown>.
+        </else>
+
+    2.  Output the minted identifiers of <results/>, one per line and
+        each enclosed in backticks, with the following <template/>:
+
+        <template>
+        <ase-tpl-boxed title="MINT" subtitle="<type/>">
+        ●   **HINT**: <hint-shown/>
+
+        ○   `<result-1/>`
+        ○   `<result-2/>`
+        ○   [...]
+        </ase-tpl-boxed>
+        </template>
+
+    3.  <if condition="<warning/> is non-empty">
+        Additionally output the following <template/> directly below the
+        box:
+
+        <template>
+        ⧉ **ASE**: ✪ skill: **ase-meta-mint**, ▶ WARNING: <warning/>
+        </template>
+        </if>
+
+    </step>
+
+</flow>

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

@@ -0,0 +1,114 @@
+
+##  NAME
+
+`ase-meta-mint` - Mint an Identifier or Name
+
+##  SYNOPSIS
+
+`ase-meta-mint`
+    [`--help`|`-h`]
+    [`--type`|`-t` `uuid`|`sha1`|`const`|`var`|`class`|`func`|`path`|`name`]
+    [`--count`|`-c` *count*]
+    [*hint*]
+
+##  DESCRIPTION
+
+The `ase-meta-mint` skill *mints* an identifier or a name of a requested
+type out of the free-text *hint* formed by the positional arguments. It
+dispatches on `--type` and emits the generated strings as its result.
+
+The two *hash-derived* types are delegated to the `ase_mint` tool of the
+`ase` MCP server, which derives them reproducibly instead of guessing
+them:
+
+-   `uuid`:
+    a deterministic *UUID V5* over the *hint*, within the fixed *ASE*
+    namespace (itself a *UUID V5* over `https://ase.tools` in the
+    standard URL namespace), or a random *UUID V4* if no *hint* is
+    given.
+
+-   `sha1`:
+    the 40-character hexadecimal *SHA-1* digest of the *hint*.
+
+The six *linguistic* types are derived by the skill itself: the *hint*
+is distilled into its essential words, which are then assembled
+according to the conventions of the type:
+
+-   `const`:
+    an `UPPER_SNAKE_CASE` constant identifier, such as `FOO_BAR_QUUX`.
+
+-   `var`:
+    a `lowerCamelCase` variable identifier, such as `fooBarQuux`, whose
+    *last* part is a substantive naming what the value *is*, never a
+    verb.
+
+-   `func`:
+    a `lowerCamelCase` function identifier, such as `fooBarQuux`, whose
+    *first* part is a verb naming what the function *does*.
+
+-   `class`:
+    an `UpperCamelCase` class identifier, such as `FooBarQuux`, as a
+    singular substantive phrase naming the modeled entity.
+
+-   `path`:
+    a `kebab-case` path component, such as `foo-bar-quux`.
+
+-   `name`:
+    an `UpperCamelCase` *product name*, such as `FooBarQuux`, optimized
+    for a brand rather than for a description: short, pronounceable,
+    memorable, and distinctive.
+
+A *hint* is mandatory for every type except `uuid`, which falls back to
+a random *UUID V4* without one.
+
+##  OPTIONS
+
+`--type`|`-t` `uuid`|`sha1`|`const`|`var`|`class`|`func`|`path`|`name`:
+    Select the type of the minted identifier or name (default: `uuid`).
+
+`--count`|`-c` *count*:
+    Mint *count* identifiers instead of just one (default: `1`, maximum:
+    `100`). For the hash-derived types it is honored only for an empty
+    *hint*, where *count* random *UUID V4* values are emitted; with a
+    non-empty *hint*, hashing is a pure function of that *hint* and
+    hence always yields exactly one identifier, so *count* is clamped to
+    `1` and a warning is emitted. For the linguistic types, *count*
+    distinct candidates are emitted, ordered best-first.
+
+##  ARGUMENTS
+
+*hint*:
+    The free-text hint the identifier or name is derived from. It may be
+    a short description, a phrase, or a few keywords. It is mandatory
+    for all types except `uuid`.
+
+##  SCENARIOS
+
+-   You need a stable, reproducible UUID or SHA-1 digest for a concept
+-   You need a well-formed constant, variable, function, or class identifier
+-   You need a path component or slug derived from a description
+-   You need a catchy product name for a new component or tool
+
+##  EXAMPLES
+
+Mint a deterministic UUID for a concept:
+
+```text
+❯ /ase-meta-mint --type uuid the ASE artifact kind resolution cache
+```
+
+Mint a function identifier from a description:
+
+```text
+❯ /ase-meta-mint -t func compute the checksum of an artifact file
+```
+
+Mint three product name candidates:
+
+```text
+❯ /ase-meta-mint -t name -c 3 a background service bridging a project into the agent tool
+```
+
+##  SEE ALSO
+
+[`ase-task-id`](../ase-task-id/help.md), [`ase-meta-brainstorm`](../ase-meta-brainstorm/help.md), [`ase-code-craft`](../ase-code-craft/help.md), [`ase-arch-discover`](../ase-arch-discover/help.md).

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

@@ -39,14 +39,14 @@ the `ase-meta-proximity` sub-agent before its proximity is re-determined.
 
 ##  OPTIONS
 
-`--ground`|`-g`:
+-   `--ground`|`-g`:
     Ground the determination in Internet/Web facts gathered by the
     `ase-meta-proximity` agent before determining the proximity. Without
     this option, the determination is derived from model knowledge only.
     When combined with `--loop`, every newly navigated-to topic is
     re-grounded.
 
-`--loop`|`-l`:
+-   `--loop`|`-l`:
     Present the neighboring topics in an interactive dialog and, upon
     selection, adopt the picked topic as the new current topic and
     restart the determination. Without this option, the proximity of the
@@ -54,7 +54,7 @@ the `ase-meta-proximity` sub-agent before its proximity is re-determined.
 
 ##  ARGUMENTS
 
-*topic*:
+-   *topic*:
     The topic whose conceptual proximity is to be determined. It may be
     a technical concept, a phenomenon, or any other subject; the skill
     determines its parent, sibling, and child topics.

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

@@ -26,7 +26,7 @@ complete, unmodified individual responses.
 
 ##  OPTIONS
 
-`--models`|`-m` *model*[,...]:
+-   `--models`|`-m` *model*[,...]:
     Restrict the *foreign* LLMs that are queried to the given
     comma-separated list of *model* tokens. Recognized tokens are
     `all`, `chatgpt`, `gemini`, `deepseek`, `grok`, `glm`, and `qwen`,
@@ -37,7 +37,7 @@ complete, unmodified individual responses.
 
 ##  ARGUMENTS
 
-*question*:
+-   *question*:
     The question to ask all available AIs.
 
 ##  SCENARIOS

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

@@ -50,7 +50,7 @@ the attribution of the quote.
 
 ##  OPTIONS
 
-`--ground`|`-g`:
+-   `--ground`|`-g`:
     Gather quotes from the Internet/Web via the `ase-meta-search` skill
     (dispatched in a sub-agent, querying all available search backends)
     *in addition to* -- and never *instead* of -- the model knowledge,
@@ -63,7 +63,7 @@ the attribution of the quote.
     and the skill falls back to the model knowledge only. Without this
     option, the quotes are derived from model knowledge only.
 
-`--proximity`|`-p`:
+-   `--proximity`|`-p`:
     Widen the harvest beyond the given topic to its *conceptual
     neighborhood* -- the parent (more general) topic, the four sibling
     (same-level) topics, and the four child (more specialized) topics --
@@ -76,7 +76,7 @@ the attribution of the quote.
     warning is emitted and the skill continues with the narrow topic
     only. Without this option, only the given topic is harvested.
 
-`--count`|`-c` *count*:
+-   `--count`|`-c` *count*:
     Maximum total number of quotes across all four quadrants (default:
     `8`, i.e. about two quotes per quadrant). The quotes are distributed
     as evenly as possible across the quadrants, preferring the most
@@ -85,7 +85,7 @@ the attribution of the quote.
 
 ##  ARGUMENTS
 
-*topic-keywords*:
+-   *topic-keywords*:
     The topic keywords the quotes are searched for. They act both as the
     search query and as the keyword set of the *literalness* dimension of
     the matrix.

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

@@ -55,7 +55,7 @@ before it is committed.
 
 ##  OPTIONS
 
-`--severity`|`-S`=(`LOW`|`MEDIUM`|`HIGH`):
+-   `--severity`|`-S`=(`LOW`|`MEDIUM`|`HIGH`):
     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

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

@@ -24,14 +24,14 @@ Brave, or `WebSearch` individually.
 
 ##  OPTIONS
 
-`--services`|`-s`=(`all`|`perplexity`|`brave`|`exa`|`websearch`)...:
+-   `--services`|`-s`=(`all`|`perplexity`|`brave`|`exa`|`websearch`)...:
     The comma-separated list of search backends to query. The default
     `all` queries every available backend;
     otherwise only the listed backends are queried.
 
 ##  ARGUMENTS
 
-*query*:
+-   *query*:
     The search query to dispatch to the search services.
 
 ##  SCENARIOS

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

@@ -50,20 +50,20 @@ cheerleading.
 
 ##  OPTIONS
 
-`--count`|`-c` *count*:
+-   `--count`|`-c` *count*:
     Surface at least *count* strong pro-theses (default *10*) per defense
     pass before sorting and reporting the top *count* and deriving the
     *FORTIFICATION*. An invalid or non-positive *count* reverts to the
     default *10*.
 
-`--rounds`|`-r` *rounds*:
+-   `--rounds`|`-r` *rounds*:
     Run *rounds* iterative defense rounds (default *1*), feeding each
     round's *FORTIFICATION* in as the next round's *thesis*. An invalid
     or non-positive *rounds* reverts to the default *1*.
 
 ##  ARGUMENTS
 
-*thesis*:
+-   *thesis*:
     The statement, claim, or position to be charitably strengthened.
     It may be technical, factual, or opinion-based; the skill defends
     its strongest ("steelman") interpretation.

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

@@ -31,13 +31,13 @@ source code changes.
 
 ##  OPTIONS
 
-`--depth`|`-d` *N*:
+-   `--depth`|`-d` *N*:
     The *maximum* number of "why" iterations (the Five-Whys chain
     length), acting as an *upper bound* only - the analysis still stops
     early once the root cause is reached. Defaults to *5*. A non-numeric
     or non-positive value falls back to the default.
 
-`--width`|`-w` *M*:
+-   `--width`|`-w` *M*:
     The *maximum* number of *candidate sub-causes* to surface per "why"
     level. With the default *1*, the skill walks a single causality chain
     (classic Five-Whys); with *M* > 1, each level surfaces up to *M*
@@ -51,7 +51,7 @@ source code changes.
 
 ##  ARGUMENTS
 
-*fact*:
+-   *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.

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

@@ -338,8 +338,9 @@ Procedure
         following the `Generated Skill Contract` above.
 
     3.  Write <skill-content/> to <target-skill/>, creating the directory
-        `<dir/>/<new-skill-name/>` if it does not exist yet. Calculate the
-        number of words <words/> of <skill-content/>.
+        `<dir/>/<new-skill-name/>` if it does not exist yet. Then call the
+        `ase_text_metric(file: "<target-skill/>")` tool of the `ase` MCP
+        server and set <words/> to the `words` field of its result.
 
     4.  Report the result with the following <template/>:
 

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

@@ -66,7 +66,7 @@ agent tool:
 
 ##  OPTIONS
 
-`--scope`|`-s` `local`|`user`:
+-   `--scope`|`-s` `local`|`user`:
     Where the generated skill is stored. With `local` (the default),
     it is written into the current project, where it can be committed
     and reviewed alongside the code. With `user`, it is written into the
@@ -77,20 +77,20 @@ agent tool:
     Copilot*, and `.agents/skills/` and `~/.codex/skills/` under *OpenAI
     Codex*.
 
-`--force`|`-f`:
+-   `--force`|`-f`:
     Overwrite an already existing skill. Without this option, the skill
     refuses with an error as soon as the target `SKILL.md` exists, so
     hand-edited skills are never lost silently.
 
 ##  ARGUMENTS
 
-*skill-name*:
+-   *skill-name*:
     Name of the skill to generate, matching `^[a-zA-Z][a-zA-Z0-9_-]*$`.
     It is used as the directory name, as the frontmatter `name`, and as
     the resulting `/`*skill-name* command (respectively the
     `$`*skill-name* mention under *OpenAI Codex*).
 
-*workflow-description*:
+-   *workflow-description*:
     Free-text description of the workflow the generated skill should
     perform. Mentioning that actions run "in parallel", that they are
     dispatched "in a sub-agent", or naming concrete `ase-xxx-xxx` skills

package/plugin/skills/ase-meta-workflow/workflow.txt

@@ -15,13 +15,16 @@ START               -> ase-arch-discover
 START               -> ase-code-insight
 START               -> ase-code-explain
 START               -> ase-code-lint
-START               -> ase-docs-distill
+START               -> ase-docs-shorten
+START               -> ase-docs-refine
 START               -> ase-docs-proofread
+START               -> ase-docs-distill
 START               -> ase-meta-review
 START               -> ase-meta-diff
 START               -> ase-meta-changelog
 START               -> ase-meta-commit
 START               -> ase-meta-proximity
+START               -> ase-meta-mint
 START               -> ase-meta-workflow
 START               -> ase-code-dissect
 ase-help-skill      -> END
@@ -41,13 +44,16 @@ ase-arch-discover   -> END
 ase-code-insight    -> END
 ase-code-explain    -> END
 ase-code-lint       -> END
-ase-docs-distill    -> END
+ase-docs-shorten    -> END
+ase-docs-refine     -> END
 ase-docs-proofread  -> END
+ase-docs-distill    -> END
 ase-meta-review     -> END
 ase-meta-diff       -> END
 ase-meta-changelog  -> END
 ase-meta-commit     -> END
 ase-meta-proximity  -> END
+ase-meta-mint       -> END
 ase-meta-workflow   -> END
 ase-code-dissect    -> END
 START               -> SKETCH

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

@@ -454,7 +454,7 @@ empty <todo-what/> or <todo-how/> renders as `(none)`:
     *NOT* run any build, tests, linter, or type-checker.
 
     1.  Validate the specification and capture its <diagnostics/> array
-        of `{ file, line, column, message }` objects:
+        of `{ file, line, column, severity, message }` objects:
 
         <if condition="<worktree-dir/> is not empty">
         Run the command `ase spec lint` with <worktree-dir/> as its