ClawHub

UPI Go Live Checklist

v1.0.1

Guide UPI payments launch from setup through sandbox testing to go-live readiness with detailed checklists, test matrix, gates, and rollback planning.

⭐ 0· 104·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
Name/description (UPI go-live checklist) match the included checklists, runbooks, templates, and phase-based workflow; nothing requested (env vars, binaries, installs) is unrelated to that purpose.
✓
Instruction Scope
SKILL.md and companion files confine actions to planning, checklist generation, and local project artifacts (memory.md, evidence). There are no instructions to read unrelated system files, exfiltrate data, call external endpoints, or access secrets other than recommending secure secret storage.
✓
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is written to disk or downloaded by the skill itself.
✓
Credentials
The skill requests no environment variables, credentials, or config paths. It explicitly advises storing credentials in a secure secret manager and not in chat/source control.
✓
Persistence & Privilege
No always:true flag, no privileged persistence or configuration of other skills. The skill is user-invocable and may be called autonomously by agents per platform defaults, which is normal for an instruction skill.
Assessment
This skill provides operational checklists and templates and appears coherent and safe for planning work. Before installing or using it: (1) do not paste real credentials into chat — follow the skill's advice to use a secrets manager; (2) verify provider and regulatory details (RBI/NPCI) are current for your region and update templates accordingly; (3) if you let an agent invoke this skill autonomously, ensure the agent does not have access to production secrets or system credentials it shouldn't use; and (4) treat the guidance as advisory—complete legal/compliance reviews and technical validation with your teams before any production cutover.

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

latestvk978k7t8fcywnt9bdmkvcrm5v9836z2n

License

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

Comments