CF vercel-ai-gateway
Vercel AI Gateway API integration with managed authentication. Browse the model catalog across 30+ providers, inspect per-provider endpoints, pricing, and uptime, check credit balance, look up generation usage, and run OpenAI-compatible inference (chat completions, responses, embeddings) or Anthropic-shaped messages. Use this skill when users want to discover available models, compare provider pricing or context windows, monitor AI Gateway credits and spend, or route inference requests through Vercel AI Gateway. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Vercel AI Gateway connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Vercel AI Gateway 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 Vercel AI Gateway examples; they add no Vercel AI Gateway capability - Vercel AI Gateway is not an event source, a trigger cannot read Vercel AI Gateway data, 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).
Vercel AI Gateway API integration with managed authentication.
As a process F 51/100 · Will not run — References files that are not bundled: references/<source>/triggers.md, references/{source}/triggers.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Shorten the description to 1024 characters.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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 · 16
✓ No critical or high findings
Medium and low: 16
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Bash Read Grep Glob
-
low Secrets in code
secret-high-entropy-tokenreferences/github/triggers.md:1139High-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-tokenreferences/github/triggers.md:1313High-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-blobreferences/slack/triggers.md:73Long base64-looking blob (quoted — discussed, not commanded)"event_context": "4-ey…ifQ",
quoted -
low Obfuscation
obf-base64-blobreferences/slack/triggers.md:133Long base64-looking blob (quoted — discussed, not commanded)"event_context": "4-ey…ifQ",
quoted -
low Obfuscation
obf-base64-blobreferences/slack/triggers.md:179Long base64-looking blob (quoted — discussed, not commanded)"event_context": "4-ey…In0",
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/stripe/triggers.md:41High-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-tokenreferences/stripe/triggers.md:117High-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-tokenreferences/stripe/triggers.md:144High-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-tokenreferences/stripe/triggers.md:180High-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-tokenreferences/stripe/triggers.md:194High-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-tokenSKILL.md:1190High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"id": "gen_…03M",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:1291High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"id": "gen_…9X6",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:1317High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"generationId": "gen_…9X6"
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:1338High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"generationId": "gen_…9X6"
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:1370High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"id": "gen_…V2B",
quoted
Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1880 chars, limit 1024 - warning
body-longSKILL.md body ≈ 20053 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/<source>/triggers.md - warning
missing-refreference to a missing file: references/{source}/triggers.md - note
description-budgetdescription takes 1880 of the ~15000-char shared budget for all skills - note
edit-residuethe text marks something as outdated (lines 689, 1032, 1034, 1520): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 51/100
- 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 20053 tokens: crowds the task out of the window
- 30Running it twice. 85 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 107 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 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
- low The skill ranks results itself: that belongs to the system behind the tool, not the model
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 1879: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 91 headings
- +3Step-by-step instructions: 107 items
- +3Output format is stated explicitly
- +4Has examples (104 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 37.