follow-up-after-call

Use after a completed customer, prospect, partner, or important internal sales call, discovery session, demo, or conversation, including when the user supplies or uploads a transcript, notes, recording summary, or other grounded evidence. Advise on, assess, qualify, recap, and produce seller-ready follow-up actions and drafts.

Quality

95%

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

100%

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

An exemplary instruction-only skill body: concise, highly actionable with a copy-ready output template, a well-sequenced workflow with validation checkpoints, and clean one-level progressive disclosure to real reference files.

Dimension	Reasoning	Score
Conciseness	The body is dense and prescriptive with no padding about concepts Claude already knows (no explanation of what a CRM, transcript, or discovery call is); each conditional guard clause earns its place for a genuinely nuanced workflow, so it stays lean despite its length.	3 / 3
Actionability	It provides a complete copy-paste output template, exact literals ("write exactly `Not applicable: this was an internal call.`", "Keep the CRM text to exactly one sentence"), explicit ask_user_input option lists, and concrete automation file paths — fully actionable guidance for an instruction-only skill.	3 / 3
Workflow Clarity	A clear four-step numbered sequence (Resolve evidence → Gather enrichment → Classify/extract → Draft) with explicit validation checkpoints ("ask the user to confirm it before drafting", "do not gather broad enrichment before the user chooses", "Stop once the package is grounded") and a dedicated Failure Handling section.	3 / 3
Progressive Disclosure	The body is an overview that defers detail to two real one-level-deep references (request-schema.yaml for input normalization, opportunity-and-channel-selection.md for ranking/channel safety), each clearly signaled with a "Use ... when ..." condition; both files exist in references/.	3 / 3
	Total	12 / 12 Passed

Description

90%

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 description that clearly states both capability and trigger conditions with natural, well-scoped keywords. The only weakness is imperative voice where third person is preferred by the rubric, which caps specificity.

Suggestions

Reword capability verbs into third person (e.g., "Advises on, assesses, qualifies, recaps, and produces seller-ready follow-up actions and drafts") to satisfy the rubric's voice guideline and recover the specificity point.

Open with a third-person capability clause before the "Use after..." trigger to avoid leading with a second-person imperative.

Dimension	Reasoning	Score
Specificity	The phrase "Advise on, assess, qualify, recap, and produce seller-ready follow-up actions and drafts" lists multiple concrete actions (anchor 3), but the description uses imperative/second-person voice ("Use after...", "Advise on...") rather than third person, so per the rubric's voice guideline specificity is reduced by 1.	2 / 3
Completeness	It answers both what ("Advise on, assess, qualify, recap, and produce seller-ready follow-up actions and drafts") and when ("Use after a completed customer, prospect, partner, or important internal sales call... including when the user supplies or uploads a transcript, notes, recording summary"), with an explicit trigger clause.	3 / 3
Trigger Term Quality	Natural user-facing terms are well covered: "sales call, discovery session, demo, or conversation" plus "transcript, notes, recording summary" — phrasings a user would actually say when they need this skill.	3 / 3
Distinctiveness Conflict Risk	The post-call sales follow-up niche is clearly scoped ("after a completed customer, prospect, partner, or important internal sales call, discovery session, demo") with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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/follow-up-after-call/SKILL.md
Commit: ff87d47

Reviewed: about 10 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.