mpp-agent

Pay HTTP 402 APIs via Machine Payments Protocol (MPP).

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/payments/mpp-agent/SKILL.md

Quality

Content

88%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 is an efficient, highly actionable guide with a well-sequenced procedure and explicit validation; structure and external references are clearly signaled with only minor organization gaps.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's knowledge (no filler about HTTP 402 fundamentals), with only minor redundancy between the client-choice table and the following default-client paragraph.	4 / 5
Actionability	Commands are concrete and copy-paste ready across the common cases (install, probe with curl, GET pay, POST with body, verify receipt, version check).	5 / 5
Workflow Clarity	The mppx path is a clearly numbered sequence with explicit validation checkpoints: a curl probe to confirm the server speaks MPP and a verification gate (exit code 0).	5 / 5
Progressive Disclosure	Well-organized sections with clearly signaled one-level-deep external references (Tempo/Privy/AgentCash SKILL.md via web_extract, mpp.dev quickstart); no local bundle files exist, and a couple of inline blocks could conceivably be split out.	4 / 5
	Total	18 / 20 Passed

Description

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

The description is clear and distinctive about a niche capability, but it states only one action and lacks any "Use when..." trigger guidance, leaving a user unsure when to invoke it.

Suggestions

Add a trigger clause, e.g. "Use when an API returns HTTP 402 Payment Required or the user asks to pay per request."

Broaden action coverage beyond a single verb, e.g. "discover, challenge, and pay MPP-priced APIs."

Include at least one natural user-facing phrase ("pay per request", "agent wallet") alongside the technical MPP term.

Dimension	Reasoning	Score
Specificity	Names the domain (MPP, HTTP 402 APIs) and one concrete action ("Pay...APIs"), but lists only a single action rather than several comprehensive ones.	3 / 5
Completeness	A clear "what" is stated (pay 402 APIs via MPP) but there is no "when"/trigger clause, which caps completeness per the rubric guideline.	3 / 5
Trigger Term Quality	Relevant keywords ("HTTP 402", "Machine Payments Protocol", "MPP") are present but lean toward technical jargon and miss natural user phrasings like "pay per request" or "payment required".	3 / 5
Distinctiveness Conflict Risk	The HTTP 402 / MPP niche is highly distinctive with minimal overlap risk against other skills.	5 / 5
	Total	14 / 20 Passed

Validation

81%

Warnings & errors only

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

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: optional-skills/payments/mpp-agent/SKILL.md
Commit: 6327930

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.