agentleFS
Sign inStart free
runxhqrunxhq/runx/skills/charge/SKILL.md

charge

Skill97 starsChanged 32 days agoApache-2.0View on GitHub

Verify and settle one provider-side paid call through Runx Hosted with approval and provider readback.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill when Runx is the provider of a paid operation.

    line 22
  2. Distinctive:

    Stop on missing or ambiguous policy, credential reference, capability, counterparty, or idempotency material.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Charge

charge is the public seller-side contract for a paid operation. Its OSS graph is deliberately thin: it submits the exact tool call, hosted pricing policy, opaque returned credential reference, verification capability reference, and idempotency seed to the approved Runx Hosted payment operation, then requires a provider readback before the run can close.

Runx Hosted owns pricing validation, challenge and credential semantics, settlement admission, provider credentials, rail execution, idempotency, recovery, and the private payment ledger. The OSS runtime owns the generic provider-effect gate and receipt envelope. It does not implement a payment rail or infer settlement from caller input.

Operator guide

Use this skill when Runx is the provider of a paid operation. Use spend on the buyer side and refund for a receipt-linked reversal. A hosted connector and grants for payment.charge and payment.charge.read are required.

Stop on missing or ambiguous policy, credential reference, capability, counterparty, or idempotency material. Refuse raw card, wallet, provider-key, or bearer material. Never release the paid operation unless hosted execution and readback agree on a terminal successful charge.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free