Token导航 LogoToken导航

Agent Skill · 开发

set-up-wso2-open-banking(设置 wso2 开放银行)

set-up-wso2-open-banking 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

set-up-wso2-open-banking 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为接触敏感数据;许可证信息还不明确,第三方扫描有提醒项,按安装量在开发类的 21,746 个 Skill 里排第 20,060。

总安装 242周安装 10GitHub Stars 公开资料未说明下载 79核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:set-up-wso2-open-banking(设置 wso2 开放银行)
来源仓库:https://github.com/vimukthirajapaksha/agent-skills
仓库路径:skills/set-up-wso2-open-banking
安装命令:
npx skills add https://github.com/vimukthirajapaksha/agent-skills --skill set-up-wso2-open-banking
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/vimukthirajapaksha/agent-skills --skill set-up-wso2-open-banking

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

set-up-wso2-open-banking 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理时使用。

它支持按来源仓库、安装命令和原始 README 核验具体用法,适用于开发协作与代码管理场景。通过 npx skills add 命令从指定 GitHub 仓库安装,需确认权限范围和维护状态后再部署。安装前建议检查是否会触发联网、命令执行或文件读写,避免误操作影响系统安全。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/set-up-wso2-open-banking

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/vimukthirajapaksha/agent-skills --skill set-up…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

set-up-wso2-open-banking 怎么安装?

在终端执行 npx skills add https://github.com/vimukthirajapaksha/agent-skills --skill set-up-wso2-open…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

set-up-wso2-open-banking 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

set-up-wso2-open-banking 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

set-up-wso2-open-banking 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

set-up-wso2-open-banking 用的人多吗?

公开数据是累计安装 242 次,近一周安装 10 次,下载 79 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

set-up-wso2-open-banking 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
set-up-wso2-open-banking

设置 wso2 开放银行 · 本页

242—接触敏感数据未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Setting up WSO2 Open Banking

Set up WSO2 Open Banking Accelerator on:

  • WSO2 Identity Server (IS)
  • WSO2 API Manager (APIM) (required for OB3, optional for OB4)
  • Optional WSO2 Streaming Integrator (SI) (OB3 data publishing only)

Rules:

  • Collect all inputs first.
  • Run steps in order.
  • Stop on first failed check/command.
  • Use skip logic for optional components.
  • Use idempotent checks before destructive actions.

Guardrails

  • Confirm before destructive actions (scripts, keystores/truststores, overwriting configs).
  • Do not ask the user to paste secrets.
  • Change only the files listed in this workflow.
  • Run commands one by one (do not combine all commands into one script).

Execution contract

  1. Do not execute any command until all required non-secret inputs are collected.
  2. During input collection, ask one question at a time.
  3. For secret values, require environment variables only (never ask to paste raw secrets).
  4. When a pre-check fails, stop immediately and report the exact failed check.
  5. For optional components (APIM/SI), skip all related steps explicitly and log the skip reason.
  6. Always print resolved paths before running commands there.

Input contract (collect first)

If missing, use defaults.

  • OB_VERSION: OB3 or OB4 (default: OB4)

Version-specific inputs

Host inputs

  • IS_HOST: default https://localhost:9446
  • APIM_HOST: default https://localhost:9443 (required only when APIM is selected)
  • SI_HOST: default https://localhost:9444 (required only when SI is selected)

Database host inputs

  • DB_HOST: default localhost
  • DB_PORT: default 3306

Workspace input

  • WORK_DIR: absolute path used to create the setup directory (default: $pwd)

Primary workflow (do not reorder)

1. Prerequisites

  • Run preflight checks:
java -version
command -v mysql
command -v curl
command -v keytool
command -v unzip
  • Stop if any required tools are missing.

2. Install accelerators into base products

  • Create <WORK_DIR>/wso2-open-banking-accelerator and cd into it.
  • Resolve and record canonical paths after extraction:

- <IS_HOME> - <APIM_HOME> (if IS+APIM) - <SI_HOME> (if OB3 data publishing requested) - <OB_IAM_ACCELERATOR_HOME> inside <IS_HOME> - <OB_AM_ACCELERATOR_HOME> inside <APIM_HOME> (if IS+APIM) - <OB_SI_ACCELERATOR_HOME> inside <SI_HOME> (if OB3 data publishing)

  • A zip source is a URL if it starts with https://; otherwise treat it as a local path. Download only for URLs.
  • Extract base product zips into the current directory.
  • Unzip accelerators into corresponding base product directories.
  • Path resolution rule:

- <IS_HOME>: extracted dir name starts with wso2is- and contains bin. - <APIM_HOME>: extracted dir name starts with wso2am- and contains bin. - <SI_HOME>: extracted dir name starts with wso2si- and contains bin. - <OB_IAM_ACCELERATOR_HOME>: dir under <IS_HOME> containing repository/conf/configure.properties. - <OB_AM_ACCELERATOR_HOME>: dir under <APIM_HOME> containing repository/conf/configure.properties. - <OB_SI_ACCELERATOR_HOME>: dir under <SI_HOME> containing repository/conf/configure.properties.

  • Verify path existence before continuing:

- <IS_HOME>/bin - <OB_IAM_ACCELERATOR_HOME>/bin - <APIM_HOME>/bin and <OB_AM_ACCELERATOR_HOME>/bin only if IS+APIM

  • Version-specific branch:

- If OB3, run set up IS connector. - If OB3 data publishing requested, run set up data publishing.

3. Update base products and accelerators

  • Select relevant update binary by OS:

- macOS: wso2update_darwin - Linux: wso2update_linux - Windows: wso2update_windows.exe

  • Verify the OS-specific update tool exists in each directory below.

- <IS_HOME>/bin - <OB_IAM_ACCELERATOR_HOME>/bin - <APIM_HOME>/bin (if IS+APIM) - <OB_AM_ACCELERATOR_HOME>/bin (if IS+APIM) - <SI_HOME>/bin (if OB3 data publishing) - <OB_SI_ACCELERATOR_HOME>/bin (if OB3 data publishing)

  • If missing, stop and tell the user their WSO2 subscription is likely missing. Ask them to contact WSO2 Online Support System to download the product or skip updates.
  • Verify the required environment variables for the update tool are set. Stop if missing:
test -n "$OB_AGENT_UPDATE_TOOL_USERNAME"
test -n "$OB_AGENT_UPDATE_TOOL_PASSWORD"
  • Run the update tool in each directory:
./<WSO2UPDATE_BINARY> --username "$OB_AGENT_UPDATE_TOOL_USERNAME" --password "$OB_AGENT_UPDATE_TOOL_PASSWORD"

4. Configure MySQL database

  • Verify MySQL >= 8.0 available, stop if not.
  • Verify DB credentials are provided via environment variables. Stop if missing:
test -n "$OB_AGENT_DATABASE_USERNAME"
test -n "$OB_AGENT_DATABASE_PASSWORD"
  • Verify DB credentials by connecting to the DB. Stop if invalid.

MySQL check example:

MYSQL_PWD="$OB_AGENT_DATABASE_PASSWORD" mysql -h "$DB_HOST" -P "$DB_PORT" -u "$OB_AGENT_DATABASE_USERNAME" -e "SELECT 1;"
  • Download compatible JDBC driver (MySQL 8 example):
curl -L "https://repo1.maven.org/maven2/com/mysql/mysql-connector-j/9.6.0/mysql-connector-j-9.6.0.jar" -o mysql-connector-j-9.6.0.jar
  • Place the JDBC driver JAR:

- IS: copy the driver JAR into <IS_HOME>/repository/components/lib - APIM: copy the driver JAR into <APIM_HOME>/repository/components/lib - SI: copy the driver JAR into <SI_HOME>/lib (if OB3 data publishing requires DB connectivity there)

  • Set and verify DB_USER and DB_PASS in <OB_IAM_ACCELERATOR_HOME>/repository/conf/configure.properties match the environment variables. Do not print the values, report only MATCH or MISMATCH per property. Stop on any MISMATCH: grep -q "^DB_USER=$OB_AGENT_DATABASE_USERNAME$" repository/conf/configure.properties && echo "DB_USER: MATCH" || echo "DB_USER: MISMATCH"
Note: Use Select-String on Windows.
  • Update the following in <OB_IAM_ACCELERATOR_HOME>/repository/conf/configure.properties:

- DB connection properties - Change DB name pattern from current value to <DATE_PREFIX>_* - Hostnames for IS/APIM/SI - IS_PRODUCT=wso2is-<IS_VERSION> - PRODUCT_CONF_PATH=repository/resources/wso2is-<IS_VERSION>-deployment.toml

<DATE_PREFIX> uses today's date in YYYYMMDD.

  • Run IAM Accelerator scripts:
cd <OB_IAM_ACCELERATOR_HOME>/bin
./merge.sh
./configure.sh
  • If IS+APIM, repeat equivalent configuration + scripts in:

- <OB_AM_ACCELERATOR_HOME>/repository/conf/configure.properties - <OB_AM_ACCELERATOR_HOME>/bin (merge.sh, configure.sh)

  • If OB3 data publishing is requested, repeat equivalent configuration + scripts in:

- <OB_SI_ACCELERATOR_HOME>/repository/conf/configure.properties - <OB_SI_ACCELERATOR_HOME>/bin (merge.sh, configure.sh)

  • Create event-notification tables (OB4 only):

- Check if target tables already exist; skip if present. - Run mysql.sql from <IS_HOME>/dbscripts/financial-services/event-notifications against the consent DB. - Default consent DB name: <DATE_PREFIX>_*consentdb

5. Exchange Certificates

6. Start servers and verify basic health

Start order:

  1. IS: run the OS-specific startup script in <IS_HOME>/bin
./wso2server.(sh|bat) start
  1. APIM (optional): run the OS-specific startup script in <APIM_HOME>/bin
./api-manager.(sh|bat) start
  1. SI (optional): run the OS-specific startup script in <SI_HOME>/bin
./server.(sh|bat) start

Verification checklist:

  • IS, APIM, and SI hosts and ports are reachable
  • No critical errors in selected components logs:

- <IS_HOME>/repository/logs/wso2carbon.log - <APIM_HOME>/repository/logs/wso2carbon.log (if APIM selected) - <SI_HOME>/wso2/server/logs/carbon.log (if SI selected)

Completion criteria (must satisfy all applicable)

  • All selected components start successfully.
  • Health/port checks pass for selected components only.
  • No startup-blocking or critical errors in logs after 30 seconds (e.g., ERROR|FATAL).
  • Accelerator configs and DB scripts are applied for selected components.
  • Certificate exchange is complete for selected components.

Failure handling

  • On any failed command:

1. Stop immediately. 2. Report the exact command, exit code, and path. 3. Do not continue until user confirms remediation.

平台分布

Codex

36.07%
按下载量换算28

Claude

32.7%
按下载量换算26

Cursor

17.4%
按下载量换算14

Gemini CLI

9.12%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills