envdump

Dump basic environment info to out/env.txt.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./openclaw/skills/envdump/SKILL.md

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 content body is exemplary for a simple skill: lean, immediately actionable, and correctly sized with no unnecessary explanation or external references. The single command is copy-paste ready and the referenced script exists and matches its documented usage. Nothing material needs improvement.

Dimension	Reasoning	Score
Conciseness	The body is ~18 lines with zero padding: an overview sentence, one command, and one output file entry. It assumes Claude's competence and every token earns its place, matching the lean/efficient anchor. Not 4 because there is nothing to trim — no over-explanation exists.	5 / 5
Actionability	"bash scripts/envdump.sh out/env.txt" is fully executable, copy-paste ready, and the referenced script exists and accepts exactly that argument. The single common case is completely covered; not 4 because there are no gaps in the guidance for this skill's purpose.	5 / 5
Workflow Clarity	This is a simple single-task skill and the single action is unambiguous, so per the rubric's simple-skill exception workflow clarity can score 5. The operation writes a new output file and is neither destructive nor batch, so the validation-cap at 3 does not apply; not 4 because a one-step skill with an explicit command leaves no sequence ambiguity.	5 / 5
Progressive Disclosure	Under 50 lines with no need for external references, the body is organized into three clear sections (Overview, Command, Output Files), and the one referenced path (scripts/envdump.sh) is a real, working bundle file. Meets the simple-skill anchor for well-organized sections; not 4 because there is no content that should be split out or any navigation ambiguity.	5 / 5
	Total	20 / 20 Passed

Description

50%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 answers "what" clearly and concisely but omits any "when to use" guidance, which drags completeness, trigger quality, and distinctiveness to the midpoint. It is neither vague fluff nor over-claiming, just under-specified. Adding a "Use when..." clause with natural trigger phrases would lift all four dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to dump, inspect, or collect environment/system info or environment variables."

Enumerate the concrete data collected (date, working directory, uname, environment variables) so the "what" is comprehensive rather than "basic environment info".

Include natural synonyms users would say — "system info", "environment variables", "env" — to improve trigger term coverage and distinctiveness from other inspection skills.

Dimension	Reasoning	Score
Specificity	"Dump basic environment info to out/env.txt" names the domain and one concrete action with a specific output destination, matching the anchor for 1-2 concrete actions that is not comprehensive. Not 4 because it never says what environment info is collected; not 2 because a real action and target file are explicitly stated.	3 / 5
Completeness	The description has a clear "what" (dump environment info to out/env.txt) but no "when" clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. Not 4 because the "when" is entirely absent, not just under-specified.	3 / 5
Trigger Term Quality	"environment info" and "env.txt" are relevant natural keywords, but common variations users would say ("system info", "environment variables", "env vars") are missing. This fits anchor 3 (some relevant keywords, missing common variations); not 4 because keyword coverage is sparse rather than merely missing a few.	3 / 5
Distinctiveness Conflict Risk	"Dump basic environment info" is somewhat specific with a distinct output artifact (out/env.txt), but the domain phrasing is generic enough to overlap with other system/environment-inspection skills. Fits anchor 3; not 2 because the stated action and destination are more concrete than "Helps with document files".	3 / 5
	Total	12 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: trpc-group/trpc-agent-go
Path: openclaw/skills/envdump/SKILL.md
Commit: 9bb1c42

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.