BD Market Structure Algorithm
Rule-based trading algorithm using Ichimoku (1H bias), Bollinger Bands, MACD, RSI(14) + 14-period smoothed MA, Fib ratios, EMA Ribbon (5,8,13,21,50), and Linear Regression. Calculates confluence score (0-7) and generates clear signals. Supports all markets. No BOS, CHOCH, SMC, ICT. Analysis only — no automatic execution.
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 2. 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: Implicit map keys need to be followed by map values at line 5, column 1: triggers: ["market structure scan", "scan market", "mss", "mss BTC", "scan ETH"… thinking=low ^^^^^^^^^^^^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "triggers"
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (Market Structure Algorithm) differs from the folder (market-structure-scan)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 85Steps. 23 steps, 1 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 759 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)
- +4Structure: 0 headings, hard to scan
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 322: enough signal without eating the budget
- +3Step-by-step instructions: 23 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 48.