RSAD Copilot
v1.0.0Use this skill when working with IBM Rational Software Architect Designer (RSAD/RSA) in the context of IBM FTM (Financial Transaction Manager) development. T...
⭐ 1· 72·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
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the included runtime instructions and reference documents. All content is about RSAD modelling, FSMs, mapping and SQL export; there are no unrelated environment variables, binaries, or external services requested.
Instruction Scope
SKILL.md and the reference files provide detailed, domain-specific instructions for modeling, exporting SQL, and packaging RSAD artifacts. This is within the stated purpose, but the trigger guidance is broad (“When in doubt, trigger this skill”) which may cause frequent or unnecessary invocation if used without stricter eligibility rules. The instructions reference working with .emx/.uml files, exporting SQL, and committing to version control — appropriate for a design copilot but they implicitly assume access to the user's RSAD workspace and VCS artifacts.
Install Mechanism
Instruction-only skill with no install spec, no downloads, and no code files to execute — minimal install risk.
Credentials
The skill declares no required env vars, no credentials, and no config paths. The scope of data it asks the agent to reason about (RSAD models, DB2 SQL exports) is proportional to its purpose. No unexplained SECRET/TOKEN/PASSWORD requirements are present.
Persistence & Privilege
Skill is not always-enabled (always: false) and is user-invocable. It does not request elevated platform privileges or modify other skills. Autonomous invocation is permitted by default but not combined with other red flags.
Assessment
This skill appears coherent for RSAD/FTM design guidance: it is instruction-only, asks for no credentials, and does not install code. Before enabling it for an agent: 1) decide whether you want the broad trigger rule (“when in doubt, trigger this skill”); tighten triggers if you want to avoid noisy/autonomous invocation. 2) Do not grant the agent access to DB2 credentials, enterprise VCS, or RSAD workspaces unless you intend the agent to operate on those artifacts — the skill assumes you will perform exports and commits but does not itself require secrets. 3) Verify the author/source (no homepage provided) if you need provenance/auditability for enterprise use. 4) If you plan to let the agent act on files (exporting SQL, committing .emx/.uml), log and review those actions in your CI/VCS process.Like a lobster shell, security has layers — review code before you run it.
latestvk970j0tenpyeq77zyev54fg1y183ks15
License
MIT-0
Free to use, modify, and redistribute. No attribution required.