ClawHub

STX Copilot

v1.0.0

Expert IBM Transformation Extender (WTX/ITX/Sterling TX) development assistant. Invoke this skill whenever the user mentions WTX, ITX, IBM Transformation Ext...

⭐ 1· 94·0 current·0 all-time
byShoaib Khan@shoaibkhan
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
The name/description (ITX/WTX/STX copilot) match the SKILL.md and the included reference material. All commands, env var names, CLI flags, and file types mentioned are relevant to ITX map development, compilation, execution, debugging, and ACE integration — there is no unrelated credential or binary requirement.
ℹ
Instruction Scope
The SKILL.md is instruction-only and stays within the domain of map design, compile/run, Launcher/ACE integration, and debugging. It does include explicit debugging suggestions that may capture full input payloads (e.g., WTX_DUMP_DATA=true, verbose tracing, enabling trace output files) and examples that show adding a Launcher user with a plaintext password in CLI examples — these are operationally sensitive but within the scope of ITX administration rather than out-of-scope data exfiltration or unrelated system access.
✓
Install Mechanism
No install spec or bundled code is present; this is instruction-only so nothing is downloaded or written to disk by the skill itself.
ℹ
Credentials
The skill declares no required env vars or credentials (none in requires.env). The documentation references common ITX environment variables (DTX_HOME_DIR, DTX_TMP_DIR, LD_LIBRARY_PATH) and runtime functions (GETTXINSTALLDIRECTORY, GETFILENAME) which are appropriate for the purpose. Note: enabling debug flags described in the docs can cause sensitive message content to be written to logs; the skill does not request secrets but advises actions that could expose them if performed.
✓
Persistence & Privilege
The skill is not always-enabled, makes no persistent system changes, and has no install-time hooks. Autonomous invocation is allowed (platform default) but is not combined with elevated privileges or cross-skill config changes.
Assessment
This appears to be a coherent, instruction-only ITX/WTX copilot. Before using it: (1) do not blindly copy-and-run the example commands in production — verify paths, versions, and target hosts; (2) avoid enabling verbose trace or WTX_DUMP_DATA in production because those options can log entire message payloads (sensitive payment/PII); (3) if you follow examples that create accounts or set passwords (launcheradmin -adduser ...), replace example credentials with secure ones and follow your org's credential policies; (4) confirm any filesystem paths (/opt/IBM/itx, .mmc/.mar locations) and runtime versions before compiling/deploying maps. If you want deeper assurance, provide the skill author/source or any runtime wrappers that will invoke these commands so I can re-evaluate for hidden or cross-system operations.

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

latestvk970hayce8dcz1kxbn8e2jm3q183jr8m

License

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

Comments