CtrlK
BlogDocsLog inGet started
Tessl Logo

agents-pay

Use when THIS agent needs to pay for x402-protected content at runtime: hitting a paywall mid-task, settling it via AgentCore Payments, and applying operator-defined spend limits. Covers payment setup, policy, session budgets, and troubleshooting. Triggers on: "my agent hit a 402 while calling an API", "a tool call returned 402 Payment Required", "my agent needs to pay for x402-protected content", "let the agent pay for content, capped at $5 per session", "set a spend limit for the agent", "ProcessPayment failed", or "why did my agent refuse to pay". Not for BUILDING payment capability for end users, including wallets and framework middleware; use agents-build and references/payments.md. For non-paid APIs via Gateway use agents-connect. For inbound auth use agents-harden. For project scaffolding use agents-get-started.

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

The canonical home for this skill is agents-pay in aws/agent-toolkit-for-aws

SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

A thorough, highly actionable skill body with a clear sequenced process, executable commands, and well-signaled references. Its main weakness is conciseness: the core security principle is repeated across several sections and some conceptual material could be consolidated into the reference files it already points to.

Suggestions

Consolidate the role-separation/IAM message into one authoritative section (e.g. 'Read this before deploying') and reference it from the other sections instead of restating it in Architecture, Step 4, 'How the policy is honored across platforms', and Quality criteria.

Add references/openclaw-setup.md to the Files table so every referenced file is discoverable from one central index.

Move the conceptual 'How the policy is honored across platforms' and 'Cross-runtime notes' analysis into references/security-model.md, keeping SKILL.md to the actionable process and a brief pointer.

DimensionReasoningScore

Conciseness

Mostly efficient and domain-specific, but the role-separation security principle is restated in five separate sections ('Read this before deploying', 'Architecture', Step 4, 'How the policy is honored across platforms', 'Quality criteria') and several conceptual/argumentative passages ('The one idea that matters', 'How the policy is honored across platforms') could be tightened or moved to references.

3 / 5

Actionability

Fully executable throughout — exact bash commands with flags ('agents_pay_admin.py new-session --budget 1.00 --expiry-minutes 60'), a config-key table, copy-paste Python for the browser handle flow, a CLI flag table, and explicit exit-code semantics cover the common cases.

5 / 5

Workflow Clarity

A clearly sequenced Step 0–6 process with explicit validation checkpoints (preflight in Step 5, 'test_x402_policy.py... all must pass' in Step 6) and a closing Quality criteria checklist; not a 5 because the test-failure fix-and-revalidate loop is implied rather than spelled out as an explicit feedback loop.

4 / 5

Progressive Disclosure

A well-organized Files table signals one-level-deep references to four reference docs and five scripts, and the body largely acts as an overview with inline links; however references/openclaw-setup.md is cited in Step 5 but omitted from the central Files table, and some inline platform-policy analysis could live in references/security-model.md.

4 / 5

Total

16

/

20

Passed

Description

95%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 strong, third-person description that crisply states a runtime payment niche, enumerates natural trigger phrases, and actively disambiguates from four sibling skills. Specificity is the only slightly soft dimension, as some listed coverage areas are domains rather than equally concrete actions.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'hitting a paywall mid-task, settling it via AgentCore Payments, and applying operator-defined spend limits' plus 'payment setup, policy, session budgets, and troubleshooting' — but the latter grouping is domain enumeration rather than equally concrete actions, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ('pay for x402-protected content at runtime... settling it via AgentCore Payments, and applying operator-defined spend limits') and when (a 'Use when...' clause plus a dedicated 'Triggers on:' list of concrete phrases).

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases including synonyms and error strings — 'my agent hit a 402 while calling an API', 'a tool call returned 402 Payment Required', 'set a spend limit for the agent', 'ProcessPayment failed', 'why did my agent refuse to pay' — covering the ways users would actually phrase the need.

5 / 5

Distinctiveness Conflict Risk

Clear niche with explicit 'Not for...' disambiguation against sibling skills — 'use agents-build', 'For non-paid APIs via Gateway use agents-connect', 'For inbound auth use agents-harden', 'For project scaffolding use agents-get-started' — minimizing wrong-skill triggering.

5 / 5

Total

19

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (549 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 16 missing

Warning

referenced_paths_exist

Referenced path issues: 44 missing

Warning

Total

13

/

16

Passed

Repository
aws/agent-toolkit-for-aws
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.