/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>.
$ npx -y skills add rse/ase --skill hello --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
/hello
Context 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>.
SKILL.md
hello.SKILL.mdname: 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`
<skill name="hello"> Hello World </skill>
<expand name="getopt" arg1="foo"> $ARGUMENTS </expand>
<flow>
1. <step id="STEP 1: Determine Parameters">
1. Set <subject><getopt-arguments/></subject> Set <language><getopt-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: Product Output">
1. Create the greeting string, based on the greeting format.
2. Translate the greeting string into the target language <language/>.
3. Output the greeting string verbatim. Do not output anything else.
</step>
</flow>
Repo: rse/ase
Other skills on ase.
- /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 - /ase-code-explain
Explains code with WHAT, WHY, ANALOGY, DIAGRAM, CRUXES, and GOTCHAS. Use when you want to know how code works or when the user asks "how does this work?"
Open skill

