AC idx-scalper
Use when user needs scalping or day trading analysis for IDX (Bursa Efek Indonesia) stocks. Provides entry points, cut loss levels, and target sell with focus on momentum trading, volume analysis, and short-term timeframes (M5, M15). Requires Stockbit data (OHLC, volume, screenshots) before analysis. Triggered by: scalping requests, day trading analysis, momentum trading questions, or IDX stock entry/exit recommendations.
As a process C 59/100 · Has gaps — weak spots: when it triggers, 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Use when user needs scalping or day trading analysis for IDX (Burs… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 59/100
- 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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 35 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1034 tokens
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)
- +1No license
- +2Single-language instructions
- +3Description length 425: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 35 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.