CtrlK
BlogDocsLog inGet started
Tessl Logo

build-business-case

Review commercial proposals and build customer-led business cases, ROI or value models, pricing or investment rationales, executive summaries, and customer-ready value stories tied to a customer, workflow, initiative, or decision.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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, highly actionable instruction skill with clear sequencing and excellent progressive disclosure; its only weakness is moderate redundancy across the workflow, rules, and output sections that inflates token use without adding new information.

Suggestions

Deduplicate the value buckets, the evidence-priority order, and the 'do not post/share/create a document' prohibition so each appears in one canonical place (e.g., keep buckets/order in their reference and the prohibition once in Rules).

Consider trimming the Output Format template where it re-states the Known/Inferred/Assumed/Missing labels and buckets already defined in §3–§4, pointing instead to the definitions.

Tighten the 'Next Step Options' and 'Next steps to avoid' pair, which overlaps the Rules and Failure Handling sections, into a single consolidated closing block.

DimensionReasoningScore

Conciseness

It assumes Claude's competence (no basic-concept padding) and is action-dense, but several elements repeat across sections — value buckets in §3 and the Output Format, the evidence-priority order in §4, and the "do not post/share/create a document" rule in Rules, Next steps to avoid, and Failure Handling — so not every token earns its place and it could be tightened.

2 / 3

Actionability

Gives concrete, copy-paste-ready guidance: exact Knowledge & Files query strings, named formula patterns per value bucket, a full labeled output template with tables, and the Known/Inferred/Assumed/Missing taxonomy — actionable instruction-only guidance with no code needed.

3 / 3

Workflow Clarity

A clearly numbered five-step sequence (resolve anchor → find account-native anchor → build value logic → quantify → draft) with explicit checkpoints — "Stop the first pass once the core case is supported", "bounded pass using at most three source reads", "keep the math structural" when inputs are missing — and a failure-handling feedback loop for multi-source operations.

3 / 3

Progressive Disclosure

SKILL.md is a clear overview with four well-signaled, one-level-deep references (verified as real, flat files with no cross-nesting), each gated by a 'Use X when...' trigger, with detail appropriately split across input/output, workflow, value-model, and presentation files.

3 / 3

Total

11

/

12

Passed

Description

82%

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 specific, distinct description with strong natural trigger terms, but it states only what the skill does and never gives an explicit "Use when..." trigger clause, capping completeness at 2.

Suggestions

Add an explicit 'Use when...' clause naming the user situations that should trigger this skill (e.g., 'Use when a user asks for a business case, ROI or value model, or executive summary tied to a specific account or initiative').

Include a couple more common user phrasings in the trigger (e.g., 'build a business case', 'justify the investment', 'value story for a deal') to broaden natural trigger coverage.

Briefly state what this skill is NOT (a placement on the distinctiveness already present in the body) directly in the description to further reduce overlap with adjacent sales skills.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "Review commercial proposals", "build customer-led business cases, ROI or value models", "pricing or investment rationales", "executive summaries", and "customer-ready value stories" — matching the anchor that lists several specific concrete actions.

3 / 3

Completeness

It clearly answers "what" (multiple concrete actions) but lacks an explicit "Use when..." clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 2 even though the "what" is strong.

2 / 3

Trigger Term Quality

Uses natural terms a user would say in this domain — "business cases", "ROI", "value models", "pricing", "investment rationales", "executive summaries", "value stories" — giving good coverage of likely utterances; not just technical jargon.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — customer-led commercial value cases — and the "tied to a customer, workflow, initiative, or decision" scoping plus the body's explicit contrasts with presentation/writeback workflows make it unlikely to trigger for the wrong skill.

3 / 3

Total

11

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository
XiaomiMiMo/MiMo-Code
Reviewed

Table of Contents

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.