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 task-specific without providing context for when it should be used. It lacks trigger terms users would naturally say and provides no 'Use when...' guidance, making it difficult for Claude to correctly select this skill from a pool of options.
Suggestions
Add an explicit 'Use when...' clause describing the scenarios that should trigger this skill, e.g., 'Use when the user asks to create a hello/test file or wants to verify the workspace output directory is writable.'
Include natural trigger terms a user might say, such as 'test file', 'hello world', 'sample output', or 'verify output directory'.
Clarify the purpose of the skill beyond the mechanical action—explain why someone would want a hello file written (e.g., testing, initialization, verification).
| 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 partially answers '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 too minimal to warrant a 2. | 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 narrow ('hello file' to a specific directory), which reduces conflict risk, but it's unclear enough in purpose that it could be confused 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 very concise, well-structured skill for a simple task. However, it lacks actionability details—the script contents are opaque, there's no indication of what 'hello.txt' should contain, and there's no verification step to confirm success. The skill tells Claude to run a script but doesn't give enough context about what the script does or how to verify the result.
Suggestions
Show the expected content of out/hello.txt so Claude can verify the output is correct.
Add a brief verification step, e.g., 'Verify: `cat out/hello.txt` should output "Hello, world!"'
Consider showing what scripts/hello.sh contains or at minimum describe what it does, so Claude isn't blindly executing an unknown script.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely lean—just a few lines with no unnecessary explanation. Every token serves a purpose for this simple task. | 3 / 3 |
Actionability | It provides a concrete command to run, but lacks detail on what the script does, what the expected output content is, and there's no executable code shown—just a shell invocation of an external script whose contents are unknown. | 2 / 3 |
Workflow Clarity | For this simple single-step task, the command is clear, but there's no validation or verification step (e.g., confirming the file was created or checking its contents). For a task that writes files, a brief verification step would be appropriate. | 2 / 3 |
Progressive Disclosure | For a skill this simple (under 50 lines, single task), the organization into Overview, Command, and Output Files sections is clean and appropriate. No external references are needed. | 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
09cce3e
- 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.