feat: improve meeting-scheduler skill score (86% → 90%)

[yogesh-tessl]

Hey @lorilynsuperhuman 👋

this is seriously impressive. 5 skills covering everything from morning briefings to deal tracking, that's a really practical set. The way each one maps to a specific email workflow makes it clear you've thought about how people actually use their inbox.

Iran your skills through tessl skill review at work and found some targeted improvements for meeting-scheduler. Here's the before/after:

Skill	Before	After	Change
meeting-scheduler	86%	90%	+4%

What changed in meeting-scheduler

• Expanded frontmatter description with concrete capability listing - now explicitly names contact resolution, cross-timezone availability checking, conflict detection, recurring meeting creation, and focus time blocking instead of relying on trigger phrases alone (Description: 90% → 100%)
• Removed redundant "Important guidelines" section - every rule there (verify identity, confirm before booking, include user on invite, respect working hours, follow personalization settings) was already stated inline in the workflow steps
• Trimmed introductory paragraphs - removed generic framing ("You are a scheduling assistant…") that added tokens without value since the workflow steps are self-explanatory
• Tightened parameter documentation - shortened verbose explanations while keeping all MCP tool calls, parameter names, and format requirements intact
• Folded recurrence field into Step 4a (direct booking) instead of a separate guideline, making it discoverable where it's actually used
• Used quoted string format for the frontmatter description field

---

also stress-tested your meeting-scheduler skill against a few real-world task evals and it held up really well on cross-timezone scheduling with multi-participant availability filtering. Kudos for that.

quick honest disclosure. I work at https://github.com/tesslio where we build tooling around skills like these. Not a pitch, just saw room for improvement and wanted to contribute.

if you want to self-improve your skills, or define your own scenarios to pressure test, just ask your agent (Claude Code, Codex, etc.) to evaluate and optimize your skill with Tessl. Ping me @yogesh-tessl, if you hit any snags.

[yogesh-tessl]

hey @lorilynsuperhuman, just resurfacing this in case it slipped by, let me know if any changes are needed!
Understand if there's a queue, take your time.