CtrlK
BlogDocsLog inGet started
Tessl Logo

initiate

Initiate coverage — generate both research note (HTML) and Excel model (.xlsx)

51

Quality

56%

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/daloopa/skills/initiate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%

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

This is a well-structured, highly specific capstone workflow with excellent phase sequencing and explicit validation, but it is long and redundant, lacks executable code or a concrete spreadsheet-generation mechanism, and keeps too much detail inline rather than splitting it into bundle reference files.

Suggestions

Remove the redundant Context Key Checklist (it restates keys already defined per phase) and de-duplicate the citation-format and design-system references to tighten conciseness.

Replace 'best available spreadsheet-generation workflow' with a concrete approach — a specific openpyxl snippet or a bundled script — and provide an example tab template instead of prose-only specs, to lift actionability.

Move the detailed Excel tab specs and the context-key checklist into a bundled reference file (e.g., references/excel-model.md) referenced one level deep from the body, improving progressive disclosure.

DimensionReasoningScore

Conciseness

The ~450-line body is mostly domain-specific actionable guidance (no basic-concept padding), but it carries real redundancy: the Context Key Checklist restates context keys already defined per phase, the citation format is stated at both line 363 and line 452, and design-system/data-access pointers are repeated throughout.

2 / 3

Actionability

It gives highly concrete specs (WACC formula, citation format, 8-tab structure, WebSearch query templates, hex colors, file names), but provides no executable code and leaves some steps vague ('best available spreadsheet-generation workflow', 'build the narrative', 'be honest and critical').

2 / 3

Workflow Clarity

A clearly sequenced 13-phase process with explicit validation checkpoints — a pre-render Context Key Checklist, the opening guard ('ask for one before proceeding'), and citation enforcement ('No exceptions') — plus checklists for a complex multi-output process.

3 / 3

Progressive Disclosure

External references are well-signaled and one level deep ('../data-access.md Section 1.5', '../design-system.md'), but the body is a monolithic 450-line wall with no bundle files, and content that could be split (Excel tab specs, the context-key checklist) is kept inline.

2 / 3

Total

9

/

12

Passed

Description

50%

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 states the skill's purpose and two concrete deliverables but is otherwise thin: it lacks an explicit 'Use when' trigger, omits most of the skill's actual actions, and overlaps with sibling research skills. It is adequate but mediocre.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when initiating equity research coverage on a company — producing a research note and Excel model together').

Include natural trigger variations users would say, such as 'equity research initiation', 'initiation report', or 'financial model'.

Mention additional concrete actions (DCF valuation, forward projections, peer comps) to raise specificity and distinguish it from the separate research-note and build-model skills.

DimensionReasoningScore

Specificity

It names the domain ('Initiate coverage') and two concrete deliverables ('research note (HTML) and Excel model (.xlsx)'), but relies on a single action verb ('generate') and omits the many other concrete actions the skill performs (DCF, projections, peer analysis), so it is not comprehensive.

2 / 3

Completeness

It clearly states what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

'Initiate coverage', 'research note', 'Excel model', and '.xlsx' are natural terms an analyst would say, but common variations like 'equity research', 'initiation report', or 'financial model' are absent.

2 / 3

Distinctiveness Conflict Risk

'Initiate coverage' with dual HTML+Excel outputs is a clear niche, but the body itself references sibling 'research-note' and 'build-model' skills, indicating real overlap with similar skills.

2 / 3

Total

8

/

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

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
openai/plugins
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.