AC stx-copilot
Expert IBM Transformation Extender (WTX/ITX/Sterling TX) development assistant. Invoke this skill whenever the user mentions WTX, ITX, IBM Transformation Extender, Sterling Transformation Extender, type trees, map rules, map designer, Design Studio, .mtt files, .mms files, .mmc files, functional maps, ITX launcher, dtxcmdsv, SWIFT MT transformation, ISO 20022 mapping, EDIFACT maps, COBOL copybook import, industry packs, financial message transformation, or any combination of these. Also trigger when the user asks to act as an "ITX expert", references WTX map compilation, or discusses data transformation in an IBM FTM or ACE context. When in doubt, trigger — ITX developers always benefit from this context.
As a process C 51/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- 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: 9. 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 51/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
- 30Running it twice. 9 mutating operations with no state check
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 23 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1685 tokens
- 100Progress reporting. Reports progress
- low 13 top-level sections: this looks like several domains in one skill
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)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 714: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (7 of 7)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.