CtrlK
BlogDocsLog inGet started
Tessl Logo

google-calendar-meeting-prep

Build a practical meeting prep brief from a connected Google Calendar event and its nearby context. Use when the user wants to prepare for an upcoming meeting, understand what to read beforehand, pull in linked notes or docs, or get a concise brief on what the meeting appears to require.

68

Quality

81%

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

72%Weight 40%Scale 1-3

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

A lean, well-organized body with clear sequencing and good section structure. It would reach top marks on actionability and workflow clarity by adding a sample action invocation and an explicit verify/confirm checkpoint.

Suggestions

Add one concrete example of calling `read_event`/`search_events` and a short sample prep-brief output so the guidance is copy-paste ready and fully actionable.

Insert an explicit checkpoint in the workflow, e.g. 'Confirm the event has attendees/attachments before deciding what to surface,' to lift workflow clarity to the top anchor.

Optionally note how to handle a missing or access-restricted event as a feedback loop, which would strengthen the sequence for edge cases.

DimensionReasoningScore

Conciseness

The body is lean (~25 lines) with no concept explanations or padding; each line assumes Claude's competence and earns its place.

3 / 3

Actionability

Concrete action names with clear conditions are present ('Use `read_event` or `read_event_all_fields` for the focal meeting', 'Use `search_events` when recurrence history...'), but there are no example invocations or a sample brief/output template, so it is not fully copy-paste ready.

2 / 3

Workflow Clarity

The five numbered steps are clearly sequenced, but there are no explicit validation checkpoints or feedback loops, which the top anchor requires even though the task is read-only.

2 / 3

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into clear sections (Relevant Actions, Workflow, Output Conventions), satisfying the simple-skill allowance for a top score.

3 / 3

Total

10

/

12

Passed

Description

90%Weight 40%Scale 1-3

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 concise, well-targeted description that clearly answers both what it does and when to use it, with natural trigger phrasing. It is slightly below top specificity only because it elaborates one core capability rather than listing several distinct concrete operations.

DimensionReasoningScore

Specificity

Names the domain and concrete actions ('Build a practical meeting prep brief', 'pull in linked notes or docs') but centers on one capability with elaboration rather than a list of multiple distinct concrete operations, so it stops short of the top anchor.

2 / 3

Completeness

It explicitly states what it does ('Build a practical meeting prep brief from a connected Google Calendar event and its nearby context') and follows with an explicit 'Use when the user wants...' clause covering the when.

3 / 3

Trigger Term Quality

Natural trigger phrases a user would say appear throughout ('prepare for an upcoming meeting', 'understand what to read beforehand', 'pull in linked notes or docs'), giving good coverage rather than a single keyword.

3 / 3

Distinctiveness Conflict Risk

Tied to a clear niche (Google Calendar + meeting prep brief) with distinct triggers, making overlap with unrelated skills unlikely.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
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.