hello
Write a hello file to the workspace output directory.
56
45%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./openclaw/skills/hello/SKILL.mdQuality
Discovery
17%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is extremely minimal and appears to describe a trivial or demo skill. It lacks a 'Use when...' clause, natural trigger terms, and sufficient detail about what the skill actually accomplishes. The description would be nearly impossible for Claude to correctly select from a pool of skills because it provides no context about when or why it should be used.
Suggestions
Add a 'Use when...' clause that explicitly states the conditions under which this skill should be triggered, e.g., 'Use when the user asks to create a test file, hello world file, or verify workspace output.'
Include natural trigger terms that users might actually say, such as 'test file', 'hello world', 'sample output', or 'verify workspace setup'.
Clarify what 'hello file' means—specify the file format, content, and purpose so Claude can distinguish this skill from other file-writing skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names a specific action ('write a hello file') and a specific location ('workspace output directory'), but describes only a single narrow action without listing multiple concrete capabilities. | 2 / 3 |
Completeness | It describes a 'what' (write a hello file) but has no 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill, which caps completeness at a maximum of 2, and the 'what' itself is also quite weak. | 1 / 3 |
Trigger Term Quality | The description lacks natural keywords a user would say. 'Hello file' and 'workspace output directory' are not terms users would naturally use in requests; there are no common variations or recognizable trigger terms. | 1 / 3 |
Distinctiveness Conflict Risk | The description is narrow enough ('hello file' to 'workspace output directory') that it's unlikely to conflict with many other skills, but the vague nature of 'hello file' could cause confusion about whether this is a test/demo skill or something more specific. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a minimal skill for a simple task. Its brevity is appropriate and the structure is clean, but it lacks key details: what the hello script contains or does, whether it needs to exist beforehand, and any verification that the output was created correctly. The skill tells Claude to run a command but doesn't ensure Claude can actually execute it end-to-end.
Suggestions
Show the contents of `scripts/hello.sh` or provide the script inline so Claude can create it if it doesn't exist, making the skill fully self-contained and executable.
Add a brief verification step after the command, e.g., `cat out/hello.txt` to confirm the expected output content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations or padding. Every line serves a purpose for this simple task. | 3 / 3 |
Actionability | Provides a concrete command to run, but lacks detail on what the script does, what the expected output content is, and whether the script already exists or needs to be created. Not fully copy-paste ready since the script itself isn't shown. | 2 / 3 |
Workflow Clarity | For this simple single-step task, the command is clear, but there's no validation step (e.g., verify the file was created, check its contents). For a file-writing operation, a brief verification step would improve clarity. | 2 / 3 |
Progressive Disclosure | For a simple skill under 50 lines with a single task, the content is well-organized with clear sections (Overview, Command, Output Files). No need for external references. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- trpc-group/trpc-agent-go
- Commit
af8bd5f
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.