review-forecast

Use when the user wants forecast posture, forecast accuracy, commit, upside, forecast-call preparation, or a pipeline or deal-risk review for a seller book, team, period, report, or named deal set. Produce a manager-ready forecast rollup, risk posture, recommendation changes, evidence gaps, and follow-up actions.

Quality

86%

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

73%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 delivers a well-sequenced, validation-rich workflow with concrete enums, fields, and a copy-paste-ready output template, scoring highly on workflow clarity and actionability. It is held back from the top tier by repeated read-only language and a long inline automation section that could be condensed or moved to a reference.

Suggestions

De-duplicate the read-only constraint (currently restated in Context-Gathering, Workflow, Automation Offer Guard, and Rules) into a single authoritative statement to improve conciseness.

Add one filled-in worked example of the Forecast Review output so the actionability moves from a strong template to fully exemplified common cases.

Consider moving the automation prompt template and matching logic into a reference file to reduce inline body length while preserving the one-level-deep reference pattern.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient domain guidance rather than generic concept explanation, but the read-only constraint is repeated three to four times and the inline Automation Offer Guard section is long enough that it could be tightened.	3 / 5
Actionability	Concrete enums (low/moderate/high, none/light/standard), specific required CRM fields, and a copy-paste-ready output template give strong executable guidance, but no filled-in worked example is provided, leaving a minor gap versus fully exemplified coverage.	4 / 5
Workflow Clarity	The four numbered steps are clearly sequenced with explicit validation gates (stop-and-ask for missing truth, bounded three-read candidate pass, downgrade-to-risk-only when thin, confirm inferred conventions), and the skill is explicitly read-only so the destructive-operation cap does not apply.	5 / 5
Progressive Disclosure	A clear one-level-deep reference to references/request-schema.yaml (verified present) is well signaled and the body has clean section headers, but the dense inline Automation Offer Guard and output template keep it just short of an ideally split overview.	4 / 5
	Total	16 / 20 Passed

Description

100%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 a strong, third-person statement that explicitly couples concrete trigger phrases with concrete deliverables for a well-defined forecast-review niche. It is comprehensive without padding and uses natural sales-domain terminology with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	"Produce a manager-ready forecast rollup, risk posture, recommendation changes, evidence gaps, and follow-up actions" lists multiple specific concrete deliverables with comprehensive coverage of the skill's output, matching the score-5 anchor.	5 / 5
Completeness	It explicitly pairs a concrete "Use when the user wants..." trigger clause with a concrete "Produce a..." deliverables clause, clearly answering both what and when.	5 / 5
Trigger Term Quality	Phrases like "forecast posture," "forecast accuracy," "commit," "upside," "forecast-call preparation," and "pipeline or deal-risk review" are natural terms a sales forecaster would actually say, with synonym coverage across the forecast domain.	5 / 5
Distinctiveness Conflict Risk	The forecast-review-for-a-seller-book/team/period/report niche with forecast-specific triggers (commit, upside, forecast-call) is clearly distinct with minimal overlap risk.	5 / 5
	Total	20 / 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/review-forecast/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.