plan-deal-strategy

Use when the user wants strategy for one active deal, renewal, negotiation, buying process, or initial sales motion for an offer or product. Build a grounded deal map or practical sales plan with objections, sequencing, posture, and prioritized next actions. Use prepare-for-meeting instead for multi-account same-day customer call queues.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

The body is a well-organized, actionable instruction skill with a complete output template and properly disclosed references. The main room for improvement is tightening repeated routing/alias guidance and adding a filled-in example artifact.

Suggestions

Consolidate the repeated ask_user_input routing and alias-resolution guidance so each rule appears once, reducing token cost without losing clarity.

Add one short worked example (a filled-in Deal Snapshot + one Prioritized Next Action) so the output template is unambiguous in practice.

Tighten the Key Dependency Categories list — the per-source descriptions partly restate what the category name already conveys.

Dimension	Reasoning	Score
Conciseness	Instruction-dense and free of concepts Claude already knows, but the ~170-line body repeats some guidance (e.g., ask_user_input routing and alias logic across steps) that could be trimmed; broadly efficient with minor padding.	4 / 5
Actionability	Highly concrete guidance — explicit role/stance/influence enums, a 5-7 action count with required fields, a 90-day default window, and a complete copy-paste output template — but a fully worked filled-in example would push it to fully executable.	4 / 5
Workflow Clarity	A clear five-step sequence (Qualify, Resolve anchor, Gather evidence, Build strategy, Separate evidence/inference) with explicit stop conditions and a Failure Handling section; checkpoints are mostly soft/confidence-based rather than hard validate-fix-retry loops, though the read-only nature limits that need.	4 / 5
Progressive Disclosure	Well-structured sections in SKILL.md with two real, clearly signaled one-level-deep references (request-schema.yaml, risk-rubric.md), each loaded only when its detail matters; detail is appropriately split out and navigation is easy.	5 / 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.

The description is strong across the board: concrete capabilities, explicit when-trigger, and clear boundary guidance against a sibling skill. Trigger terms are thorough though a couple of common sales synonyms could be added.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Build a grounded deal map or practical sales plan with objections, sequencing, posture, and prioritized next actions" — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both what ("Build a grounded deal map or practical sales plan...") and when ("Use when the user wants strategy for one active deal, renewal, negotiation, buying process, or initial sales motion..."), with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural trigger terms ("active deal, renewal, negotiation, buying process, initial sales motion, offer or product") with good synonym coverage; a few common sales terms like "opportunity" or "pipeline" are absent, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Clear niche (single active-deal strategy) with explicit disambiguation — "Use prepare-for-meeting instead for multi-account same-day customer call queues" — minimizing conflict risk with adjacent skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: XiaomiMiMo/MiMo-Code
Path: packages/opencode/src/skill/builtin/.bundle/sales/workflows/plan-deal-strategy/SKILL.md
Commit: df9f3c9

Reviewed: 1 day 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.