The content is highly actionable and token-efficient, with executable code and a clear sequenced workflow including a verification step. The main gap is the absence of an explicit end-to-end validation feedback loop for the webhook/checkout integration.

Suggestions

Add a final validation step that tests the checkout flow and confirms isSubscribed returns true after a successful webhook, with a retry-on-failure note.

Consider moving the Stripe Dashboard webhook configuration (step 7) into a short reference section to keep the core integration workflow tighter.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient — direct commands and tight, executable code blocks with no padding or explanation of what Stripe/Convex is — matching 'lean and efficient; assumes Claude's competence'.	5 / 5
Actionability	It provides copy-paste-ready, complete code for convex.config.ts, http.ts, and billing.ts plus concrete CLI and Stripe-dashboard steps with expected verification output, matching 'fully executable; copy-paste ready code or commands'.	5 / 5
Workflow Clarity	The 7-step sequence is clear with a verification checkpoint (step 6 output check), but it lacks an explicit validate-and-retry feedback loop for the webhook/checkout integration, fitting 'clear sequence with most checkpoints; minor validation gaps'.	4 / 5
Progressive Disclosure	Content is well-organized into Workflow and Rules sections with no nested references, but at ~80 lines it sits just above the simple-skill threshold and keeps everything inline with no external file split, matching 'good structure; most content appropriately placed; minor organization gaps'.	4 / 5
	Total	18 / 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.

The description is specific and distinct, naming a concrete library and three actions, but it lacks any explicit 'Use when' trigger guidance, which caps its completeness. Adding a trigger clause would push it toward the top of the scale.

Suggestions

Append a 'Use when adding Stripe billing, subscriptions, or payments to a Convex app' trigger clause to satisfy the 'when' half of completeness.

Include natural synonyms like 'subscriptions' or 'invoices' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain, the specific library (@convex-dev/stripe), and three concrete actions ('checkout + webhook + gating'), matching 'lists several specific actions; minor gaps' rather than the comprehensive coverage of a 5.	4 / 5
Completeness	It has a clear, specific 'what' but no explicit 'when'/'Use when' trigger clause; per the guidelines a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms a user would say ('billing', 'payments', 'Stripe', 'checkout', 'webhook', 'gating') are present, but synonyms like 'subscriptions' or 'invoice' are missing, fitting 'good keyword coverage; a few natural terms missing'.	4 / 5
Distinctiveness Conflict Risk	The niche is highly specific (Convex + Stripe via @convex-dev/stripe), giving it distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	16 / 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-billing/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.