CtrlK
BlogDocsLog inGet started
Tessl Logo

sales-company-research

Research companies, partners, and referral channels to shape draft outreach approaches, messages, or partner motions; exclude descriptive company profiling, list enrichment, and internal source finding.

59

Quality

68%

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 ./packages/opencode/src/skill/builtin/.bundle/sales/workflows/sales-company-research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 compact, well-structured instruction skill with concrete routing boundaries, an explicit output template, and clean workflow sequencing. Its main weaknesses are dangling cross-references buried in the output template, repeated send/CRM guardrails, and the absence of worked examples for its core artifacts.

Suggestions

Move the '../index/SKILL.md' cross-references out of the fenced output template into clearly signaled links in the body, and fix the malformed 'SKILL.md## Cross-Skill Best Practices' path.

Consolidate the 'never send / no CRM write' guardrail into one Rules entry instead of repeating it in the intro, workflow, next-steps, and rules sections.

Add one short worked example of a fit hypothesis and draft outreach line to make the output template concrete.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no concept re-teaching, tight workflow steps), but 'never send / no CRM write' is repeated in four places, and strikethrough list items ('~~Sales Intelligence...') plus '{Follow the instructions...}' placeholder lines add avoidable noise. Not 5 because of this redundancy; not 3 because padding is minor rather than a pattern of unnecessary explanation.

4 / 5

Actionability

Concrete, specific guidance throughout: a 4-step workflow, routing rules to three named sibling skills ('enrich-company-and-contact-data', 'find-key-internal-sources', 'plan-deal-strategy'), a full output template, and explicit next-step options. Not 5 because there are no worked examples (e.g., a sample fit hypothesis or draft message) covering the common cases; not 3 because the guidance is executable, not high-level hints.

4 / 5

Workflow Clarity

The 4-step workflow is clearly sequenced with explicit decision handling ('If a material anchor is missing, ask only for the smallest input that changes the research path') and evidence/inference separation. Not 5 because validation checkpoints are lighter than the anchor's explicit validate-fix-retry loops (e.g., no step to verify sourced claims before drafting); not 3 because the sequence and guardrails are explicit, not implicit.

4 / 5

Progressive Disclosure

Sections are well-organized and the skill is self-contained, but its only references ('plugins/sales/skills/index/SKILL.md', '../index/SKILL.md#limitations-and-improvements') are dangling, unverifiable, one malformed ('SKILL.md## Cross-Skill Best Practices'), and buried inside the fenced output template as curly-brace placeholders. Not 4 because navigation to supporting material is unclear and the references are not clearly signaled in the body; not 2 because the inline content is appropriately concise rather than monolithic.

3 / 5

Total

15

/

20

Passed

Description

66%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 focused, boundary-aware description with a clear 'what' and well-chosen exclusions, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness and weakens its trigger coverage. Adding a concrete trigger phrase (e.g., 'Use when preparing outreach or partner messages for a researched target') would lift the two weakest dimensions.

Suggestions

Add an explicit trigger clause: 'Use when drafting outreach for a researched company, partner, or referral channel' to satisfy the completeness cap.

Include natural user synonyms such as 'prospecting', 'account research', or 'outreach drafting' to broaden trigger-term coverage.

Sharpen the positive action list with 1-2 more concrete outputs (e.g., 'draft-first emails and partner scripts') to approach comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('research companies, partners, and referral channels to shape draft outreach approaches, messages, or partner motions') with explicit exclusions, matching the 'several specific actions; minor gaps in coverage' anchor. It falls short of 5 because the actions are framed at a fairly abstract level without the comprehensive, fully concrete coverage of the top anchor, and above 3 because it goes well beyond 1-2 concrete actions.

4 / 5

Completeness

The 'what' is clear (research targets to shape draft outreach), but there is no 'Use when...' clause or equivalent explicit trigger guidance; the exclusion clause is a boundary statement, not a trigger. Per the judging guidelines, a missing explicit trigger clause caps completeness at 3 even though the 'what' half is strong.

3 / 5

Trigger Term Quality

Good keyword coverage with natural phrases users would say ('companies', 'partners', 'referral channels', 'outreach approaches', 'messages', 'partner motions'). Not 5 because common sales-research synonyms like 'prospecting', 'cold email', 'account research', or 'firmographics' are absent; not 3 because coverage is solid rather than only partially relevant.

4 / 5

Distinctiveness Conflict Risk

The explicit exclusions ('exclude descriptive company profiling, list enrichment, and internal source finding') carve out the nearest competing skills, giving a mostly distinct niche. Not 5 because the positive space ('research companies, partners') is still broad enough to overlap with general company-research or sales-strategy skills; not 3 because the exclusions materially reduce overlap risk.

4 / 5

Total

15

/

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

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository
XiaomiMiMo/MiMo-Code
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.