alphaear-signal-tracker

Track finance investment signal evolution and update logic based on new finance market information. Use when monitoring finance signals and determining if they are strengthened, weakened, or falsified.

Quality

51%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/alphaear-signal-tracker/SKILL.md

Quality

Content

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body sketches a recognizable three-step workflow and points to a real prompts reference, but its actionability is weak: the sole code block is a deferring comment, referenced symbols ('track_signal', '_sanitize_signal_output') are misnamed or absent, and there are no validation checkpoints for the state-updating operation.

Suggestions

Replace the placeholder code block with an executable example or a precise function call (e.g. show how to invoke FinUtils.sanitize_signal_output with the correct signature).

Fix the broken references: the helper is named 'sanitize_signal_output' (not '_sanitize_signal_output') and there is no 'track_signal' method, so point readers to the real Signal Tracking prompt and the actual schema in scripts/schema/models.py.

Add an explicit validation step to the Track workflow (e.g. verify the updated InvestmentSignal against the schema and confirm the evolution state is one of Strengthened/Weakened/Falsified/Unchanged before writing it back), and remove the duplicated 'Track Signal Evolution' heading and the 'future refactor' meta-commentary.

Dimension	Reasoning	Score
Conciseness	The body is short and mostly efficient, but it pads with redundant labels (the duplicated '### 1. Track Signal Evolution' heading) and meta-commentary ('This skill is currently a pattern extracted from FinAgent', 'In a future refactor...') that add tokens without guidance.	2 / 3
Actionability	The only code block is a non-executable comment that defers to an implementation elsewhere, and the referenced helper '_sanitize_signal_output' does not exist by that name (the actual method is 'sanitize_signal_output'); guidance is descriptive rather than executable.	1 / 3
Workflow Clarity	A research→analyze→track sequence is listed with prompts named per step, but there are no validation checkpoints or feedback loops despite signal-updating being a state-mutating operation, which caps clarity at 2.	2 / 3
Progressive Disclosure	Content is split into a one-level-deep references file (PROMPTS.md) and a scripts bundle that are signaled, but the body misnames the reference path ('references/PROMPTS.md' is real while the in-text code comment points to 'scripts/fin_agent.py' 'track_signal' which does not exist), so navigation is present but unreliable.	2 / 3
	Total	7 / 12 Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has an explicit 'Use when...' trigger and a clear domain, satisfying completeness, but its actions are abstract rather than concrete and its trigger vocabulary is narrow. It is a solid, slightly generic trigger that could be sharpened.

Suggestions

Replace abstract verbs with concrete actions, e.g. 'Track and update investment signals by comparing new market news/price data against an existing signal thesis, then re-score confidence and mark it Strengthened, Weakened, Falsified, or Unchanged.'

Broaden trigger terms to cover natural user phrasings such as 'investment signals', 'signal monitoring', 're-evaluate a trade thesis', or 'has my signal changed'.

Differentiate the skill more sharply from general finance-analysis skills by naming the signal-evolution states and the update mechanism explicitly.

Dimension	Reasoning	Score
Specificity	It names the domain ('finance investment signal evolution') and actions ('track...and update logic'), but the verbs are abstract rather than a list of multiple concrete actions like the level-3 anchor requires.	2 / 3
Completeness	It explicitly answers both what ('Track finance investment signal evolution and update logic') and when ('Use when monitoring finance signals and determining if they are strengthened, weakened, or falsified') with an explicit trigger clause.	3 / 3
Trigger Term Quality	It includes relevant natural phrases ('monitoring finance signals', 'strengthened, weakened, or falsified'), but the trigger vocabulary is narrow and lacks common user variations, leaning on the same 'finance signal' term throughout.	2 / 3
Distinctiveness Conflict Risk	The finance-investment-signal niche is fairly specific, but the description could still overlap with general finance-analysis or research skills and the triggers are not sharply distinct from sibling skills.	2 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: RKiding/Awesome-finance-skills
Path: skills/alphaear-signal-tracker/SKILL.md
Commit: 853f09b

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.