release-packet

Validate ISO 20022 payment data against OFAC sanctions and prepare approval packets.

86|42|Updated May 6, 2026
One-click install
npx skills add https://github.com/NVIDIA/nemoclaw-community --skill release-packet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-packet
Source: https://github.com/NVIDIA/nemoclaw-community/tree/main/examples/recipes/nvidia/payment-ops-hermes/skills/release-packet
Command: npx skills add https://github.com/NVIDIA/nemoclaw-community --skill release-packet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the challenge of maintaining strict maker-checker compliance in payment workflows by ensuring that no payment can be released without explicit human intervention.

Core Features & Use Cases

  • Automated Screening: Re-validates payments against ISO 20022 standards and OFAC sanctions lists before preparation.
  • Compliance Guardrails: Enforces a maker-checker model by preventing unauthorized egress to payment rails and marking packets as pending for human approval.
  • Use Case: A financial operator needs to prepare a wire transfer for review; this skill verifies the payment status and generates a secure packet that requires a separate human action to finalize.

Quick Start

Use the release-packet skill to prepare a release packet for payment WIRE-1007 by providing the required queue and sanctions data files.

Frequently Asked Questions about release-packet

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare payment packets for human approval while ensuring OFAC sanctions compliance?

To prepare payment packets for human approval, you validate ISO 20022 data against OFAC sanctions lists and generate a secure packet marked as pending, enforcing maker-checker separation of duties.

What is maker-checker separation of duties in payment screening workflows?

Maker-checker separation of duties in payment screening prevents unauthorized egress to payment rails by requiring a separate human action to finalize any screened financial transaction before release.

Can I validate ISO 20022 payment data against OFAC sanctions lists automatically before release?

Yes, you can automatically re-validate ISO 20022 payment data against OFAC sanctions lists before preparing the release packet, ensuring no non-compliant transactions reach the payment rails.

Do I need Python 3 and local JSON files to prepare screened payment packets?

Yes, preparing screened payment packets requires Python 3 along with access to local payment queue and sanctions fixture JSON files to operate within the restricted sandbox environment.

Does payment screening for ISO 20022 transfers prevent automated egress to payment rails?

Yes, payment screening for ISO 20022 transfers operates within restricted sandbox environments to prevent unauthorized automated egress, marking packets as pending until a human explicitly approves the release.