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

75%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/opencode/src/skill/builtin/.bundle/sales/SKILL.md

Quality

Content

77%

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

A concise, clearly sequenced routing skill body that delegates well by design, but its actionability and progressive disclosure are undermined because every referenced workflow, script, and provider skill is absent from the bundle.

Suggestions

Ship the referenced bundle (at minimum workflows/index/SKILL.md) so the routing instructions resolve to real files.

Add one concrete, executable example of a routed step (e.g., a sample command or template path) so the body is actionable even before a workflow is loaded.

Include a verification checkpoint in routing (e.g., 'Confirm the named workflow exists under workflows/ before proceeding') to catch missing bundles.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence ("Read workflows/index/SKILL.md completely", "Select the narrowest focused workflow") with no concept padding or unnecessary explanation, matching the lean-and-efficient anchor.	3 / 3
Actionability	It gives procedural direction ("Read every selected workflow's SKILL.md completely before acting", "Load provider-specific skills... only when relevant") but no executable specifics, and the referenced paths (workflows/index/SKILL.md, bundled scripts) do not exist in the bundle, leaving guidance incomplete.	2 / 3
Workflow Clarity	"Route the request" is a clearly ordered five-step sequence with explicit conditionals (steps 3-5 gate loading on relevance and stated conditions); routing is non-destructive so the missing-validation cap does not apply.	3 / 3
Progressive Disclosure	References are well-signaled and one level deep (workflows/index/SKILL.md, provider-specific skills, bundled scripts/templates), but no bundle files exist, so the references dangle and the navigation cannot be verified, stopping short of the fully-functional level-3 anchor.	2 / 3
	Total	10 / 12 Passed

Description

72%

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 trigger-rich, well-scoped sales invocation description with excellent natural keywords and low conflict risk, but it over-indices on "when" and leaves the "what does this skill do" only implied.

Suggestions

Lead with one concrete statement of what the skill does (e.g., 'Routes sales requests to focused workflows for meeting prep, deal strategy, and CRM enrichment') before the trigger list.

Convert domain nouns into verb phrases so capabilities read as actions ('prepare customer meetings', 'prioritize accounts', 'build business cases') to lift specificity.

Dimension	Reasoning	Score
Specificity	Names the Sales domain and many task areas ("customer meeting preparation, call follow-up, account prioritization, account signals, deal strategy"), but these read as a trigger list of domains rather than the concrete actions the skill performs, so it stops short of the multi-action anchor.	2 / 3
Completeness	It has an explicit, strong "when" ("Use this skill whenever Sales is explicitly invoked or the task involves...") but never states what the skill does, so the "what" is only implied rather than answered; not the level-3 both-what-and-when anchor.	2 / 3
Trigger Term Quality	Strong coverage of natural terms a sales user would say ("call follow-up", "deal strategy", "business cases", "competitive briefs", "forecasts", "rep coaching", "company research", "CRM context", "enrichment"), matching the good-coverage anchor.	3 / 3
Distinctiveness Conflict Risk	The explicit "Sales is explicitly invoked" trigger plus sales-specific domain terms carve a clear niche unlikely to fire for non-sales skills, matching the distinct-trigger anchor.	3 / 3
	Total	10 / 12 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: ff87d47

Reviewed: about 9 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.