CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

company-analysis

Analyze companies and generate comprehensive research reports. Use when user asks to research, analyze, profile, or investigate a company.

80

1.21x
Quality

79%

Does it follow best practices?

Impact

84%

1.21x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./lesson-04-claude-code-config/demo/.claude/skills/company-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 thorough, actionable research playbook with a clear phased workflow and copy-paste templates. Its main weaknesses are verbosity from inlined reference-style content and the absence of validation feedback loops.

Suggestions

Move the full report-format template and the long search-pattern/tip lists into reference files (e.g. references/report-template.md, references/search-patterns.md) and link to them from SKILL.md to improve conciseness and progressive disclosure.

Add explicit validation/verification checkpoints in the workflow (e.g. cross-check facts across two independent sources before writing them, and re-run searches if a section returns no usable results) to strengthen feedback loops.

Trim sections that restate what Claude already knows about how web search works, keeping only the company-specific query patterns that add value.

DimensionReasoningScore

Conciseness

The body mostly assumes Claude's competence but the ~75-line placeholder report template and exhaustive search-pattern/tips sections restate search behavior Claude already knows, adding padding that could be tightened.

3 / 5

Actionability

Concrete search query strings, a copy-paste report template, named third-party sources (Crunchbase, BuiltWith, Wappalyzer), and explicit subagent delegation (web-researcher, people-finder) give mostly executable guidance with minor gaps.

4 / 5

Workflow Clarity

A clear three-phase sequence with time budgets and a terminal Quality Checklist, but no validate→fix→retry feedback loops embedded in the flow; sits above 3 due to the explicit checklist checkpoint.

4 / 5

Progressive Disclosure

Well-organized with clear section headers, but at ~310 lines the full report template and search-pattern vault are inlined with no external reference files, so content that could be split out remains in SKILL.md.

3 / 5

Total

14

/

20

Passed

Description

87%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, well-formed description that answers both what and when with natural trigger verbs and a clear niche. Minor room to add noun-form triggers and broaden the action list.

DimensionReasoningScore

Specificity

"Analyze companies and generate comprehensive research reports" names the domain and two concrete actions plus the output artifact; not a 5 because "analyze companies" is somewhat generic and the action list is not exhaustive.

4 / 5

Completeness

It explicitly states both the "what" (analyze companies and generate research reports) and the "when" ("Use when user asks to research, analyze, profile, or investigate a company") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"research, analyze, profile, or investigate a company" provides four natural verbs users actually say; missing noun-form synonyms like "company profile" or "tell me about," so it falls short of comprehensive (5).

4 / 5

Distinctiveness Conflict Risk

The company-research niche with specific trigger verbs is clearly distinguishable from other skills and unlikely to fire for the wrong skill.

5 / 5

Total

18

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

udacity/cd14715-claude-code-classroom

Path

lesson-04-claude-code-config/demo/.claude/skills/company-analysis/SKILL.md

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.