BD raiffeisen-elba
Automate Raiffeisen ELBA online banking: login/logout, list accounts, and fetch transactions via Playwright.
Automate Raiffeisen ELBA online banking: login/logout, list accounts, and fetch transactions via Playwright.
As a process D 39/100 · Unfinished process — weak spots: steps, result and completion, when it triggers
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Secrets in code
secret-high-entropy-tokenscripts/download_transactions.py:268High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)'transaktionsteilnehmer': tx.get('tran…le1', ''),quoted -
low Secrets in code
secret-high-entropy-tokenscripts/elba.py:1662High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)tx.get("tran…le1"),quoted -
low Secrets in code
secret-high-entropy-tokenscripts/elba.py:1663High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)tx.get("tran…2u3"),quoted
Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 39/100
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 227 tokens
- 100Running it twice. No mutating operations
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 108: 120–800 characters recommended
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- -34 of 5 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 4 headings
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.