AA alphaear-signal-tracker
Use this skill to track the evolution of an existing finance or investment signal when the user provides a prior thesis/signal and asks whether new market information strengthens, weakens, falsifies, realizes, or leaves it unchanged. It should compare baseline logic with updated news, prices, and fundamentals, then output a structured signal update. Use mx-search and mx-data for fresh facts as needed; do not use for simple news lookup, raw data lookup, stock screening, or diagram-only requests.
Use this skill to track the evolution of an existing finance or investment signal when the user provides a prior thesis/signal and asks whether new market…
As a process A 81/100 · Runs to the end — weak spots: running it twice, progress reporting
How to improve
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenscripts/utils/hybrid_search.py:22High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)model_name: 向量模型名称,默认使用 para…-v2
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/utils/hybrid_search.py:34High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)self.model_name = model_name or os.getenv("EMBEDDING_MODEL", "para…-v2")quoted
Files scanned: 36. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 81/100
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 22 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 541 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
- +4No input/output examples
- -32 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 499: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 22 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.