CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hello

Write a hello file to the workspace output directory.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./openclaw/skills/hello/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

96%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an exemplary minimal skill: lean, fully executable, and unambiguous, with a real bundled script matching the documented command. The only flaw is cosmetic — unlabeled markdown headings — which slightly weakens the section structure.

DimensionReasoningScore

Conciseness

The body is three short labeled sections with zero padding or explanation of concepts Claude already knows ("This skill writes a small hello file under `out/`"). Every token earns its place, matching the lean-and-efficient anchor.

5 / 5

Actionability

It gives the exact, copy-paste-ready command `bash scripts/hello.sh out/hello.txt`, and the referenced script exists in the bundle and is a complete, executable program. This fully matches the executable-and-complete anchor.

5 / 5

Workflow Clarity

This is a simple single-purpose skill whose one action (run the given command) is unambiguous, which the guidelines allow to score 5. The operation is neither destructive nor batch, so no validation step is required.

5 / 5

Progressive Disclosure

The skill is well under 50 lines with no need for external references, and the sections (Overview, Command, Output Files) plus the verified `scripts/hello.sh` bundle path give good structure. However, the section headings are plain text without markdown `#` formatting, a minor organization gap that keeps it below the well-organized-sections anchor for 5.

4 / 5

Total

19

/

20

Passed

Description

46%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description states a single concrete action clearly but has no "Use when..." trigger guidance and almost no natural trigger terms. It is serviceable for such a narrow skill yet leaves Claude with no basis for deciding when to invoke it.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to create a hello/greeting file or test workspace output writing."

Include a few natural trigger terms and variations users might say ("hello file", "greeting file", "test file", "sample output file").

State the concrete output (a file containing a single hello line at out/hello.txt) so the what is fully specified rather than implied.

DimensionReasoningScore

Specificity

The description names one concrete action ("Write a hello file") and a destination ("the workspace output directory"), matching the anchor for 1-2 concrete actions that are not comprehensive. It does not list several specific actions, so it falls short of a 4.

3 / 5

Completeness

It has a clear "what" (write a hello file to the output directory) but no "when" clause whatsoever, which the judging guidelines explicitly cap at 3. It is not a 2 because the "what" is concrete rather than vague.

3 / 5

Trigger Term Quality

The only keywords are "hello file" and "workspace output directory" — essentially one or two keywords with no natural phrases or synonyms a user would say. There are relevant terms but no coverage of variations, so it sits between the sparse keyword anchor (2) and partial-coverage anchor (3), closer to 2.

2 / 5

Distinctiveness Conflict Risk

Writing a hello file is a narrow, mostly distinct niche unlikely to trigger competing skills, though it could overlap with generic file-writing skills. It lacks distinct trigger phrases, so it does not reach the clear-niche-with-distinct-triggers anchor (5).

4 / 5

Total

12

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

trpc-group/trpc-agent-go

Path

openclaw/skills/hello/SKILL.md

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.