AC time-cycles
当用户问时间周期（CRB 10.5 个月、28 天交易周期、季节性）、用"波峰左移/右移"判趋势拐点，或想用 周期窗口择时，并需要"周期须与传统信号验证""熊市少做周期抄底"等约束时激活。 不适用于：数艾略特波浪（转 elliott-wave）、均线趋势跟踪（转 moving-averages）。 关键 trigger 词：周期、季节性、波峰左移右移、28天、10.5个月、时间窗、1月高点、大豆4-7月、天数、上涨下跌天数。 Activate when the user asks about time cycles (CRB 10.5-month, 28-day trading cycle, seasonality), uses "peak left/right shift" to judge turning points, or wants to time with cycle windows, with constraints like "cycles must be confirmed by traditional signals" and "avoid cycle bottom-fishing in bear markets". Not applicable: counting Elliott waves (-> elliott-wave), MA trend-following (-> moving-averages). Key trigger words: cycle, seasonality, peak left/right shift, 28 days, 10.5 months, time window, January high, soybean Apr-Jul, day count, up/down day count.
当用户问时间周期（CRB 10.5 个月、28 天交易周期、季节性）、用"波峰左移/右移"判趋势拐点，或想用 周期窗口择时，并需要"周期须与传统信号验证""熊市少做周期抄底"等约束时激活。 不适用于：数艾略特波浪（转 elliott-wave）、均线趋势跟踪（转 moving-averages）。 关键…
As a process C 59/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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "source_book" - note
frontmatter-keyunknown frontmatter key "source_chapter" - note
frontmatter-keyunknown frontmatter key "related_skills"
Process rating: all ten parameters 59/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
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 46 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 624 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 784: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 46 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.