hello
Write a hello file to the workspace output directory.
67
Quality
58%
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 too minimal and lacks the guidance Claude needs to select it appropriately. It describes a very narrow action without explaining when to use it or providing natural trigger terms users would actually say. The description reads more like an internal command than a skill description.
Suggestions
Add a 'Use when...' clause explaining the scenarios that should trigger this skill (e.g., 'Use when testing file output, verifying workspace setup, or when user asks to create a test file')
Include natural trigger terms users might say, such as 'test file', 'sample output', 'verify workspace', or 'create example file'
Expand the capability description to explain the purpose - is this for testing, initialization, or demonstration? Context helps Claude choose appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names a specific action ('Write a hello file') and location ('workspace output directory'), but describes only a single narrow action rather than multiple concrete capabilities. | 2 / 3 |
Completeness | Describes what it does minimally but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains no natural keywords users would say - 'hello file' and 'workspace output directory' are technical/internal terms, not phrases users would naturally use when requesting help. | 1 / 3 |
Distinctiveness Conflict Risk | The specific mention of 'hello file' and 'workspace output directory' provides some distinctiveness, but 'write a file' could overlap with many file-writing skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary simple skill that accomplishes its purpose with maximum efficiency. It provides exactly what's needed: a brief overview, the executable command, and expected output. No unnecessary explanation or verbosity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean content with no unnecessary explanation. Every line serves a purpose and assumes Claude's competence. | 3 / 3 |
Actionability | Provides a concrete, copy-paste ready command with clear input/output. No ambiguity about what to execute. | 3 / 3 |
Workflow Clarity | This is a simple single-step task (run one command). The action is unambiguous and no multi-step validation is needed for a non-destructive hello file operation. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with a single simple task, the content is appropriately organized with clear sections (Overview, Command, Output Files). No external references needed. | 3 / 3 |
Total | 12 / 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
8763418
- 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.