sales

Use this skill whenever Sales is explicitly invoked or the task involves customer meeting preparation, call follow-up, account prioritization, account signals, deal strategy, business cases, competitive briefs, forecasts, customer evidence, rep coaching, company research, CRM context, or company and contact enrichment.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

An efficient, well-structured router skill that delegates detail to bundled workflows and enforces a confirmation checkpoint before external actions. Minor gains are possible by rendering workflow references as explicit links and tightening a few high-level routing steps.

Suggestions

Render the referenced workflow and provider-skill paths as explicit markdown links (e.g., [workflows/index/SKILL.md](workflows/index/SKILL.md)) so navigation is resolvable rather than described.

Add a brief validation cue in the routing sequence (e.g., 'confirm the chosen workflow matches the request scope before loading provider skills') to make the per-step checkpoint explicit rather than implied.

Tighten step 4 ('read them only when their stated conditions apply') by specifying how to evaluate those conditions, so the routing step is fully executable.

Dimension	Reasoning	Score
Conciseness	Lean router overview with no padding or explanation of concepts Claude already knows; every line ('Read workflows/index/SKILL.md completely', 'Select the narrowest focused workflow', 'Do not invent customer facts') earns its place.	5 / 5
Actionability	Concrete directives ('Read every selected workflow's SKILL.md completely before acting', 'Resolve relative links from the file containing the link') give executable routing guidance; as an instruction-only router it appropriately lacks code, though a few steps remain high-level.	4 / 5
Workflow Clarity	Clear 5-step routing sequence with an explicit confirmation checkpoint for external/destructive actions ('Require appropriate confirmation before sending messages, updating CRM records, or taking other external actions'), satisfying the validation requirement; per-workflow validation is delegated rather than repeated inline, leaving a minor gap.	4 / 5
Progressive Disclosure	Well-organized overview pointing one level deep to workflows/index/SKILL.md and provider-specific skills with clear signaling; references are described rather than given as resolvable links, a minor organization gap.	4 / 5
	Total	17 / 20 Passed

Description

92%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-structured description that explicitly pairs a 'Use when…' trigger with a comprehensive list of concrete sales activities. It is concise, specific, and clearly distinct from other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete sales actions — 'customer meeting preparation, call follow-up, account prioritization, account signals, deal strategy, business cases, competitive briefs, forecasts, customer evidence, rep coaching, company research, CRM context, or company and contact enrichment' — providing comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers 'when' via 'Use this skill whenever Sales is explicitly invoked or the task involves…' and answers 'what' via the enumerated activity list, with concrete trigger phrases for both.	5 / 5
Trigger Term Quality	Strong natural trigger phrasing ('Sales is explicitly invoked', 'customer meeting preparation', 'forecasts', 'CRM context') that users would actually say; a few common synonyms or product-name variants are missing, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear sales-specific niche with distinct triggers ('Sales is explicitly invoked', deal strategy, forecasts, CRM context) and minimal overlap risk with non-sales skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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: XiaomiMiMo/MiMo-Code
Path: packages/opencode/src/skill/builtin/.bundle/sales/SKILL.md
Commit: ec3f989

Reviewed: ~13 hours ago

Table of Contents

Discovery Implementation Validation

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.