prioritize-accounts

Use when the user asks which existing accounts to work now, which leads are hottest in a grounded list or pipeline, how to rank a territory, book, pipeline, ICP list, or account list, where to focus this week, or what rep-ready next actions to take. Prioritize accounts using current evidence, suppress or account for in-flight motion, and identify reachable contacts when supported. Use enrichment instead for net-new company discovery or missing-data completion.

Quality

90%

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

86%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 highly actionable, well-structured skill body with concrete commands, exact file contracts, and properly separated one-level-deep references. Minor conciseness redundancy and an implicit error-recovery loop are the only weak spots.

Suggestions

Add an explicit 'if the sanity check fails, locate the unresolved placeholder, fix the payload, and regenerate' feedback loop to the view-generation workflow.

De-duplicate the no-outreach / no-CRM-write prohibition so it is stated once authoritatively rather than repeated across Overall Rules and the Automation section.

Dimension	Reasoning	Score
Conciseness	Dense, domain-specific rules that assume Claude's competence and avoid explaining basic concepts, with only minor redundancy (e.g., the no-outreach prohibition repeats across Overall Rules and Automation), placing it above the 3-anchor but not fully lean.	4 / 5
Actionability	Fully executable guidance: exact output paths per OS, the exact placeholder __PRIORITIZE_ACCOUNTS_DATA_JSON__, the \u003c escape rule, a referenced payload schema, and a copy-paste output format template covering common cases.	5 / 5
Workflow Clarity	Clear sequenced view-generation steps with an explicit sanity-check validation ("Sanity check that the generated file contains no unresolved placeholder"), but the fix-and-retry feedback loop on validation failure is only implicit rather than spelled out.	4 / 5
Progressive Disclosure	Overview body points to well-signaled, one-level-deep references (references/suppression-and-fallbacks.md, references/template-payload.schema.json, assets/account-priority-pane.template.html), all verified to exist, with content appropriately split into bundle files.	5 / 5
	Total	18 / 20 Passed

Description

95%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, third-person description with rich natural trigger phrasing, explicit what/when guidance, and a clear disambiguation against the related enrichment skill. Specificity is the only slightly-less-than-perfect dimension.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("Prioritize accounts using current evidence, suppress or account for in-flight motion, and identify reachable contacts when supported") with only minor coverage gaps, falling just short of the fully comprehensive 5-anchor example.	4 / 5
Completeness	Explicitly answers both what ("Prioritize accounts using current evidence, suppress or account for in-flight motion") and when ("Use when the user asks which existing accounts to work now..."), with concrete trigger phrases and a disambiguating clause.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases a user would actually say ("which leads are hottest", "rank a territory, book, pipeline, ICP list, or account list", "where to focus this week", "rep-ready next actions"), matching the 5-anchor coverage including synonyms.	5 / 5
Distinctiveness Conflict Risk	Carves a clear niche (prioritizing existing accounts) and explicitly reduces conflict risk with "Use enrichment instead for net-new company discovery or missing-data completion."	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/prioritize-accounts/SKILL.md
Commit: ec3f989

Reviewed: 3 days 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.