CtrlK
BlogDocsLog inGet started
Tessl Logo

initiating-coverage

Create institutional-quality equity research initiation reports through a 5-task workflow. Tasks must be executed individually with verified prerequisites - (1) company research, (2) financial modeling, (3) valuation analysis, (4) chart generation, (5) final report assembly. Each task produces specific deliverables (markdown docs, Excel models, charts, or DOCX reports). Tasks 3-5 have dependencies on earlier tasks.

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/vertical-plugins/equity-research/skills/initiating-coverage/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The content is highly actionable with excellent workflow sequencing, validation checkpoints, and a sound progressive-disclosure structure that delegates detailed workflows to real reference files. Its main weakness is verbosity: the single-task-mode and no-shortcuts/deliverables rules are repeated many times across sections.

Suggestions

Consolidate the 'one task at a time / never chain tasks' rule into a single authoritative section and remove its restatements from 'How to Use', 'Task Execution Order', 'No End-to-End Execution', and 'Important Notes'.

Factor the repeated per-task '⚠️ DELIVER ONLY... NO completion summaries' and 'DO NOT TAKE SHORTCUTS' blocks into one shared 'Deliverables Policy' section referenced by each task instead of duplicating it five times.

Move the scripted full-pipeline response templates into a reference file so the SKILL.md overview stays lean.

DimensionReasoningScore

Conciseness

The body is heavily redundant — the single-task-mode rule is restated in 'CRITICAL: One Task at a Time', 'How to Use', 'Task Execution Order', 'No End-to-End Execution', and 'Important Notes', and the 'DELIVER ONLY... NO SHORTCUTS' block is repeated verbatim per task — so it could be substantially tightened; it avoids a 1 because it does not explain concepts Claude already knows.

2 / 3

Actionability

Provides concrete, copy-paste-ready guidance — specific file names ('[Company]_Research_Document_[Date].md'), word/tab/chart counts, checkbox verification lists, and named tools (DOCX skill, XLSX skill, Read tool) — matching the 'fully executable... copy-paste ready' anchor; not a 2 because guidance is complete rather than pseudocode.

3 / 3

Workflow Clarity

Multi-step process is clearly sequenced (Task Execution Order with dependency arrows) with explicit validation checkpoints (per-task input-verification checkboxes, 'Verification before proceeding' lists, and a 'What to Do if Verification Fails' feedback loop), matching the 'clear sequence with explicit validation steps; feedback loops' anchor.

3 / 3

Progressive Disclosure

The body is an orchestration overview pointing to real one-level-deep reference files (all 6 references/ and 2 assets/ files verified present) with clear 'load only the relevant task reference' navigation guidance, matching the 'clear overview with well-signaled one-level-deep references' anchor.

3 / 3

Total

11

/

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 is specific and distinctive, clearly conveying what the skill does and its multi-task structure, but it omits an explicit 'Use when...' trigger clause and lacks natural term variations a user might actually say.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when initiating coverage on a company, writing a sell-side equity research initiation report, or producing a target price and BUY/HOLD/SELL recommendation.'

Include natural term variations users would say — 'initiate coverage', 'initiation of coverage', 'sell-side research', 'target price' — to broaden trigger coverage beyond the formal task names.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('company research, financial modeling, valuation analysis, chart generation, final report assembly') with specific deliverable types ('markdown docs, Excel models, charts, or DOCX reports'), matching the 'lists multiple specific concrete actions' anchor rather than the partial coverage of a 2.

3 / 3

Completeness

Clearly answers 'what' (create initiation reports via a 5-task workflow with deliverables) but lacks any 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2 rather than 3.

2 / 3

Trigger Term Quality

Contains relevant domain terms ('equity research initiation reports', 'valuation analysis', 'financial modeling') a finance user would say, but misses common natural variations like 'initiate coverage', 'sell-side research', or 'target price' that would warrant a 3.

2 / 3

Distinctiveness Conflict Risk

The 'equity research initiation reports through a 5-task workflow' framing is a clear niche with distinct triggers unlikely to overlap with other skills, matching the 'clear niche with distinct triggers' anchor; not a 2 because it is far more specific than 'works with document files'.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (784 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

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.