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.

72

Quality

88%

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

77%

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-sequenced meeting-prep skill with concrete templates and validation checkpoints. Its main weaknesses are a verbose, repetitive Automation Offer Guard section and a monolithic structure with no progressive disclosure into bundled reference files.

Suggestions

Tighten the Automation Offer Guard: collapse the repeated value-framing, read-only constraints, and matching rules into a single concise checklist to reduce token cost.

Extract the two mode output-format templates (Single Meeting Prep, Daily Prep Digest) into separate reference files under ./references and link to them one level deep, leaving a concise overview in SKILL.md.

Consolidate the duplicated '{Follow the instructions...}' Next Steps / Limitations pointers so each appears once rather than repeating the cross-reference after every output template.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's competence, but the Automation Offer Guard section repeats the same framing (value, read-only constraints, matching logic) across multiple paragraphs that could be tightened without losing clarity.

2 / 3

Actionability

Provides concrete, executable guidance: specific search parameters ('next 3 business days, 25 max results'), literal output-format templates per mode, and a copy-paste automation prompt block with named fields.

3 / 3

Workflow Clarity

Sequenced workflow (Resolve Dependencies and Clarify → rank/select → draft → next steps) with explicit checkpoints such as 'If no credible anchor exists, state the gap' and 'If context is missing, stale, or conflicting, state the limitation'.

3 / 3

Progressive Disclosure

A single ~180-line file with no bundled reference files in ./references or ./scripts; the two detailed output templates are inline and the only references point to an external plugin index skill rather than one-level-deep references for this skill's own detail.

2 / 3

Total

10

/

12

Passed

Description

100%

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, well-structured description with an explicit 'Use when' trigger, concrete deliverables, and natural user phrasing. It clearly distinguishes the skill's purpose and scope from generic calendar or document skills.

DimensionReasoningScore

Specificity

Names multiple concrete outputs — 'Produce an individual meeting brief or a chronological multi-meeting agenda' — matching the anchor that lists specific concrete actions rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Produce an individual meeting brief or a chronological multi-meeting agenda') and when via a leading 'Use when...' clause with enumerated trigger conditions.

3 / 3

Trigger Term Quality

Covers natural phrasings a user would say ('prepare for one or more upcoming meetings', 'organize a same-day customer call queue', 'most important qualifying meeting of the day'), with good breadth of common variations.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear sales-meeting-prep niche with distinct triggers (qualifying meetings, customer/prospect/partner/renewal context) unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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