alphaear-reporter

Plan, write, and edit professional financial reports; generate finance chart configurations. Use when condensing finance analysis into a structured output.

Quality

71%

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-reporter/SKILL.md

Quality

Content

57%

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

A lean, well-structured skill that correctly delegates detailed prompts to a one-level-deep reference and names the relevant script. Its weaknesses are a duplicated section header plus a restated overview, and a workflow that lacks validation/feedback checkpoints or an executable example for the visualizer.

Suggestions

Remove the duplicate '## Capabilities' header and trim the Overview so it does not restate the frontmatter description verbatim.

Add a brief validation/assembly-check step to the workflow (e.g. verify H2/H3 hierarchy and that every cluster has a section) so the multi-step process has an explicit checkpoint.

Include a one-line executable example for scripts/visualizer.py (e.g. expected input/CLI usage or a sample json-chart invocation) to make the visualization guidance copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is short and does not over-explain concepts, but the Overview nearly restates the frontmatter description ('planning, writing, editing, and creating visual aids') and the '## Capabilities' header is duplicated, so it could be tightened; not level 3 because of this redundancy, not level 1 because it is not padded with concepts Claude already knows.	2 / 3
Actionability	It points to named prompts ('Cluster Signals Prompt', 'Write Section Prompt', 'Final Assembly Prompt') and 'scripts/visualizer.py', which is concrete direction, but provides no executable command or example invocation of the visualizer, leaving key details incomplete; not level 3 because nothing is copy-paste ready, not level 1 because it does name specific artifacts.	2 / 3
Workflow Clarity	A clear 3-step sequence (Cluster Signals -> Write Sections -> Assemble) is present, but there are no validation or verification checkpoints for this multi-step generation workflow, which per the guidelines caps workflow clarity at 2; not level 3 because checkpoints are missing, not level 1 because the sequence is explicit.	2 / 3
Progressive Disclosure	The overview points one level deep to real, well-signaled bundle files ('references/PROMPTS.md' and 'scripts/visualizer.py', both verified to exist) with content appropriately split out, matching the level-3 anchor; not level 2 because references are clearly signaled rather than buried or inline.	3 / 3
	Total	9 / 12 Passed

Description

85%

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

A strong, third-person description with concrete actions and an explicit 'Use when...' trigger. Its main weakness is trigger-term breadth: it covers finance-reporting vocabulary but omits several natural phrasings a user would say.

Suggestions

Broaden trigger terms to include natural user phrasings such as 'financial analysis', 'summarize finance signals', or 'write a finance report'.

Consider mentioning the input shape (e.g. 'from finance signals/analysis') so the trigger more precisely signals when this skill applies.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Plan, write, and edit professional financial reports; generate finance chart configurations' — matching the anchor for several specific concrete actions rather than the level-2 single-domain example.	3 / 3
Completeness	Explicitly answers both what ('Plan, write, and edit...generate finance chart configurations') and when ('Use when condensing finance analysis into a structured output'), matching the level-3 anchor with an explicit trigger clause; not level 2 because the 'when' is explicit rather than implied.	3 / 3
Trigger Term Quality	Includes relevant terms like 'financial reports', 'finance chart configurations', and 'finance analysis', but misses common natural variations a user might say (e.g. 'summarize', 'financial analysis', 'report'), so it is not the comprehensive level-3 coverage.	2 / 3
Distinctiveness Conflict Risk	The finance-reporting niche ('professional financial reports', 'finance chart configurations') is distinct and unlikely to fire for unrelated skills, matching the clear-niche level-3 anchor; not level 2 because the domain and trigger are specific rather than broadly overlapping.	3 / 3
	Total	11 / 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-reporter/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.