CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

scheduling-coordination

Coordinate availability, confirmations, calendar changes, and participant notifications with read-back verification

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./resources/skills/communication/scheduling-coordination/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tight, well-structured instruction skill: a clear six-step sequence with an explicit read-back verification checkpoint, a pitfalls section guarding the risky failure modes, and no token waste. The only refinements would be naming the recovery action on verification mismatch and grounding a couple of the softer directives with examples.

DimensionReasoningScore

Conciseness

The ~40-line body is lean and assumes Claude's competence: directives like 'Compute candidate intervals in one explicit reference time zone and reject conflicts or insufficient travel buffers' convey constraints without explaining what calendars or time zones are. Every section (When to Use, Procedure, Pitfalls, Verification) earns its tokens, matching 'Lean and efficient; every token earns its place'.

5 / 5

Actionability

The guidance is concrete and executable for an instruction-only skill — step 6 names the exact fields to verify ('title, start, end, time zone, attendees, location, and conferencing details') and step 3 gives explicit rejection criteria. It falls short of 5 only because some steps stay at a directive altitude ('Present or draft a small set of viable options', 'using declared calendar and contact capabilities') without examples or parameters such as how many options or how to format the read-back.

4 / 5

Workflow Clarity

The six-step procedure is clearly sequenced with an explicit validation checkpoint (step 6 read-back) plus a dedicated Verification checklist, well above anchor 3. It does not fully match anchor 5 because the error-recovery feedback loop is implicit: nothing says what to do when the read-back mismatches the authorized details (only the pitfall 'Do not create duplicates when an existing event can be updated safely' hints at recovery).

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (no references/, scripts/, or assets/ exist in the bundle), and the body is organized into well-labeled sections (When to Use, Procedure, Pitfalls, Verification). Per the rubric's simple-skill guidance, this earns a 5 with just well-organized sections.

5 / 5

Total

18

/

20

Passed

Description

58%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 gives a concrete, multi-action picture of what the skill does, but omits any explicit 'Use when' trigger guidance and lacks the natural phrases users would actually say when they need scheduling help. Overall it reads as a competent capability statement with discovery-relevant gaps.

Suggestions

Add an explicit trigger clause, e.g. 'Use when scheduling or rescheduling meetings across multiple participants, calendars, or time zones.'

Include natural user phrases such as 'schedule a meeting', 'reschedule', 'find a time that works', and 'send calendar invites' so the skill matches how users actually phrase the request.

State the proposal step explicitly (e.g., 'propose candidate time slots') so the action list covers the full workflow, not just the confirmation and notification phases.

DimensionReasoningScore

Specificity

The description names several concrete actions — 'Coordinate availability, confirmations, calendar changes, and participant notifications with read-back verification' — comparable to the anchor example 'Extracts text from PDF files, fills forms, converts pages to images'. It is not a 5 because the actions are noun-phrase level ('coordinate availability') rather than fully concrete operations, leaving minor coverage gaps (e.g., proposing candidate times is only implied).

4 / 5

Completeness

The 'what' is clear (coordinate availability, confirmations, calendar changes, notifications, read-back verification), but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description, which caps completeness at 3 per the judging guidelines. It is above 2 because the 'what' is concrete and multi-part rather than vague.

3 / 5

Trigger Term Quality

Relevant keywords like 'availability', 'calendar', 'confirmations', and 'notifications' are present, but the most natural phrases a user would say — 'schedule a meeting', 'reschedule', 'find a time', 'send invites' — are entirely absent, matching the anchor 'Some relevant keywords but missing common variations or synonyms'. It does not reach 4 because the missing terms are the primary way users request this skill, not just a few edge synonyms.

3 / 5

Distinctiveness Conflict Risk

The multi-participant coordination framing with 'read-back verification' carves a fairly distinct niche, with only minor overlap risk against closely related skills (generic calendar-reading, email-drafting, or notification skills), matching 'Mostly distinct; minor overlap risk'. It is not 5 because terms like 'calendar changes' and 'notifications' could still collide with simpler calendar or messaging skills absent a distinct trigger phrase.

4 / 5

Total

14

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

odysseus-dev/odysseus

Path

resources/skills/communication/scheduling-coordination/SKILL.md

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.