AB stripe-direct-connection
Stripe payments, subscriptions, invoicing, refunds, disputes, and balance — full read/write for customers. Use when an agent needs stripe, stripe direct connection, launch saas subscription billing with recurring prices and hosted payment links, automate customer onboarding and crm to stripe sync, generate stripe checkout payment links for e commerce orders, run customer support refund workflows with reason tracking, cancel subscription, subscription through AgentPMT-hosted remote tool calls.
Stripe payments, subscriptions, invoicing, refunds, disputes, and balance — full read/write for customers.
As a process B 75/100 · Nearly there — weak spots: running it twice, progress reporting
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5939 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 75/100
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 67 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 5939 tokens
- 85Steps. 79 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 top-level sections: this looks like several domains in one skill
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)
- +1No license
- +2Single-language instructions
- +3Description length 497: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 79 items
- +3Output format is stated explicitly
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.