ase-arch-analyze
Review software architecture, including package cohesion and inter-package coupling
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>.
$ npx -y skills add rse/ase --skill hello --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/helloContext preview
The summary Claude sees to decide when to auto-load this skill.
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>.
name: hello
argument-hint: "[--help|-h] [--lang|-l=(en|de|fr|it)] [<subject>]"
description: >
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>.
user-invocable: true
disable-model-invocation: false
allowed-tools:
- "Bash(date *)"
- "Bash(ase meta *)"!`ase meta control skill getopt`
<purpose name="hello"> Show a Nice Greeting Message </purpose>
<expand name="getopt" arg1="hello" arg2="--lang|-l=(en|de|fr|it)"> $ARGUMENTS </expand>
<flow>
1. <step id="STEP 1: Determine Parameters">
1. Set <subject><getopt-arguments/></subject> Set <language><getopt-option-lang/></language>
2. <if condition="<subject/> is empty"> Set <subject>World</subject> </if>
3. The current time <time/> is set by capturing the output of the `Bash` tool command `date '+%Y-%m-%d %H:%M:%S'`
4. The greeting format in Markdown is exactly: `[<time/>]: ☯ *Hello*, **<subject/>**, nice to meet you!`
</step>
2. <step id="STEP 2: Produce Output">
1. Create the greeting string, based on the greeting format and store the result in <greeting/>.
2. Translate the <greeting/> into the target language <language/>.
3. Output the greeting with the following <template/>. Do not output anything else.
<template> <ase-tpl-boxed title="Hello"> <greeting/> </ase-tpl-boxed> </template>
</step>
</flow>
Repo: rse/ase
Review software architecture, including package cohesion and inter-package coupling
Discover additional, third-party components (libraries/frameworks) for the technology stack to provide needed functionality.
Analyze the source code for problems in either the logic and semantics and its related control flow, performance and efficiency, or security.
Craft Source Code: Use when user wants to "create", "add", or "craft" a new feature from scratch.
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…
Edit Source Code: Use when the user wants to "edit" the code base in one shot from a query or a bare analyzer issue id like "P1", fusing crafting, refactoring,…