altllm-portal-payments

Use this skill when the user asks to create a NOWPayments crypto payment link, poll payment status, or execute a supported direct wallet payment through the AltLLM Portal CLI. Do NOT use for wallet login, API key management, billing history, or x402 credit top-ups.

Quality

82%

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

Quality

Content

72%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 well-structured, token-efficient overview that uses progressive disclosure effectively and delegates executable detail to a verified reference file. Its weaknesses are in the body itself: it contains no executable command invocations and no explicitly sequenced validated workflow for these destructive payment operations.

Suggestions

Add one minimal end-to-end command example inline (e.g. a topup-crypto + payment-status --wait sequence) so the body is actionable without requiring the reference for the common case.

Include a short numbered workflow with an explicit validation checkpoint (e.g. preview discount code → verify allowedPayCurrencies → create link → poll until settled) to lift workflow_clarity above the destructive-operation cap of 3.

Surface the discount-code top-up flow in the command index or a one-line example, since it is heavily governed by the guardrails but invisible as an actionable path in the body.

Dimension	Reasoning	Score
Conciseness	Lean ~40-line overview that assumes Claude's competence — no padding about what NOWPayments or crypto payments are; every section (command index, guardrails, setup pointer) earns its place.	5 / 5
Actionability	The body names concrete commands (topup-crypto, payment-status, pay-payment-link) and specific operational guardrails (terminal states, supported currencies), but the executable invocations themselves live in the referenced file rather than in the body.	3 / 5
Workflow Clarity	The guardrails encode validation rules (fail fast, no paying terminal links, preview before creation, reject mismatched currencies), but no sequenced multi-step workflow appears in the body; the destructive-payment cap-at-3 applies since financial operations lack an inline validated step sequence.	3 / 5
Progressive Disclosure	Textbook progressive disclosure: a concise overview with a command index and guardrails inline, delegating workflows and outputs to a clearly signaled one-level-deep references/cli-reference.md that exists in the bundle.	5 / 5
	Total	16 / 20 Passed

Description

92%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 names concrete capabilities, provides explicit trigger guidance, and clearly deconflicts from related skills via a negative boundary. The only gap is modest synonym coverage in the trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'create a NOWPayments crypto payment link, poll payment status, or execute a supported direct wallet payment' — covering the skill's core capabilities comprehensively.	5 / 5
Completeness	Explicitly answers both what (create/poll/execute payment flows via the AltLLM Portal CLI) and when ('Use this skill when the user asks to...') with concrete trigger phrases, plus explicit exclusions.	5 / 5
Trigger Term Quality	Good natural keywords like 'crypto payment link', 'poll payment status', and 'direct wallet payment', but lacks common synonyms/variations a user might say (e.g. 'pay with crypto', 'check my payment', 'top up').	4 / 5
Distinctiveness Conflict Risk	Clear niche (NOWPayments crypto payments via AltLLM Portal CLI) with an explicit 'Do NOT use for wallet login, API key management, billing history, or x402 credit top-ups' boundary that actively deconflicts the sibling x402 skill.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: internet-court/internet-court-skill
Path: vendored/altlayer/altllm-portal-payments/SKILL.md
Commit: fa89195

Reviewed: 4 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.