CtrlK
BlogDocsLog inGet started
Tessl Logo

hello

Write a hello file to the workspace output directory.

62

Quality

73%

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

100%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 a model of brevity and actionability for a simple skill: a real executable script, clear sections, and no wasted tokens.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence; every section earns its place with no padded explanations of concepts Claude already knows.

5 / 5

Actionability

It gives a fully executable, copy-paste-ready command ("bash scripts/hello.sh out/hello.txt") backed by a real, working script in the bundle.

5 / 5

Workflow Clarity

This is a simple single-purpose skill with an unambiguous single action, so the simple-skill exception applies and workflow clarity is fully clear.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references, the well-organized Overview / Command / Output Files sections satisfy the simple-skill progressive disclosure bar.

5 / 5

Total

20

/

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 is clear and third-person but thin: it states a single concrete action with no trigger guidance, leaving Claude without explicit "when to use" direction.

Suggestions

Add an explicit trigger clause such as "Use when the user asks to create a sample or placeholder hello file in the workspace output directory."

Broaden keyword coverage with natural user phrasing and synonyms (e.g., "hello file", "sample file", "placeholder output", "out/ directory").

Consider listing any variant actions the skill supports to lift specificity above a single task.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ("Write a hello file to the workspace output directory"), but coverage is minimal rather than comprehensive.

3 / 5

Completeness

It clearly states what the skill does but provides no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Only generic keywords ("hello file", "workspace output directory") appear; the natural phrases a user would actually say when needing this skill are missing.

2 / 5

Distinctiveness Conflict Risk

The narrow niche (writing a hello file to the output directory) is mostly distinct with only minor overlap risk against general file-writing skills.

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.

Validation16 / 16 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.