CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

convex-deploy-guard

Classify + announce the target Convex deployment before any deployment-affecting command; fresh explicit consent for prod actions; session read-only mode.

Quality

88%

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

The canonical home for this skill is convex-deploy-guard in openclaw/clawhub

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary instruction-only guard: every step is executable with exact flags, commands, and file paths, and the risky operations are fenced with consent, ambiguity, and disagreement checkpoints. The only real criticism is redundancy between the Workflow steps and the Rules bullets that restate them.

DimensionReasoningScore

Conciseness

The body is dense and directive with no background tutorials, but five of the six Rules bullets restate Workflow steps nearly verbatim (e.g. step 6 vs "A deploy that seemed to do nothing means the WRONG deployment changed") and the opening motivational sentence could be trimmed.

4 / 5

Actionability

Fully actionable for an instruction-only skill: exact env vars and files (CONVEX_DEPLOYMENT in .env.local, convex.json, CONVEX_DEPLOY_KEY), literal commands (npx convex deploy, npx convex run --prod, npx convex env list), exact MCP flags, and a copy-paste announce format ('target: dev (joyful-capybara-123, personal dev)').

5 / 5

Workflow Clarity

Seven explicitly sequenced steps with validation checkpoints ("If two sources disagree, resolve before proceeding", "Ambiguity = stop... never guess") and a feedback loop for the failure case (a no-op deploy means re-run step 1, not re-deploy harder), so the destructive-operation cap does not apply.

5 / 5

Progressive Disclosure

Under 50 lines, no bundle files exist to reference, and the content is well-organized into Workflow and Rules sections, satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

19

/

20

Passed

Description

78%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 tight, distinctive description that names four concrete guard behaviors and an explicit applicability condition. Its main gap is the absence of a 'Use when...' clause with natural user-facing trigger phrases and command synonyms, which keeps completeness and trigger-term quality at 4 rather than 5.

Suggestions

Add an explicit trigger clause in user language, e.g. 'Use when the user asks to deploy, run functions, or change environment variables on a Convex deployment (dev, preview, or production).' to make the 'when' concrete rather than procedural.

Include common synonyms and literal commands — 'production' (not just 'prod'), 'npx convex deploy', 'npx convex run --prod' — so natural phrasings users actually say match the description.

DimensionReasoningScore

Specificity

Names four concrete behaviors — "Classify + announce the target Convex deployment", "fresh explicit consent for prod actions", "session read-only mode" — but omits capabilities the body covers (MCP flag handling, wrong-deployment diagnosis), leaving minor gaps in coverage.

4 / 5

Completeness

The 'what' is explicit and a 'when' is stated via "before any deployment-affecting command", but there is no 'Use when...' clause with concrete user-facing trigger phrases, placing it between anchor 4 and anchor 5 rather than clearly at 5.

4 / 5

Trigger Term Quality

Natural terms a Convex user would say are present ("Convex deployment", "prod", "read-only"), but common variations are missing — "production", "dev/preview", and literal commands like "npx convex deploy" — so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

"Convex deployment" combined with "prod" and "read-only mode" carves a clear niche with distinct triggers and minimal conflict risk against non-Convex skills.

5 / 5

Total

17

/

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

FacundoLucci/autonomous-buyer

Path

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