CtrlK
BlogDocsLog inGet started
Tessl Logo

prepare-for-meeting

Use when the user wants to prepare for one or more upcoming meetings with customers, prospects, partners, accounts, or important stakeholders; requests daily or date-based meeting preparation; asks to organize a same-day customer call queue; asks for the most important qualifying meeting of the day; or identifies meetings only by company, attendee, topic, or date. Produce an individual meeting brief or a chronological multi-meeting agenda as appropriate.

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 is a well-structured, highly actionable instruction skill with concrete templates and clear workflows; its main weakness is moderate redundancy in the automation sections. Progressive disclosure is handled well through signaled cross-skill references.

Suggestions

Tighten the Automation Offer Guard section — the digest shape and prompt block are described twice; consolidate to a single statement plus the code block to reduce token cost.

Dedupe the limitation/source-gap guidance ('Avoid unsupported claims', 'state the limitation') into one canonical location and reference it rather than restating across Workflow Guidance and Key Dependency Categories.

Add an explicit validate/refine checkpoint after the first draft (e.g., re-confirm account/opportunity anchor and re-check time bounds) to strengthen the feedback loop in workflow_clarity.

DimensionReasoningScore

Conciseness

Mostly efficient but contains redundancy: the Automation Offer Guard restates the digest shape and prompt block more than once, and some guidance ('Avoid unsupported claims') repeats across sections; could be tightened without losing clarity.

3 / 5

Actionability

Highly actionable for an instruction-only skill: numbered ranking priorities, exact candidate-offering parameters ('up to three candidates via ask_user_input()', 'next 3 business days, with 25 max results'), copy-ready output templates, and a ready-to-use automation prompt block.

5 / 5

Workflow Clarity

Clear sequenced workflow (resolve/clarify → draft → offer next step) with verification guards ('If context is missing, stale, or conflicting, state the limitation', 'All suggested events must be in the future', automation-existence check), though no explicit re-validation loop on brief refinement.

4 / 5

Progressive Disclosure

Well-organized sections with clearly signaled one-level references to ../index/SKILL.md sections via inline placeholders; no bundle files present. Minor gaps: the long Automation Offer Guard could plausibly be a separate reference.

4 / 5

Total

16

/

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.

The description is explicit, trigger-rich, and tightly scoped to meeting preparation, clearly answering both what and when. It is among the strongest examples for this skill type.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'prepare for one or more upcoming meetings', 'organize a same-day customer call queue', 'Produce an individual meeting brief or a chronological multi-meeting agenda' — with minor coverage gaps versus a fully comprehensive action list.

4 / 5

Completeness

Explicitly answers both what ('Produce an individual meeting brief or a chronological multi-meeting agenda') and when (the 'Use when the user wants to...' clause with concrete trigger phrases).

5 / 5

Trigger Term Quality

Comprehensive natural triggers users would actually say: 'upcoming meetings', 'daily or date-based meeting preparation', 'same-day customer call queue', 'most important qualifying meeting of the day', and identification 'by company, attendee, topic, or date'.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear sales/customer meeting-prep niche with distinct triggers (qualifying meetings, call queues, stakeholder prep) and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

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: 4 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.