CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

x402-api-paywall

Add stablecoin micropayment paywalls to FastAPI and Express routes using the HTTP 402 standard. Use when: Monetize specific high-cost API endpoints for AI agent consumption; Enforce per-request billing without managing complex user accounts; Integrate standard HTTP 402 handshakes into existing Node or Python backends.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/nex-dev-essentials/skills/x402-api-paywall/SKILL.md

The canonical home for this skill is x402-api-paywall in NexaiGuy/nex-ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body reads as a product landing page rather than an agent skill: it markets the skill's value, answers customer FAQs, and links to the vendor's catalog, but provides almost no executable guidance for actually implementing an x402 paywall. The empty bundle (no scripts, templates, or references) means the promised middleware workflow is entirely absent. Only the small example section approaches instructional content.

Suggestions

Replace the FAQ and promotional sections with a concrete integration workflow: numbered steps for adding the payment dependency to a FastAPI route and mounting middleware in Express, including install commands and facilitator configuration.

Provide complete, executable code for the middleware/dependency (e.g., a full require_payment implementation with the 402 response format and proof-verification call) instead of the single illustrative snippet with a '...' placeholder body.

Either bundle the referenced scripts/templates or replace the note that they are 'not in this folder' with pointers to equivalent inline content, and add a validation step (e.g., testing with a mocked payment proof) to the workflow.

DimensionReasoningScore

Conciseness

The body is padded with marketing prose ("Turn your API into a Revenue Stream"), promotional links ("Built by Nex AI. More skills and info at nex-ai.be and slopsome.com"), and a six-question FAQ that adds no instructional value; it does not lecture on known concepts, which keeps it above anchor 1. Sections like "What it does" and "Why use this over raw prompting?" describe the skill's value proposition rather than teach anything Claude needs.

2 / 5

Actionability

The only code present is a result illustration fragment ("dependencies=[Depends(require_payment)]" with a "..." body), not executable guidance; there are no install commands, middleware implementation details, or facilitator configuration steps. This is minimal concrete guidance with high-level hints only, matching anchor 2 rather than anchor 1 only because one partially concrete snippet exists.

2 / 5

Workflow Clarity

No integration sequence exists anywhere in the body; "What it does" describes the protocol's runtime behavior (detect missing payment, return 402, verify proof) rather than steps Claude would take. This matches anchor 1 — steps missing, no sequence, no validation checkpoints.

1 / 5

Progressive Disclosure

The body has clear section headers and is short enough to navigate, but the bundle directory contains no reference, script, or asset files — the body itself admits "Scripts, extension source, and templates from the original package are not in this folder" — and no replacement pointers are given. Structure exists but organization is undermined by inlined FAQ/marketing content and a missing implementation layer.

3 / 5

Total

8

/

20

Passed

Description

82%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 description with a clear, specific capability statement and an explicit multi-scenario "Use when" clause. Trigger terms are natural and domain-specific. The only weakness is that it describes a single composite action rather than enumerating several distinct capabilities.

DimensionReasoningScore

Specificity

"Add stablecoin micropayment paywalls to FastAPI and Express routes using the HTTP 402 standard" names one concrete action with specific technologies, but no additional capability actions are listed; this matches anchor 3 (domain plus 1-2 concrete actions) rather than anchor 4 (several specific actions).

3 / 5

Completeness

It explicitly answers both what ("Add stablecoin micropayment paywalls to FastAPI and Express routes using the HTTP 402 standard") and when, via an explicit "Use when:" clause with three concrete trigger scenarios, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Includes natural user phrases like "monetize", "paywalls", "per-request billing", "micropayment", and framework names "FastAPI" and "Express", giving good keyword coverage; a few natural variants (e.g., "charge for API access", "402") are missing, so it is not the comprehensive anchor-5 coverage.

4 / 5

Distinctiveness Conflict Risk

The niche is highly distinct — HTTP 402 stablecoin paywalls on two named frameworks with AI-agent billing triggers — so it is clearly distinguishable from other skills with minimal risk of triggering for the wrong skill.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NexaiGuy/nex-ai-skills

Path

plugins/nex-dev-essentials/skills/x402-api-paywall/SKILL.md

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.