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 narrow and lacks clarity about its purpose, trigger conditions, and the broader context in which it should be used. It reads more like a single command than a skill description, with no 'Use when' clause and no natural language trigger terms that would help Claude select it appropriately.
Suggestions
Add a 'Use when...' clause explaining the specific scenarios that should trigger this skill, e.g., 'Use when the user asks to create a hello world file, test file output, or verify workspace write access.'
Include natural trigger terms users might say, such as 'hello world', 'test file', 'sample output', or 'write test'.
Clarify what a 'hello file' actually is (e.g., a hello world text file, a greeting template) 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 so narrow and unclear that it scores a 1. | 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 fairly niche ('hello file' to a specific directory), which reduces conflict risk, but the vagueness of what a 'hello file' actually is could cause confusion with other file-writing or scaffolding skills. | 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 `scripts/hello.sh` contains or whether it already exists, what the expected file content is, and any verification that the operation succeeded. 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 clarify whether it already exists in the workspace, so Claude can create it if needed.
Add a brief verification step after the command, e.g., `cat out/hello.txt` to confirm expected output.
Specify the expected content of `out/hello.txt` so Claude can validate success.
| 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 needs to exist already or 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 or 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 no need for external references, the content is well-organized with clear sections (Overview, Command, Output Files). | 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
0c1ec2b
- 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.