CtrlK
BlogDocsLog inGet started
Tessl Logo

morning-note

Draft concise morning meeting notes summarizing overnight developments, trade ideas, and key events for coverage stocks. Designed for the 7am morning meeting format — tight, opinionated, actionable. Triggers on "morning note", "morning meeting", "what happened overnight", "trade idea", "morning call prep", or "daily note".

71

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is morning-note in anthropics/financial-services

SKILL.md
Quality
Evals
Security

Quality

Content

90%Weight 40%Scale 1-5

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

Lean and highly actionable: the body delivers a copy-paste note template, an earnings quick-take table, and sharp house-style rules with no filler. The workflow is clearly sequenced with sensible edge-case guidance, but lacks any final validation checkpoint before distribution, and at ~85 lines it sits just above the size where single-file organization alone earns full progressive-disclosure credit.

Suggestions

Add a final validation step to the workflow (e.g., 'Before sending: confirm the note fits on 1 page and leads with the Top Call') to strengthen workflow_clarity.

Include one filled-in example note (or move the blank template to an examples file) to anchor format expectations and tighten the main file.

DimensionReasoningScore

Conciseness

Lean bullets and templates with zero padding — no explanation of concepts Claude already knows, and every line carries house-style judgment it would not have ("Be opinionated — morning notes that just summarize news without a view are useless", "'No news' is a valid morning note"). Matches the 5 anchor: every token earns its place.

5 / 5

Actionability

The skill provides a fill-in-ready note template with exact structure, an earnings quick-take table (Metric/Consensus/Actual/Beat-Miss), output formats, and edge-case handling (no-news notes, time-stamping, owning bad calls). Instruction-only but fully concrete and copy-paste ready — matches the 5 anchor for non-code skills.

5 / 5

Workflow Clarity

A clear four-step sequence (scan → format → earnings quick take → output) with a conditional branch ("If a coverage company reported") and an explicit length constraint ("Keep to 1 page max"). Not 5 because there is no final validation checkpoint (e.g., verify the note fits one page and leads with the top call before distribution); not 3 because the sequence is complete and coherent — this is not a destructive or batch operation, so the validation cap does not apply.

4 / 5

Progressive Disclosure

Well-organized single-file skill with clear section headers and no external references needed — nothing in the body obviously belongs in a separate file. Held at 4 rather than 5 because the body (~85 lines) exceeds the under-50-line case where organization alone earns top marks, and the inline full note template plus earnings table are borderline candidates for a separate example file.

4 / 5

Total

18

/

20

Passed

Description

83%Weight 40%Scale 1-5

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 description that clearly and explicitly states both what the skill does and when to use it, in third person with natural trigger phrases. Trigger coverage is good but misses a few natural variants, and the generic triggers 'trade idea' and 'daily note' carry minor conflict risk with adjacent skills.

DimensionReasoningScore

Specificity

"Draft concise morning meeting notes summarizing overnight developments, trade ideas, and key events for coverage stocks" names the domain and several concrete actions in third-person voice. It falls short of the 5 anchor's comprehensive action coverage (no mention of earnings analysis or the note format itself), but exceeds the 1-2 actions of the 3 anchor.

4 / 5

Completeness

Both questions are explicitly answered: a clear "what" ("Draft concise morning meeting notes summarizing overnight developments, trade ideas, and key events for coverage stocks") and an explicit "when" with concrete trigger phrases ("Triggers on 'morning note', 'morning meeting', ..."). This matches the top anchor exactly.

5 / 5

Trigger Term Quality

Explicit natural triggers — "morning note", "morning meeting", "what happened overnight", "trade idea", "morning call prep", "daily note" — are phrases users would actually say, including synonyms. Not 5 because common variants like "morning call" itself or "overnight recap" are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche — sell-side morning meeting notes for coverage stocks — with distinct triggers. Minor overlap risk remains: "trade idea" and "daily note" could fire on standalone trade-idea or daily-summary requests that are not morning notes.

4 / 5

Total

17

/

20

Passed

Validation

100%

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
anthropics/financial-services
Reviewed

Table of Contents

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.