BD stripe
Query Stripe customer and billing data from a synced PostgreSQL database. Use when the user asks about Stripe customers, subscriptions, invoices, charges, or any Stripe-related data.
As a process D 35/100 · Unfinished process — weak spots: steps, result and completion, inputs and preconditions
ProcedurePostgreSQLStripeInfrastructureFinancetype and topics are labelled automatically from the skill text
How to improve
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 35/100
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 66 mutating operations with no state check
- 40Consistency. Frontmatter name (stripe) differs from the folder (paymentsdb)
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 4807 tokens
- 100Tools and files. No external tools needed
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +4Structure: 0 headings, hard to scan
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -5Long text without headings
- +1No license
- +2Single-language instructions
- +3Description length 182: enough signal without eating the budget
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.
External checks
ClawHub: suspicious
This Stripe database skill is understandable in purpose, but it gives the agent broad SQL access to sensitive billing data and asks users to put database credentials in a script.
LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026