ClawHub

UPI Payment UX and Ops

v1.0.2

Design and review user and operations messaging, flows, and support templates for UPI payments, mandates, refunds, disputes, and incident communication.

⭐ 0· 137·0 current·0 all-time
byASP@anugotta
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description match the actual content: UX copy, support macros, escalation matrices, and ops playbooks for UPI flows. The skill requests no binaries, environment variables, or installs, which is appropriate for a guidance-only skill.
✓
Instruction Scope
SKILL.md and the included docs only instruct the agent to produce messaging, playbooks, checklists, and to verify provider/RBI guidance. There are no directives to read unrelated local files, access environment variables, call external endpoints, or execute payments — scope is limited to content generation and process guidance.
✓
Install Mechanism
No install spec and no code files are present (instruction-only). This is the lowest-risk model — nothing will be written to disk or downloaded by the skill itself.
✓
Credentials
The skill declares no required environment variables, credentials, or config paths. That aligns with a UX/ops guidance skill which should not need secret access.
✓
Persistence & Privilege
always:false and default invocation settings are used. The skill does not request persistent presence or system-wide configuration changes.
Assessment
This skill appears coherent and safe as a content/ops guidance tool. Before using it in production: (1) verify all regulatory and provider-specific behavior (RBI, NPCI, PSPs) as the docs themselves advise, (2) run generated copy through your legal/compliance and localization reviews, (3) test messaging and playbooks in staging with real webhook/provider behavior to confirm state semantics, and (4) treat this as authoring guidance only — it does not execute payments or replace integration/runbook code. If you expect the skill to integrate with payment APIs or access production data, choose a different integration-specific skill and provide only the minimal credentials required for that purpose.

Like a lobster shell, security has layers — review code before you run it.

latestvk973myqrc8h0wc5swjgwb4539h836prx

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments