/ase-task-list
List all available task ids. Use when user wants to see all tasks.
$ npx -y skills add rse/ase --skill ase-task-list --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/ase-task-list
Context preview
The summary Claude sees to decide when to auto-load this skill.
List all available task ids. Use when user wants to see all tasks.
SKILL.md
ase-task-list.SKILL.mdname: ase-task-list
argument-hint: "[--help|-h] [--verbose|-v]"
description: >
List all available task ids.
Use when user wants to see all tasks.
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-task-list"> List Task Plans </purpose>
<expand name="getopt" arg1="ase-task-list" arg2="--verbose|-v"> $ARGUMENTS </expand>
<objective> *List* all available *task plans* of the current project. </objective>
Procedure ---------
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`).
2. If the `tasks` array is empty, output the following <template/>:
<template> ⧉ **ASE**: ◉ tasks: *(none)* </template>
Else, dispatch on <getopt-option-verbose/>:
- If <getopt-option-verbose/> is `true`, output the list of tasks
with the following <template/>, where each <id/> and <mtime/> correspond to an entry in the task list:
<template> ⧉ **ASE**: ◉ tasks:
| *Task Id* | *Last Modified* | |-----------|--------------------| | **<id/>** | `<mtime/>` | | [...] | [...] |
</template>
- If <getopt-option-verbose/> is `false`, output the list of tasks
with the following <template/>, where each <id/> corresponds to an entry in the task list:
<template> ⧉ **ASE**: ◉ tasks:
| *Task Id* | |-----------| | **<id/>** | | [...] |
</template>
3. Finally, give the closing hints by expanding the following (which, depending on the configured <ase-guidance-level/>, may each expand into nothing and hence emit no output at all):
<if condition="the `tasks` array is NOT empty"> <ase-tpl-hint level="normal"> Use `/ase-task-id <id>` to switch to one of the listed tasks and `/ase-task-view` to inspect its plan. </ase-tpl-hint> </if> <else> <ase-tpl-hint level="normal"> No task plan exists yet -- use `/ase-task-edit` to create one through a conversational loop. </ase-tpl-hint> </else>
<if condition="<getopt-option-verbose/> is not equal `true`"> <ase-tpl-hint level="verbose"> Use `/ase-task-list --verbose` to additionally show the last-modified timestamp of each task plan. </ase-tpl-hint> </if>
Read more
name: ase-task-list
argument-hint: "[--help|-h] [--verbose|-v]"
description: >
List all available task ids.
Use when user wants to see all tasks.
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-task-list"> List Task Plans </purpose>
<expand name="getopt" arg1="ase-task-list" arg2="--verbose|-v"> $ARGUMENTS </expand>
<objective> *List* all available *task plans* of the current project. </objective>
Procedure ---------
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`).
2. If the `tasks` array is empty, output the following <template/>:
<template> ⧉ **ASE**: ◉ tasks: *(none)* </template>
Else, dispatch on <getopt-option-verbose/>:
- If <getopt-option-verbose/> is `true`, output the list of tasks
with the following <template/>, where each <id/> and <mtime/> correspond to an entry in the task list:
<template> ⧉ **ASE**: ◉ tasks:
| *Task Id* | *Last Modified* | |-----------|--------------------| | **<id/>** | `<mtime/>` | | [...] | [...] |
</template>
- If <getopt-option-verbose/> is `false`, output the list of tasks
with the following <template/>, where each <id/> corresponds to an entry in the task list:
<template> ⧉ **ASE**: ◉ tasks:
| *Task Id* | |-----------| | **<id/>** | | [...] |
</template>
3. Finally, give the closing hints by expanding the following (which, depending on the configured <ase-guidance-level/>, may each expand into nothing and hence emit no output at all):
<if condition="the `tasks` array is NOT empty"> <ase-tpl-hint level="normal"> Use `/ase-task-id <id>` to switch to one of the listed tasks and `/ase-task-view` to inspect its plan. </ase-tpl-hint> </if> <else> <ase-tpl-hint level="normal"> No task plan exists yet -- use `/ase-task-edit` to create one through a conversational loop. </ase-tpl-hint> </else>
<if condition="<getopt-option-verbose/> is not equal `true`"> <ase-tpl-hint level="verbose"> Use `/ase-task-list --verbose` to additionally show the last-modified timestamp of each task plan. </ase-tpl-hint> </if>
Repo: rse/ase
Other skills on ase.
- /hello
Show a nice greeting message with a timestamp. Use this, when the user wants to greet or say hello, optionally to a certain subject <subject> and in a certain language <language>.
Open skill - /ase-arch-analyze
Review software architecture, including package cohesion and inter-package coupling
Open skill - /ase-arch-discover
Discover additional, third-party components (libraries/frameworks) for the technology stack to provide needed functionality.
Open skill - /ase-code-analyze
Analyze the source code for problems in either the logic and semantics and its related control flow, performance and efficiency, or security.
Open skill - /ase-code-craft
Craft Source Code: Use when user wants to "create", "add", or "craft" a new feature from scratch.
Open skill - /ase-code-dissect
Dissect the current Git change set, treated as an epic, domain-wise and logically into cohesive parts and materialize each part in its own dedicated Git WorkTree. Use when the user calls to "dissect", "split", "break up", or "decompose" a large change set into atomic, separately
Open skill

