CtrlK
BlogDocsLog inGet started
Tessl Logo

outlook-calendar-free-up-time

Find ways to open up meaningful free time in Outlook Calendar. Use when the user wants to clear part of their schedule, make room for focus time, create a longer uninterrupted block, or see the smallest set of calendar changes that would give time back.

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

87%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 tight, highly actionable instruction-only skill that respects token budget and is cleanly sectioned. The main gap is workflow_clarity: while the sequence and an update-gate checkpoint are present, it lacks an explicit validate-and-recover feedback loop for the event-modification step.

Suggestions

Add an explicit verification/feedback step to the Workflow, e.g., after proposing moves, confirm the target block is contiguous and the moved events still resolve before applying, and on failure re-run find_available_slots — this would lift workflow_clarity from 2 to 3.

Make the update_event gate a numbered checkpoint in the Workflow rather than only a bullet under Relevant Actions, so the validation step is unmissable in the main sequence.

DimensionReasoningScore

Conciseness

The body is lean and well-organized with no padding or explanation of concepts Claude already knows (it never explains what Outlook or a calendar is); every line provides actionable guidance, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

It names specific tool operations (list_events, fetch_event, find_available_slots, get_schedule, update_event) with concrete decision rules ('Treat Tentative, Free, self-created placeholders... as lower-cost candidates') and explicit output conventions; per the scoring notes, absence of code in an instruction-only skill is not penalized when guidance is this actionable.

3 / 3

Workflow Clarity

An 8-step Workflow is clearly sequenced and includes a checkpoint ('Use update_event only after the proposal is grounded and the intended event is unambiguous') and a before-and-after verification, but there is no explicit error-recovery feedback loop (validate -> fix -> retry) that the score-3 anchor requires for multi-step modification workflows.

2 / 3

Progressive Disclosure

The skill is under 50 lines, has no bundle files and no need for external references, and is organized into clearly labeled sections (Relevant Actions, Workflow, Prioritization Heuristics, Output Conventions), which per the scoring notes lets progressive disclosure score 3.

3 / 3

Total

11

/

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 well-constructed description with explicit what-and-when structure, natural trigger phrasing, and a clear niche. The only weakness is that the stated capability is a single abstract goal rather than a list of several concrete actions, which limits the specificity dimension.

Suggestions

Lead with a brief enumeration of concrete actions the skill performs (e.g., 'Identify movable meetings, propose the smallest edit set, and surface before-and-after block comparisons') before the trigger clause to lift specificity from 2 to 3.

DimensionReasoningScore

Specificity

The description names the domain ('Outlook Calendar') and the goal ('Find ways to open up meaningful free time') plus concrete scenarios ('clear part of their schedule, make room for focus time, create a longer uninterrupted block'), but it centers on one abstract action rather than a comprehensive list of multiple distinct concrete operations like the score-3 anchor ('Extract text and tables from PDF files, fill forms, merge documents').

2 / 3

Completeness

It explicitly answers both what ('Find ways to open up meaningful free time in Outlook Calendar') and when ('Use when the user wants to...') with an explicit trigger clause, matching the score-3 anchor; the description uses 'the user' (third person) and the standard 'Use when' pattern, so no voice penalty applies.

3 / 3

Trigger Term Quality

The 'Use when the user wants to clear part of their schedule, make room for focus time, create a longer uninterrupted block, or see the smallest set of calendar changes' phrasing covers natural terms users would actually say, matching the score-3 'good coverage of natural terms' anchor.

3 / 3

Distinctiveness Conflict Risk

It targets a clear niche (freeing up time in Outlook Calendar via schedule edits) with distinct triggers, making it unlikely to fire for unrelated skills.

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.