CtrlK
BlogDocsLog inGet started
Tessl Logo

hello

Write a hello file to the workspace output directory.

44

Quality

45%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./openclaw/skills/hello/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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, well-structured skill for a very simple task. Its conciseness is a strength, but it lacks a verification step after writing the file and doesn't show or bundle the referenced script (scripts/hello.sh), which limits actionability since Claude cannot inspect what the script actually does.

Suggestions

Add a verification step after the command, e.g., 'Verify: `cat out/hello.txt`' with expected output content.

Either include the content of `scripts/hello.sh` inline or bundle it so Claude can understand and troubleshoot the operation.

DimensionReasoningScore

Conciseness

Very lean and efficient. No unnecessary explanations or padding. Every line serves a purpose for this simple skill.

3 / 3

Actionability

Provides a concrete command to run, but lacks detail on what the script does, what the expected output content is, and there's no verification step. The script itself is not shown or bundled, so Claude can't inspect or execute it confidently.

2 / 3

Workflow Clarity

The single command is clear, but there's no validation or verification step (e.g., checking the file was created, confirming its contents). For a file-writing operation, a simple check like 'cat out/hello.txt' would improve confidence.

2 / 3

Progressive Disclosure

For a simple, single-purpose skill under 50 lines, the content is well-organized with clear sections (Overview, Command, Output Files). No need for external references.

3 / 3

Total

10

/

12

Passed

Description

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 terse and lacks critical information for skill selection. It describes a single narrow action without explaining when Claude should choose this skill, and it contains no natural trigger terms a user would use. The description would benefit significantly from a 'Use when...' clause and more context about what a 'hello file' is.

Suggestions

Add a 'Use when...' clause explaining the circumstances under which this skill should be triggered, e.g., 'Use when the user asks to test file writing, create a sample output, or generate a hello world file.'

Include natural trigger terms users might say, such as 'test file', 'sample output', 'hello world', 'write test', or 'verify workspace setup'.

Clarify what a 'hello file' actually is (e.g., a simple text file with greeting content) so Claude can better match user intent to this skill.

DimensionReasoningScore

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 provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also weak, so it scores 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 when requesting this skill; there are no common variations or recognizable trigger terms.

1 / 3

Distinctiveness Conflict Risk

The task is fairly narrow and specific ('hello file to workspace output directory'), which reduces conflict risk, but the description is unusual enough that it's unclear when it should be selected, creating potential for mismatches rather than conflicts.

2 / 3

Total

6

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
trpc-group/trpc-agent-go
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.