The body is a tight, fully executable reference for a simple task: concrete CLI commands, a correctly sequenced workflow ending in an explicit verification step, and clean section organization with no padding. The only trimmable redundancy is the triple restatement of the same three rules across the intro, Workflow, and Rules sections.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — no concept explanations, just "Store secrets as Convex deployment env vars (npx convex env set), read them with process.env in actions, never commit them". It is not 5 because the same three facts are stated three times (intro sentence, Workflow, and Rules sections: e.g., "process.env only in actions... not queries/mutations" repeats step 2), which could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready commands: `npx convex env set KEY value`, `process.env.KEY` inside actions, and `npx convex env list` for confirmation, covering the common cases including the per-deployment caveat. It matches anchor 5 and is not 4 because there are no gaps — the exact commands and the critical constraint ('actions, not queries/mutations') are both explicit.	5 / 5
Workflow Clarity	A clear 4-step sequence with an explicit validation checkpoint ("4. Confirm with `npx convex env list`"). While there is no error-recovery loop, this is a simple single-purpose skill under 50 lines where the simple-skill exception applies, and the validation step is explicit. Not 4 because the confirm step makes the checkpoint explicit rather than 'minor validation gaps'.	5 / 5
Progressive Disclosure	This is a short (<50 lines) single-purpose skill with no need for external references; per the scoring notes, well-organized sections (Workflow, Rules) warrant a 5. There are no bundle files to verify and no buried or nested references. Not 4 because organization is clean with no content that should be split out.	5 / 5
	Total	19 / 20 Passed

Description

65%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 concise, third-person, and highly distinct thanks to explicit Convex scoping, with good natural trigger terms. Its main weakness is the complete absence of a 'Use when...' clause, which caps completeness at 3 and leaves Claude without explicit trigger guidance.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user mentions Convex environment variables, secrets, deployment configuration, or .env setup for the Convex app.'

Include a few more concrete actions to broaden coverage, such as listing ('npx convex env list') or reading env vars in actions, so specificity moves beyond a single set/wire action.

Add common synonyms/extensions users might say — 'environment variables', '.env', 'API keys' — to strengthen trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Set and wire Convex deployment env vars / secrets" names the domain (Convex deployment env vars/secrets) and 1-2 concrete actions ("set", "wire"), matching the anchor for domain + 1-2 actions but not comprehensive coverage. It is below 4 because it does not list several distinct actions (e.g., list, rotate, read), and above 2 because the actions are concrete rather than generic.	3 / 5
Completeness	The 'what' is clear ("Set and wire Convex deployment env vars / secrets for the app") but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It fits anchor 3 ('clear what, when missing or only weakly implied') exactly, and is not 4 because 'when' is entirely absent rather than just imprecise.	3 / 5
Trigger Term Quality	Natural keywords users would say are present: "Convex", "env vars", "secrets", "deployment" — a user asking to set a Convex secret would phrase it almost exactly this way. Not 5 because common variations like "environment variables", ".env", or "API keys" are missing; not 3 because coverage of the niche's natural terms is good rather than merely 'some relevant keywords'.	4 / 5
Distinctiveness Conflict Risk	"Convex deployment env vars / secrets" carves out a clear niche with distinct triggers; virtually no other skill category would collide with it. It matches anchor 5 (clear niche, minimal conflict risk) and is not 4 because the domain scoping leaves essentially no overlap risk with closely related skills.	5 / 5
	Total	15 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: openclaw/clawhub
Path: .agents/skills/convex-env/SKILL.md
Commit: 0180b56

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.