SKILLEMALL.ai
GitHub ↗ RU Sign in

CF stripe

Stripe API integration with managed OAuth. This is a write-capable financial integration for customers, subscriptions, invoices, products, prices, and payments. Install only if you need Stripe administration. Connect with the least-privileged Stripe account and OAuth scopes available, verify the intended connection ID before each request, and revoke unused connections promptly. All write operations require explicit user approval showing the exact endpoint, target resource, object IDs, amounts, and test/live mode before execution. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI after `maton login --oauth`; the Stripe credential stays in the gateway and is never handled locally. Only your own Maton credential is used locally — held by the CLI, or supplied as `MATON_API_KEY` in the appendix fallback. Default to read and list calls, stay on the endpoints this skill documents, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Stripe connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Stripe action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Stripe examples; they add no Stripe capability - Stripe is itself an event source, so its own events are in `references/stripe/triggers.md`, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).

ClawHub Agent Skills author: byungkyu v1.2.4 MIT-0 11 files body ≈ 16 708 tokens Open the sourceclawhub.ai↗ analyzed 29 h ago

Stripe API integration with managed OAuth.

As a process F 44/100 · Will not run — References files that are not bundled: references/<source>/triggers.md, references/{source}/triggers.md

IntegrationStripeNotionSlackGmailFinanceSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
C
63/100
safety, quality, tests
Safety 60%
81
Quality 40%
37
Run on models
none yet
Process rating
F
44/100
Will not run
References files that are not bundled: references/<source>/triggers.md, references/{source}/triggers.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Execution cost w 6
10
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. Shorten the description to 1024 characters.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  3. The text references files that are not there: add them or drop the references.
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 · 15

✓ No critical or high findings

Medium and low: 15
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Bash Read Grep Glob
  • low Secrets in code secret-high-entropy-token references/github/triggers.md:1139
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "node_id": "MDIz…DU3"
    quoted
  • low Secrets in code secret-high-entropy-token references/github/triggers.md:1313
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "node_id": "MDEw…jY5",
    quoted
  • low Obfuscation obf-base64-blob references/slack/triggers.md:73
    Long base64-looking blob (quoted — discussed, not commanded)
    "event_context": "4-ey…ifQ",
    quoted
  • low Obfuscation obf-base64-blob references/slack/triggers.md:133
    Long base64-looking blob (quoted — discussed, not commanded)
    "event_context": "4-ey…ifQ",
    quoted
  • low Obfuscation obf-base64-blob references/slack/triggers.md:179
    Long base64-looking blob (quoted — discussed, not commanded)
    "event_context": "4-ey…In0",
    quoted
  • low Secrets in code secret-high-entropy-token references/stripe/triggers.md:41
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "balance_transaction": "txn_…GxW",
    quoted
  • low Secrets in code secret-high-entropy-token references/stripe/triggers.md:117
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "id": "evt_…qVg",
    quoted
  • low Secrets in code secret-high-entropy-token references/stripe/triggers.md:144
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "subscription": "sub_…qSY"
    quoted
  • low Secrets in code secret-high-entropy-token references/stripe/triggers.md:180
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "subscription": "sub_…qSY",
    quoted
  • low Secrets in code secret-high-entropy-token references/stripe/triggers.md:194
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "subscription": "sub_…qSY",
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:1260
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "id": "pric…SmO",
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:1349
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "id": "sub_…tDh",
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:1360
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "id": "pric…q9m",
    detector
  • low Secrets in code secret-high-entropy-token SKILL.md:1466
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "subscription": "sub_…tDh",
    quoted

Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • error description-long description is 1742 chars, limit 1024
  • warning body-long SKILL.md body ≈ 16708 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: references/<source>/triggers.md
  • warning missing-ref reference to a missing file: references/{source}/triggers.md
  • note description-budget description takes 1742 of the ~15000-char shared budget for all skills
  • note edit-residue the text marks something as outdated (lines 691): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 44/100

Will not run. References files that are not bundled: references/<source>/triggers.md, references/{source}/triggers.md
  • 0Tools and files. 2 referenced file(s) missing: references/<source>/triggers.md, references/{source}/triggers.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 10Execution cost. Instruction body is 16708 tokens: crowds the task out of the window
  • 30Running it twice. 140 mutating operations with no state check
  • 40Consistency. Frontmatter name (stripe) differs from the folder (stripe-api)
  • 50When it triggers. No condition that starts the skill
  • 60Result and completion. Output format stated, no completion criterion
  • 85Steps. 66 steps, 1 vague phrases
  • 100Failures and branches. 3 branches, has a failure section
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 14 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)
  • +3Description length 1741: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 131 headings
  • +3Step-by-step instructions: 66 items
  • +3Output format is stated explicitly
  • +4Has examples (185 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 37.

External checks

ClawHub: clean
This is a transparent but high-impact Stripe administration skill; the main caution is an optional webhook example that may expose a receiver signing key in shell history or logs.
LLM: benign (high) · VirusTotal: · 13 Sept 2026