Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Pay Bills
Purchase data, airtime, and digital products for Nigerian phone numbers instantly using wallet balance with network and plan validation.
skill openclawclawhub Free
Purchase data, airtime, and digital products for Nigerian phone numbers instantly using wallet balance with network and plan validation.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- session-token.js, skill.md, generate-order-id.js, generate-device-id.js
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 0.0.5
Provenance
- Publisher
- h1rdr3v2
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
SKILL.md โ CreditWithBleon API
Buy data, airtime, and digital products for Nigerian phone numbers via wallet balance. Base URL: https://lodu.bleon.net/v1
Helper Scripts
These Node.js scripts live in the pay-bills-skill/ directory. Run them with node to generate IDs and manage auth state. ScriptCommandPurposegenerate-order-id.jsnode pay-bills-skill/generate-order-id.jsOutputs a unique ORDER_<timestamp>_<random> string. Use this as trx_id for every order โ never hardcode or reuse a trx_id.generate-device-id.jsnode pay-bills-skill/generate-device-id.js [userId]Outputs a device ID. With userId: openclaw_<userId>. Use as deviceId in auth requests.session-token.jssee belowManages the session token for auth.
Session Token Commands
node pay-bills-skill/session-token.js check โ { "loggedIn": true/false, "sessionToken": "..." | null } node pay-bills-skill/session-token.js save <token> โ saves the token to .session_token node pay-bills-skill/session-token.js load โ prints the saved token (exit 1 if none) node pay-bills-skill/session-token.js clear โ deletes the saved token (logout)
Workflow
Before any [auth] request: run node pay-bills-skill/session-token.js check to see if a session token exists. If loggedIn: true โ use the sessionToken value as Authorization: Bearer <sessionToken>. If loggedIn: false โ start the login flow (see Auth below). After a successful login (steps that return sessionToken): run node pay-bills-skill/session-token.js save <sessionToken> to persist it. Before placing an order: run node pay-bills-skill/generate-order-id.js to get a fresh trx_id. For auth requests: run node pay-bills-skill/generate-device-id.js (no userId before login). After login, run node pay-bills-skill/generate-device-id.js <userId> to bind the device to the user. On logout or 401: run node pay-bills-skill/session-token.js clear and re-auth.
Auth
All [auth] endpoints need Authorization: Bearer <sessionToken>. If 401 โ run node pay-bills-skill/session-token.js clear and re-auth. Login flow (no auth needed): 1. POST /auth/start { "phoneNumber":"08031234567", "deviceId":"<run: node pay-bills-skill/generate-device-id.js>" } โ { success, data: { sessionId, nextStep } } nextStep will be one of: - "verify_otp" โ new user OR unrecognized device - "enter_pin" โ known device, go straight to step 3 2. POST /auth/verify-otp { "sessionId":"<from-step-1>", "code":"123456" } โ 6 digits from SMS โ { success, data: { sessionId, nextStep } } nextStep will be one of: - "set_pin" โ new user, needs to create 4-digit PIN - "enter_pin" โ existing user, new device - "complete_profile" โ profile incomplete 2b. POST /auth/set-pin { "sessionId":"...", "pin":"1234" } โ 4 digits (new users only) โ { success, data: { sessionId, nextStep:"complete_profile" } } 2c. POST /auth/complete-profile { "sessionId":"...", "fullName":"John Doe", "email":"j@x.com" } โ { success, data: { sessionId, nextStep:"verify_email" } } 2d. POST /auth/verify-email { "sessionId":"...", "code":"123456" } โ 6 digits from email โ { success, sessionToken, userId } โ DONE โ then run: node pay-bills-skill/session-token.js save <sessionToken> 3. POST /auth/verify-pin { "sessionId":"<from-above>", "pin":"1234" } โ 4 digits โ { success, sessionToken, userId } โ DONE โ then run: node pay-bills-skill/session-token.js save <sessionToken> Returning user (known device): steps 1 โ 3 only. Returning user (new device): steps 1 โ 2 โ 3. New user: steps 1 โ 2 โ 2b โ 2c โ 2d. Other auth endpoints: POST /auth/resend-otp { sessionId } โ 60s cooldown, max 5/hour POST /auth/forgot-pin { phoneNumber, deviceId } โ OTP flow โ set new PIN POST /auth/logout { sessionToken } โ then run node pay-bills-skill/session-token.js clear Rate limits: OTP: 5 sends/hour, 3 verify attempts/code. PIN: 5 attempts/15min, 5min lockout after.
Buy Data
1. POST /utils/phone/normalize { "phone": "<raw>" } โ { ok, data: "08031234567" } 2. POST /utils/phone/predict { "phone": "08031234567" } โ { ok, data: { phone, network } } 3. GET /product/networks โ [{ id, name, status }] 4. GET /product/networks/:networkId/data-plans โ { categories, plans: { daily[], weekly[], monthly[] } } Each plan: { id, name, amount, durationDays, category, status } โ only use status:"active" 5. GET /user/balance [auth] โ { ok, balance, points } 6. POST /orders [auth] { "type":"data", "payment_method":"wallet", "trx_id":"<run: node pay-bills-skill/generate-order-id.js>", "use_points":false, "data": { "phone":"08031234567", "data_id": 42 } } โ { ok, message, transactionId } 7. GET /orders/:transactionId/status [auth] โ { status, reference, createdAt }
Buy Airtime
Same steps 1-3, skip step 4. Minimum โฆ50. POST /orders [auth] { "type":"airtime", "payment_method":"wallet", "trx_id":"<run: node pay-bills-skill/generate-order-id.js>", "use_points":false, "data": { "phone":"08031234567", "network_id":1, "amount":500 } }
Order Statuses
StatusMeaningpending_paymentAwaiting online paymentorder_receivedProcessing โ poll every 15-30scompletedDeliveredfailedFailed, user auto-refunded Call only if the user wants to know the status of an order they placed.
Other Endpoints (all [auth])
GET /user/balance โ { balance, points } GET /user/profile โ { id, balance, fullName, email, phone } GET /user/deposit-account โ { account: { AccountNumber, AccountName, BankName } | null } GET /transactions?page=&limit=&type=&status=&fromDate=&toDate= โ { transactions[], total, page, totalPages } GET /transactions/recent-phones โ { recentlyUsedPhones: [{ phone_number, network_id, network_name }] } POST /payment/deposit [auth] { amount (min 100) } โ { paymentLink }
Notification Preferences (all [auth])
Users can view and update which notifications they receive. GET /user/notification-preferences โ { ok, preferences } PATCH /user/notification-preferences โ { ok, preferences }
Preference Fields (all boolean, all optional on update)
FieldDescriptionDefaultemailEnabledMaster switch for email channeltruechatEnabledMaster switch for chat channeltrueorderConfirmationsOrder placed / confirmedtrueorderStatusUpdatesOrder completed / failedtruedepositConfirmationsDeposit successfultruepaymentFailuresPayment failed / underpaidtruerefundNotificationsRefund processedtruegiveawayUpdatesGiveaway created / activatedtruegiveawayClaimAlertsSomeone claimed your giveawaytruepointsAndCashbackCashback & points earnedtruepromotionalEmailsMarketing / promotional contenttruelowBalanceWarningBalance below thresholdtrue
Example
PATCH /user/notification-preferences { "promotionalEmails": false, "lowBalanceWarning": false } โ { "ok": true, "preferences": { ...all fields... } }
Saved Contacts (all [auth])
Users can save phone numbers with names for quick reference. When a user says "buy data for Mum" or "send airtime to John", search their saved contacts first. GET /contacts?page=&limit=&search= โ { contacts[], total, page, totalPages } POST /contacts { "name":"Mum", "phoneNumber":"09012345678" } โ { ok, contact } PATCH /contacts/:id { "name":"Mother" } or { "phoneNumber":"..." } or both โ { ok, contact } DELETE /contacts/:id โ { ok, message:"Contact deleted" } GET /contacts/search?name=mum โ { ok, contacts: [{ id, name, phoneNumber }] } (max 5 results) A phone number can only be saved once per user (409 Conflict on duplicate) search param on GET /contacts matches name or phone (partial) GET /contacts/search?name= is a quick lookup โ use it to resolve a name to a phone number
Contact Behaviors
After a successful purchase: if the phone number isn't already saved, suggest saving it: "Would you like to save 0803 123 4567 with a name so you can quickly buy for them next time?" When user refers to a name: search contacts via GET /contacts/search?name=... 1 match โ use that phone number (confirm with user) Multiple matches โ show options, ask which one No match โ ask user for the phone number "Buy for Mum" flow: search contacts โ find phone โ normalize โ predict network โ fetch plans โ confirm โ order
Product Discovery (no auth)
GET /product/networks GET /product/networks/:id/data-plans GET /product/data-plans/:dataId GET /product/education
Key Rules
Always normalize phone before anything โ POST /utils/phone/normalize Always predict network โ POST /utils/phone/predict (don't guess from prefix) Never hardcode network IDs or plan IDs โ fetch fresh every time trx_id must be unique per attempt โ run node pay-bills-skill/generate-order-id.js for each order, never reuse even on failure Check balance before wallet orders โ if insufficient, suggest deposit Confirm with user before submitting โ show plan, price, phone, balance Network status must be up โ don't order on down networks Plan status must be active โ skip disabled plans payment_method wallet is preferred for agent purchases (instant, no redirect) Use GET /transactions/recent-phones for quick re-orders ("buy same as last time") Use GET /contacts/search?name= when user refers to someone by name ("buy for Mum") After a successful purchase, suggest saving the number if it's not already in contacts User's own phone is in GET /user/profile โ phone field
Enums
type: data, airtime payment_method: wallet, online transaction type: deposit, purchase_data, purchase_airtime, giveaway_funding, giveaway_claim plan category: daily, weekly, monthly, yearly
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Scripts1 Docs
- skill.md
- generate-device-id.js
- generate-order-id.js
- session-token.js