CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

convex-billing

Add Stripe billing/payments to the Convex app via @convex-dev/stripe (checkout + webhook + gating).

Quality

81%

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

82%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 actionable, executable skill with complete code, exact commands, and a verification checkpoint, structured cleanly as Workflow plus Rules. Weaknesses are minor: the Rules section repeats earlier steps, error-recovery guidance is absent, and the full billing implementation is inlined where a reference file could carry it.

DimensionReasoningScore

Conciseness

Lean body with zero concept explanation and only load-bearing code, but the Rules section duplicates step 3 (env keys) and step 4 (signature verification) content — a minor trim opportunity that keeps it just below the 'every token earns its place' anchor.

4 / 5

Actionability

Fully executable end to end: complete convex.config.ts, http.ts, and billing.ts files with real imports and validators, plus exact install/push commands and precise Stripe Dashboard endpoint and event configuration — copy-paste ready with no gaps.

5 / 5

Workflow Clarity

The 7-step sequence is clearly ordered with an explicit checkpoint (step 6: "Verify output shows `✔ Installed component stripe.`") and a precise webhook-setup step, fitting 'most checkpoints present; minor validation gaps'; it misses the error-recovery feedback loop (e.g., what to do if the push or webhook test fails) needed for the top anchor.

4 / 5

Progressive Disclosure

Well-organized single-file skill (Workflow → Rules) with no bundle files and no need for external references, but at ~80 lines with the full billing.ts implementation inline it sits above the simple-skill threshold and the implementation code could live in a reference file — good structure with minor organization gaps.

4 / 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 that names concrete capabilities and the exact package, but it lacks any "Use when…" trigger clause and misses natural synonyms like "subscriptions". Adding explicit usage triggers would raise both completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when adding Stripe payments, subscriptions, or checkout to a Convex app, or when the user mentions @convex-dev/stripe or webhook setup."

Include natural synonyms users would actually say — "subscriptions", "paywall", "Stripe integration" — to broaden trigger-term coverage.

Phrase the gating capability in searchable user-facing terms (e.g., "gate features behind an active subscription") so it reads as a discoverable behavior.

DimensionReasoningScore

Specificity

Names the domain (Stripe billing/payments on Convex) plus three concrete actions — "checkout + webhook + gating" — and the exact package @convex-dev/stripe, matching the 'several specific actions; minor gaps' anchor; not a 5 since coverage omits subscription lifecycle management, customer portal, and price/product setup.

4 / 5

Completeness

The 'what' is clear and specific, but there is no "Use when…" clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Contains natural terms users would say ("Stripe billing/payments", "checkout", "webhook", "Convex") but misses common synonyms like "subscription(s)" and "paywall", fitting the 'good keyword coverage; a few natural terms missing' anchor rather than comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The Stripe + Convex + @convex-dev/stripe pairing is a narrow, unambiguous niche with distinct triggers and minimal conflict risk with any other skill.

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

openclaw/clawhub

Path

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