xbridge-ext-helper
v1.0.0帮助开发者在 xbridge3 框架中使用扩展字段（Extension Fields）。当用户需要： - 添加新的扩展字段到交易表 - 创建国家特定的扩展字段（如越南、马来西亚等） - 配置 @EntityColumnSchema 注解 - 使用 ExtensionUtils 读取/设置扩展字段 - 理解索引字段...
⭐ 0· 55·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (xbridge3 extension fields) matches the SKILL.md and the included Java examples (CommonExtension, EntityExtensionSchema, Processor, DAO, ExtensionUtils). No unrelated binaries, env vars, or cloud credentials are requested.
Instruction Scope
SKILL.md provides concrete code examples and step-by-step guidance for defining and persisting extension fields. The instructions only reference project classes, JSON ext_data, and framework APIs; they do not instruct reading arbitrary host files, accessing unrelated env vars, or contacting external endpoints.
Install Mechanism
This is instruction-only (no install spec). Although code files are bundled for examples, there is no download/install step that would write or execute remote artifacts on the host.
Credentials
The skill declares no required environment variables, credentials, or config paths and the SKILL.md does not access any hidden secrets—requested access is proportionate to a developer help guide.
Persistence & Privilege
always is false and the skill does not request persistent system privileges or modify other skills/config. disable-model-invocation is false (normal); there is no evidence of privileged persistent behavior.
Assessment
This skill appears internally consistent and focused on xbridge3 extension-field examples, but note the source/homepage is unknown. Before using in production: (1) review the bundled Java code for licensing and to ensure it matches your project's packages/namespaces, (2) run the examples in a dev/sandbox environment, (3) confirm the idx_str/idx_date/idx_number column allocations match your DB schema and capacity, and (4) search the files for any hard-coded secrets or external endpoints (none were detected by the scanner). If you need higher assurance, ask the publisher for provenance or prefer a skill from a known project/repo.Like a lobster shell, security has layers — review code before you run it.
latestvk970ahs5045kwb64r1b6xxapzn84dxa4
License
MIT-0
Free to use, modify, and redistribute. No attribution required.