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

92%

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

85%

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

A well-structured, actionable instruction-only skill with a clear sequenced workflow, guarded evidence/inference separation, and clean progressive disclosure. Its only weakness is moderate redundancy across sections that inflates token cost.

Suggestions

Consolidate the repeated CRM-grounding and alias-handling guidance (currently restated in sections 2, 3, Rules, and Key Dependency Categories) into one canonical statement and reference it.

Merge the 'offer up to five candidates via ask_user_input' instructions that appear in both step 2 and step 3 into a single candidate-resolution sub-procedure to remove duplication.

Trim the Coverage Summary and lane-status recording rules, which overlap with the 'Record each lane as available, unavailable, empty, stale, conflicting...' line in step 3.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of concepts Claude already knows, but CRM-grounding, alias handling, and candidate-offering guidance are restated across sections 2, 3, and the Rules, so it could be tightened without loss.	2 / 3
Actionability	Highly actionable: fixed role/stance/influence enums, a 5-7 action budget with required fields (owner, due/TBD, expected outcome, linked risk/stakeholder, source), and an exact section-ordered output template.	3 / 3
Workflow Clarity	Five clearly numbered steps with explicit checkpoints — confirm a single inferred candidate via ask_user_input before enrichment, record lane status, lower confidence on conflicting evidence, and a dedicated Failure Handling section for a no-anchor case.	3 / 3
Progressive Disclosure	SKILL.md owns the core flow and signals two real one-level-deep references (request-schema.yaml, risk-rubric.md) each gated by a specific 'Use ... when' condition; both files exist and content is appropriately split.	3 / 3
	Total	11 / 12 Passed

Description

100%

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, third-person description with explicit 'Use when' trigger, concrete capability list, natural trigger terms, and clear disambiguation from a sibling skill. No vague fluff or over-claims.

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' — rather than vague language.	3 / 3
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...'), satisfying the explicit-trigger requirement.	3 / 3
Trigger Term Quality	Covers natural terms a user would say — 'strategy', 'active deal', 'renewal', 'negotiation', 'buying process', 'sales motion', 'offer', 'product' — with good variation.	3 / 3
Distinctiveness Conflict Risk	Clear niche (single active-deal strategy) and explicitly disambiguates the nearest neighbor: 'Use prepare-for-meeting instead for multi-account same-day customer call queues.'	3 / 3
	Total	12 / 12 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: 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.