CtrlK
BlogDocsLog inGet started
Tessl Logo

convex-performance-audit

Audits Convex performance for reads, subscriptions, write contention, and function limits. Use for slow features, insights findings, OCC conflicts, or read amplification.

71

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 well-structured, largely lean skill body with a clear sequenced workflow, explicit verification checkpoints, and clean one-level-deep reference routing. The only modest gaps are minor verbosity and the bulk of executable code living in references rather than the body.

DimensionReasoningScore

Conciseness

The body is lean and well-organized, assuming Claude's competence, with only minor explanatory prose (e.g., the Guardrails elaboration and the Convex read/write invalidation note) that could be trimmed slightly.

4 / 5

Actionability

It gives concrete commands ("npx convex insights --details", "npx -y convex@latest insights --details") and specific API surface to trace (ctx.db.get/query/patch/replace/insert, useQuery/usePaginatedQuery/useMutation), but the body itself is instruction-heavy with executable code deferred to the reference files.

4 / 5

Workflow Clarity

A clear five-step workflow is sequenced with an explicit validation step ("Verify before finishing" with five checkpoints), a retry feedback loop for stale CLIs, and a closing checklist, satisfying the validation/feedback/checklist anchor.

5 / 5

Progressive Disclosure

The body is an overview with a Signal Routing table and a Reference Files section pointing to four real, one-level-deep reference files (hot-path-rules.md, occ-conflicts.md, subscription-cost.md, function-budget.md), all verified present, with detail appropriately split out.

5 / 5

Total

18

/

20

Passed

Description

87%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 strong, third-person description that clearly states what the skill does and when to use it with concrete, platform-specific triggers. Minor gaps in action-verb variety and a few missing trigger synonyms keep specificity and trigger quality at 4 rather than 5.

DimensionReasoningScore

Specificity

"Audits Convex performance for reads, subscriptions, write contention, and function limits" names the domain plus four concrete audit dimensions, but relies on a single verb ("Audits") rather than listing multiple distinct actions, leaving it just below the comprehensive multi-verb anchor.

4 / 5

Completeness

It explicitly answers both what ("Audits Convex performance for reads, subscriptions, write contention, and function limits") and when ("Use for slow features, insights findings, OCC conflicts, or read amplification") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"Use for slow features, insights findings, OCC conflicts, or read amplification" includes natural phrases a debugging user would say, though a few common variants (e.g. "expensive", "timeouts", "subscription cost") are absent.

4 / 5

Distinctiveness Conflict Risk

The Convex-specific niche and platform-scoped triggers make it clearly distinguishable from other skills with minimal conflict risk.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openclaw/clawhub
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.