agentleFS
Sign inStart free
0xOpCode0xOpCode/tele-harness/.agents/skills/payment-gateway-setup/SKILL.md

payment-gateway-setup

Skill1 starsChanged 49 days agoMITView on GitHub

Integrates Telegram Payments API, Telegram Stars, and external crypto payment processors.

  • Reads credentials

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. Distinctive:

    Follow these constraints when integrating payments into Telegram bots:

    line 9
  2. Very specific:

    Use currency XTR with an empty provider token for Telegram Stars.

    line 13

≈ “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

Payment Gateway Protocol

Follow these constraints when integrating payments into Telegram bots:

  1. Native Telegram Invoices:
    • Configure PROVIDER_TOKEN in .env for fiat gateways (Stripe, Smart Glocal).
    • Use currency XTR with an empty provider token for Telegram Stars.
    • Dispatch invoices using sendInvoice with required parameters:
      • title, description, payload
      • currency
      • prices (Array of labeled price units in smallest currency fractions)
  2. Pre-Checkout Verification:
    • Listen for pre_checkout_query updates.
    • Validate order inventory, user status, and pricing consistency.
    • Respond within 10 seconds using answerPreCheckoutQuery(ok=True). Unanswered queries abort transaction.
  3. Order Fulfillment:
    • Listen for successful_payment message updates.
    • Record transaction identifier and payment provider charge ID in database.
    • Deliver purchased entitlement before returning success response.
    • Handle duplicate webhook deliveries with idempotency keys.

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