envdump

Dump basic environment info to out/env.txt.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

100%

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

The content is a model of brevity and actionability for a simple skill: a clear overview, an executable command backed by a real script, and a stated output. Structure is clean and well-organized with no unnecessary detail.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient — Overview, Command, and Output Files with no padding and no explanation of concepts Claude already knows; every token earns its place.	3 / 3
Actionability	It provides a fully executable, copy-paste-ready command 'bash scripts/envdump.sh out/env.txt', and the referenced script exists, is complete, and produces the stated output.	3 / 3
Workflow Clarity	This is a simple single-task skill where the action is unambiguous: run the command, output is written to out/env.txt. Per the simple-skills note, a clear single action scores 3.	3 / 3
Progressive Disclosure	Under 50 lines with well-organized sections (Overview, Command, Output Files) and a single one-level-deep reference to the real bundle script scripts/envdump.sh, satisfying the simple-skills guidance.	3 / 3
	Total	12 / 12 Passed

Description

50%

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 concise and states a concrete action with a clear output target, but it omits any explicit 'Use when...' trigger guidance and lacks natural keyword variations. It is adequate but not exemplary.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to collect environment or system info for debugging, diagnostics, or context sharing.'

Include natural keyword variations users would say, such as 'environment variables', 'env dump', or 'system info'.

Consider naming a second concrete action (e.g. 'collects shell environment, working directory, and system info') to broaden specificity.

Dimension	Reasoning	Score
Specificity	The phrase 'Dump basic environment info to out/env.txt' names the domain and one concrete action with a specific output target, but lists only a single action rather than multiple specific concrete actions.	2 / 3
Completeness	It states what the skill does ('Dump basic environment info to out/env.txt') but provides no 'Use when...' clause or equivalent explicit trigger guidance, so 'when' is only implied and completeness is capped at 2.	2 / 3
Trigger Term Quality	'environment info' is a somewhat relevant keyword a user might say, but common natural variations like 'environment variables', 'env', 'system info', or 'debugging context' are missing.	2 / 3
Distinctiveness Conflict Risk	'Dump basic environment info' is a fairly specific niche unlikely to conflict broadly, but it lacks distinct trigger terms that would make it clearly distinguishable from other system-inspection skills.	2 / 3
	Total	8 / 12 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
Commit: 737835b

Reviewed: 3 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.