CtrlK
BlogDocsLog inGet started
Tessl Logo

sector-overview

Create comprehensive industry and sector landscape reports covering market dynamics, competitive positioning, key players, and thematic trends. Use for client requests, sector initiations, thematic research pieces, or internal knowledge building. Triggers on "sector overview", "industry report", "market landscape", "sector analysis", "industry deep dive", or "thematic research".

70

Quality

88%

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 sector-overview in anthropics/financial-services

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, lean instructional skill: a clear six-step workflow with concrete templates, metrics, and output specs, and no bundle-file overhead. The main gaps are the absence of explicit validation checkpoints inside the workflow and no data-sourcing guidance.

Suggestions

Embed validation as explicit workflow checkpoints (e.g., after Step 2: 'Verify every market size figure has a named source or methodology before proceeding') instead of leaving all quality checks in the trailing Important Notes section.

Add brief data-sourcing guidance (which databases or research-firm reports to pull market share and multiples from, and what to do when figures conflict or are stale) to close the actionability gap.

Move the company-profile template table and output-format specification into a references/ file (e.g., REPORT_TEMPLATE.md) to keep SKILL.md a lean overview and strengthen progressive disclosure.

DimensionReasoningScore

Conciseness

The body is a dense bulleted checklist with no fluff sentences or concept explanations, matching anchor 4's 'efficient; minor instances that could be trimmed'. It falls short of 5 because items like "Valuation snapshot (P/E, EV/EBITDA, EV/Revenue)" and "Business description (2-3 sentences)" restate what a competent model already knows about sector report structure.

4 / 5

Actionability

Concrete specifics are provided: a company-comparison table with named columns, page-count guidance ("5-10 pages" vs "20-30 pages"), named chart types ("market size waterfall, competitive positioning matrix, valuation scatter plot"), and output formats (Word/PowerPoint plus Excel appendix). Anchor 5 is not reached because there is no guidance on data sourcing/retrieval or a worked example of any section, leaving minor execution gaps.

4 / 5

Workflow Clarity

The six numbered steps (Define Scope through Output) form a clear, logical sequence with decision inputs pinned in Step 1 and the deliverable specified in Step 6. It is not 5 because validation is not embedded in the flow: checks like "Source all market size data" and "note the date and flag data that may be stale" live in a trailing Important Notes section rather than as explicit checkpoints, so they are implicit rather than sequenced.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the single ~85-line file is well organized with a clear step hierarchy and a separate Important Notes section, matching anchor 4's 'good structure; most content appropriately placed'. Not 5 because it slightly exceeds the compact single-file range where a fully self-contained skill scores top marks, and the company-profile template and output specification could arguably live in a reference file.

4 / 5

Total

16

/

20

Passed

Description

95%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: explicit what and when, natural trigger synonyms, third-person voice, and no filler. The only (minor) limitation is that capability coverage is expressed as report content areas rather than a set of distinct executable actions.

DimensionReasoningScore

Specificity

"Create comprehensive industry and sector landscape reports covering market dynamics, competitive positioning, key players, and thematic trends" names the domain plus several specific coverage areas, but the action list is effectively one verb (create reports) rather than multiple distinct concrete actions like the anchor-5 example. It sits above anchor 3 (only 1-2 concrete actions) because four coverage dimensions are explicitly enumerated.

4 / 5

Completeness

The 'what' is explicit ("Create comprehensive industry and sector landscape reports covering...") and the 'when' is explicit twice: "Use for client requests, sector initiations, thematic research pieces, or internal knowledge building" plus the concrete "Triggers on" phrase list. This matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

"Triggers on 'sector overview', 'industry report', 'market landscape', 'sector analysis', 'industry deep dive', or 'thematic research'" gives comprehensive natural-phrase coverage with multiple synonyms a user would actually say. There is no file extension to include for a report-generation skill, so nothing natural is missing.

5 / 5

Distinctiveness Conflict Risk

The equity-research framing ("sector initiations", "thematic research pieces", "competitive positioning") carves out a clear niche with distinct triggers, so it is unlikely to fire for unrelated skills. Not the level below (4) because the trigger phrases are domain-specific rather than broadly overlapping with generic analysis skills.

5 / 5

Total

19

/

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.