CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

convex-env

Set and wire Convex deployment env vars / secrets for the app.

Quality

80%

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 ./.agents/skills/convex-env/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A tight, highly actionable single-file skill with copy-paste-ready Convex commands, a sequenced workflow including a verification step, and clean organization. Its main weaknesses are redundancy between the intro, Workflow, and Rules sections, and the absence of error-recovery guidance for cases like wrong-deployment or missing secrets.

Suggestions

Merge the Rules section into the Workflow steps to eliminate repeated statements (never-commit, env list --names-only, process.env-in-actions each appear 2-3 times).

Add a brief error-recovery note, e.g. what to do when a secret is missing in an action or set on the wrong deployment.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no explanation of what Convex or env vars are), with concrete commands throughout; the only trimmable redundancy is that the Rules section restates workflow points ("never commit" appears three times, and `npx convex env list --names-only` is explained twice). It is not 5 because that duplication could be collapsed, and not 3 because there is no conceptual padding beyond it.

4 / 5

Actionability

Commands are copy-paste ready and cover the common cases: `npx convex env set KEY value`, reading via process.env.KEY in actions, `npx convex env list --names-only` for verification, and .env.local for local values. This matches the fully-executable anchor rather than 4, which expects minor gaps in the guidance.

5 / 5

Workflow Clarity

The 4-step workflow is clearly sequenced and includes an explicit verification step ("Confirm it's set with `npx convex env list --names-only`"), matching the clear-sequence/most-checkpoints anchor. It is not 5 because there is no error-recovery guidance (e.g., what to do if a var is missing or set on the wrong deployment), and not 3 because a validation checkpoint is explicitly present.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files, and needs no external references; per the rubric's simple-skill guideline, well-organized sections (Workflow, Rules) warrant a 5. All paths referenced in the body are commands, not files, so there are no dangling references to verify.

5 / 5

Total

18

/

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.

A concise, third-person description with a specific niche and decent trigger keywords, but it lacks any "when to use" guidance and lists only one to two concrete actions. Adding a Use-when clause and a fuller action list would raise completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to set, check, or wire Convex deployment secrets or env vars".

Enumerate more concrete actions (set, list/verify, read in actions) instead of the single vague verb "wire".

Include common synonyms such as "environment variables", "credentials", or "API keys" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

"Set and wire Convex deployment env vars / secrets" names a specific domain with 1-2 concrete actions, but "wire" is vague and there is no coverage of related operations (list, verify, remove), matching the 1-2-actions anchor. It is not 4 because the action list is not "several specific actions," and not 2 because the domain and primary action are concrete.

3 / 5

Completeness

The description clearly answers "what" ("Set and wire Convex deployment env vars / secrets") but has no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3. It is not 2 because the "what" is clear and specific rather than vague.

3 / 5

Trigger Term Quality

"Convex", "env vars", "secrets", and "deployment" are natural terms a user needing this skill would say, giving good keyword coverage. It is not 5 because common variations like "environment variables" spelled out, "credentials", or "API keys" are missing.

4 / 5

Distinctiveness Conflict Risk

"Convex deployment env vars / secrets" carves out a clear niche with distinct triggers; only other Convex skills could plausibly overlap and the env-var/secret framing distinguishes it from them. It clearly matches the minimal-conflict anchor rather than the "minor overlap risk" anchor at 4.

5 / 5

Total

15

/

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

openclaw/clawhub

Path

.agents/skills/convex-env/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.