CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

convex-backup

Set up Convex backups and run a restore DRILL that proves recovery — snapshot, restore into a throwaway preview, assert the data came back — plus a schedule matched to your RPO and a gated recovery runbook.

Quality

79%

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-backup/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 workflow with concrete commands, explicit validation, and strong safety rules (throwaway preview target, never prod, data hygiene). The few gaps are a missing concrete assertion example, minor repetition, and no retry guidance on drill failure.

Suggestions

Add a concrete example of the recovery assertion, e.g. a sample MCP query or the exact tables/row-count check to run in step 4(d).

State the '0 rows = FAILED' criterion once (in step 4(d)) and let the Rules section reference it rather than repeating it verbatim.

Add brief error-recovery guidance for a failed drill (e.g. re-run export, check import logs, retry against a fresh preview) to close the feedback loop.

DimensionReasoningScore

Conciseness

Efficient and command-driven with no basic-concept padding, but the rhetorical intro ('the half almost nobody does — this is the point') and the duplicated 'a restore that lands 0 rows is a FAILED drill' statement (step 4d and Rules) could be trimmed.

4 / 5

Actionability

Every operation has a copy-paste-ready command with exact flags (export, preview-create, import with --deployment-by-name, --replace --prod), including a real flag gotcha; the only minor gap is that the step 4(d) assertion names MCP tools ('tables', 'data'/'runOneoffQuery') without a concrete example query.

4 / 5

Workflow Clarity

Six clearly sequenced steps with an explicit precondition-plus-fallback, an explicit ASSERT validation checkpoint with a defined failure criterion (0 rows = FAILED), and hygiene — but no fix-and-retry feedback loop after a failed drill, which keeps it below the 5 anchor.

4 / 5

Progressive Disclosure

A self-contained single-file skill under 50 lines with well-organized Workflow and Rules sections and no need for external references, matching the rubric's simple-skill exception for a 5.

5 / 5

Total

17

/

20

Passed

Description

70%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 specific, distinctive description with concrete actions and good natural keywords. Its main weaknesses are the missing 'Use when...' trigger clause (capping completeness) and one second-person slip ('your RPO').

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to back up Convex data, verify a backup restores, or prepare disaster recovery for a Convex deployment.'

Include common synonyms such as 'disaster recovery', 'DR', or 'export' so the description matches how users naturally phrase the need.

Rewrite in consistent third-person voice: replace 'a schedule matched to your RPO' with 'a schedule matched to the project's RPO'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('set up Convex backups', 'run a restore DRILL', 'snapshot, restore into a throwaway preview, assert the data came back', 'gated recovery runbook') with comprehensive coverage, but the second-person phrasing 'matched to your RPO' incurs the guideline's 1-point voice penalty from 5.

4 / 5

Completeness

The 'what' is clear and detailed (backup setup, restore drill, schedule, runbook), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good natural keywords — 'backup', 'restore', 'recovery', 'snapshot', 'Convex' — that users would plausibly say, though common synonyms like 'disaster recovery', 'DR', or 'export' are missing, so coverage is not comprehensive.

4 / 5

Distinctiveness Conflict Risk

Firmly niche — Convex-specific backup-and-restore-drill with distinct trigger terms ('restore DRILL', 'snapshot', 'RPO') — so overlap with other skills is minimal.

5 / 5

Total

16

/

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-backup/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.