AD ibm-rsad-copilot
Use this skill when working with IBM Rational Software Architect Designer (RSAD/RSA) in the context of IBM FTM (Financial Transaction Manager) development. Trigger when the user mentions: IBM RSA, IBM RSAD, Rational Software Architect, UML modeling in FTM, Service Participant design, Channel design, FSM modeling in RSA, state machine diagrams, UML sequence diagrams for payments, UML use case diagrams, class diagrams, RSA stereotypes, PMP_Alert, PMP_Terminal, PMP_OpsControl, FSM export to SQL, RSA config scripts, RSA workspace, RSA profiles, model-driven development for FTM, design artifacts for FTM, producing FTM design artifacts, RSA transformations, UML to SQL export, FTM design phase, modeling payment flows, designing FTM interfaces, or any RSA/RSAD design-time task in the FTM development workflow. Also trigger when the user is in the DESIGN step of the FTM methodology (Design → Build → Deploy → Operate). When in doubt, trigger this skill.
As a process D 45/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 45/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 7 mutating operations with no state check
- 40Consistency. Frontmatter name (ibm-rsad-copilot) differs from the folder (rsad-copilot)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 23 steps
- 100Execution cost. Instruction body is 1297 tokens
- medium 3 test cases, all positive: not one "should refuse" or "should ask first"
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 956: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Structure: 8 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.