Introduction

When integrating the Institutional VA (Virtual Account) API in Allinpay’s cross-border system, the common workload lies not merely in “calling an HTTP interface,” but in translating the fields, signatures, and asynchronous notifications from the official documentation into code item by item: DTOs must align with the documentation, request/response models must be paired, notification callbacks require handlers, and integration tests must target the real environment rather than a Mock client. Manual implementation is often repetitive and prone to missing field comments or inconsistencies with signature specifications.

The following introduces the community Skill on SkillHub: “Allinpay Cross-border System Institutional VA API Integration SKILL” (Location: @user_87ac9f03/gcp-api-organcus-business-model-generator, current version v1.0.1). Based on the Allinpay Institutional VA interface documentation specifications and targeting GCP Institutional VA API integration scenarios, it allows an Agent to generate structured code and test skeletons according to the guidance in SKILL.md.

What is this

One-sentence positioning: Based on the Allinpay Institutional VA interface documentation, it automatically generates a model layer with Chinese field comments, business services, notification handling, and real HTTP integration tests for GCP Institutional VA API integration, reusing the gcp-api-quick-integration component for signature logic.

  • Source & Origin: Published on the SkillHub community by user_87ac9f03, categorized under dev-programming, tagged with requires_api_key=false (The Skill itself does not require an API Key, but actual joint debugging still requires you to configure credentials on the Allinpay/GCP side).
  • Problem Solved: Delegates repetitive documentation-driven modeling, service separation, and integration testing setup to an Agent to produce results following unified specifications, reducing the cost of manually typing DTOs and signatures against PDFs/interface specifications.

Official Page: SkillHub - Allinpay Cross-border System Institutional VA API Integration SKILL
API Entry: https://api.skillhub.cn/user_87ac9f03/gcp-api-organcus-business-model-generator

Core Features

The following capabilities are derived from the SkillHub page and fetched summary, without additional expansion:

  1. DTO & Models: Generates DTOs with per-field Chinese comments, as well as corresponding request/response models.
  2. Business Layer: Generates business service (Service) code skeletons to facilitate orchestrating call flows according to interface documentation.
  3. Notification Handling: Generates notification (callback) handlers, covering the common asynchronous notification integration needs of the Institutional VA.
  4. Integration Tests: Generates real HTTP integration tests, explicitly avoiding the use of Mock HTTP clients, to facilitate direct verification of signature paths and connectivity when a test environment is available.
  5. Signature Reuse: Signature logic does not reinvent the wheel; it reuses the gcp-api-quick-integration component to maintain consistency with the GCP rapid integration system.

Installation & Activation

The Skill follows the general SKILL.md format. SkillHub CLI must be present on the local machine before installation; if not, please check or install the CLI according to the official installation documentation first.

1. Check CLI

command -v skillhub && skillhub --version

If not installed, you can use the official script to install it (full installation or --cli-only for CLI only) via SkillHub Installation & Priority Source Configuration.

2. Install this Skill

When installing, you must use --dir to point to the current Agent’s skills directory; otherwise, it defaults to ./skills/ and may not be recognized.

skillhub install @user_87ac9f03/gcp-api-organcus-business-model-generator --dir <Your Agent skills directory>

Common skills directories (excerpted from official installation docs):

  • Cursor: ~/.cursor/skills/
  • Claude Code: ~/.claude/skills/
  • Codex: ~/.codex/skills/ or .agents/skills/ under the project

3. Install via Agent Dialogue (Consistent with page prompts)

If you prefer driving the Agent via natural language, you can send the prompt provided by the SkillHub page to the AI:

Please install `@user_87ac9f03/gcp-api-organcus-business-model-generator` based on https://skillhub.cn/install/skillhub.md.

After installing via the steps above, enable the Skill in the corresponding Agent and initiate the integration task.

Typical Usage

The official materials do not include a complete end-to-end code repository example, but the reproducible usage is as follows:

  1. In the Agent where the Skill is installed, explain that you intend to integrate the GCP Institutional VA API and attach the scope of the Allinpay Institutional VA interface documentation you have (e.g., opening, querying, notification interfaces to be implemented).
  2. Clearly request output according to the Skill conventions: DTOs (with per-field Chinese comments), request/response models, business services, notification handlers, and real HTTP integration tests (no Mock HTTP clients).
  3. Confirm that the signature path in the generated code uses gcp-api-quick-integration to align with existing GCP integration components; then configure the real base URL and keys in the test environment to run the integration tests.

Through these steps, you obtain a compilable and debuggable project skeleton. Specific environment variables, merchant IDs, certificates, etc., must be configured by yourself according to the official Allinpay and GCP documentation. The Skill does not replace compliance review or production change processes.

Scenarios & Notes

Who is it for

  • Backend or full-stack developers currently working on joint debugging of the Allinpay cross-border Institutional VA and GCP side APIs.
  • Teams already using or planning to use gcp-api-quick-integration for signatures and rapid integration, hoping to maintain consistency with the VA module.
  • Teams wanting integration tests to hit HTTP directly, rather than achieving “fake green” with Mock clients.

Limitations & Notes

  • The source is community-driven; maintenance rhythm needs to be aligned with official Allinpay documentation updates yourself. After interface changes, you should have the Agent incrementally adjust the generated artifacts based on the new documentation.
  • The Skill tag requires_api_key=false only means the Skill installation itself does not require a Key; joint debugging and integration testing still require real credentials and network reachability in your target environment.
  • The quality of generated code depends on the clarity of the documentation fragments and constraints you provide; manual Code Review is recommended for sensitive fields, idempotency, and notification signature verification.
  • SkillHub Statistics (as of page fetch): Rating 100000, Downloads ~737, Installs ~1—For popularity reference only, not representing official endorsement by Allinpay.

Conclusion

If your pain point is the repetitive setup of DTOs, services, notifications, and integration testing in Institutional VA integration, this Skill binds Allinpay documentation standards with GCP signature components, using an Agent to pull out the skeleton in one go via SKILL.md. See the SkillHub official page for installation and details: https://www.skillhub.cn/skills/user_87ac9f03/gcp-api-organcus-business-model-generator.