CtrlK
BlogDocsLog inGet started
Tessl Logo

idea-generation

Systematic stock screening and investment idea sourcing. Combines quantitative screens, thematic research, and pattern recognition to surface new long and short ideas. Use when looking for new ideas, running screens, or conducting thematic sweeps. Triggers on "idea generation", "stock screen", "find ideas", "what looks interesting", "screen for", "new ideas", or "pitch me something".

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is idea-generation in anthropics/financial-services

SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

The content is a lean, well-structured, practitioner-grade screening playbook: concrete thresholds, clear five-step sequencing, and a ready-to-use idea presentation template. Its main gaps are the unspecified execution mechanism for running screens or thematic sweeps and the absence of explicit validation checkpoints before presenting ideas.

Suggestions

Specify how to execute the screens — the data source or tool to use for fundamentals (e.g., a specific data feed, web-search procedure, or a scripts/ helper) — so 'Run screens based on the style' is directly executable rather than left to inference.

Add an explicit validation checkpoint between screening and presentation (e.g., sanity-check that metrics reconcile across sources and flag stale or missing data before writing the idea summary), which the 'Screens surface candidates, not conclusions' note implies but never operationalizes.

Consider moving the per-style screen criteria (Value/Growth/Quality/Short/Special Situation) into a references/ file (e.g., screens.md) referenced from Step 2, keeping SKILL.md focused on the workflow and presentation format.

DimensionReasoningScore

Conciseness

The ~115-line body is dense with information Claude does not already know — concrete thresholds ("Free cash flow yield >5%", "ROIC >15%", "Strong net retention (>110% for SaaS)") and practitioner judgment ("Contrarian ideas need a catalyst — being early without a catalyst is the same as being wrong") — with no padding or explanation of known concepts. Every token earns its place.

5 / 5

Actionability

Screen criteria are fully concrete ("P/E below sector median", "Rising receivables / inventory vs. sales") and the idea-presentation template is copy-ready (metric table with "EV/EBITDA (NTM)", "P/E (NTM)", "FCF yield"). However, "Run screens based on the style" and "research the theme" never specify the execution mechanism — no tool, data source, or command — leaving a minor gap that keeps it below fully executable.

4 / 5

Workflow Clarity

A clear five-step sequence (Define Search Criteria → Quantitative Screens → Thematic Sweep → Idea Presentation → Output) with a well-defined output artifact ("Shortlist of 5-10 ideas... Prioritized list"). Validation is only implied by the caution "Screens surface candidates, not conclusions" — no explicit checkpoint or sanity-check step, so it fits 'clear sequence with most checkpoints present; minor validation gaps' rather than the full-checkpoint anchor.

4 / 5

Progressive Disclosure

A single self-contained file with well-organized sections (per-style screens, workflow steps, Important Notes) and no bundle files. Good structure for its size, though the ~40 lines of per-style screen criteria (Value/Growth/Quality/Short/Special Situation) could arguably be split into a references/ file, and the under-50-line simple-skill exception does not strictly apply.

4 / 5

Total

17

/

20

Passed

Description

100%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: third-person voice, specific concrete capabilities, an explicit 'Use when...' clause, and a rich set of natural trigger phrases with synonyms. It matches the rubric's good examples closely with no identifiable weaknesses.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — "quantitative screens, thematic research, and pattern recognition to surface new long and short ideas" — under a clearly named domain ("Systematic stock screening and investment idea sourcing"), giving comprehensive coverage comparable to the anchor-5 example "Extract text and tables from PDF files, fill forms, merge documents".

5 / 5

Completeness

It explicitly answers both questions: the "what" ("Combines quantitative screens, thematic research, and pattern recognition to surface new long and short ideas") and a concrete "when" ("Use when looking for new ideas, running screens, or conducting thematic sweeps"), mirroring the anchor-5 example structure almost verbatim.

5 / 5

Trigger Term Quality

Seven natural trigger phrases users would actually say are quoted: "idea generation", "stock screen", "find ideas", "what looks interesting", "screen for", "new ideas", "pitch me something" — including synonym variations, matching the comprehensive natural-terms anchor.

5 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (investment idea sourcing) with domain-specific triggers ("stock screen", "pitch me something") that adjacent skills (e.g., financial modeling or due-diligence skills) would not fire on, keeping conflict risk minimal.

5 / 5

Total

20

/

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.