AC money-claw-us-stocks
Screen and rank U.S.-listed common stocks, ordinary shares, and ADR/ADS securities for extreme low-float squeeze moves, including potential +500% intraday events. Use for 美股暴涨策略、盘前或盘后涨幅榜筛选、低流通盘/低价股/妖股 squeeze、ELPW/TDIC/SKK/CPOP/RGNT/CPHI/CYCU/FGI/GXAI 类案例、盘前到开盘及停牌复牌执行清单、5分钟量价阶段识别、抛物线加速与放量派发、暴涨因子回测、候选股评分，以及判断盘前、盘中或盘后异动股是否符合暴涨因子。 Evaluate point-in-time price, baseline liquidity, float/share supply, premarket, official-open, and after-hours gaps, turnover, spread, VWAP, earnings/news catalysts, splits, dilution, halts, and data quality. Primary audience: investors and traders in Asia-Pacific countries monitoring U.S. sessions and issuer disclosures. Do not use for long-term valuation or for ETFs, warrants, rights, units, preferred shares, or bonds.
Screen and rank U.S.-listed common stocks, ordinary shares, and ADR/ADS securities for extreme low-float squeeze moves, including potential +500% intraday…
As a process C 63/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: 0. 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: Screen and rank U.S.-listed common stocks, ordinary shares, and AD… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 63/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
- 100Tools and files. No external tools needed
- 100Steps. 56 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2602 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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 755: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 56 items
- +4Has examples (15 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.