persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.
56
46%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/persona-event-coordinator/SKILL.mdQuality
Discovery
32%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 identifies the domain of event planning and lists three broad capability areas, but lacks the specificity and explicit trigger guidance needed for reliable skill selection. It has no 'Use when...' clause, which is a significant gap for completeness. The trigger terms are reasonable but not comprehensive enough to cover the variety of ways users might request event-related help.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about planning events, parties, conferences, weddings, or coordinating attendees and venues.'
Make capabilities more concrete by listing specific actions like 'create guest lists, send invitations, coordinate venue bookings, manage RSVPs, build event timelines'.
Include more natural trigger term variations such as 'party', 'conference', 'wedding', 'RSVP', 'venue', 'guest list', 'event coordination' to improve matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (events) and lists some actions (scheduling, invitations, logistics), but these are still fairly high-level categories rather than concrete specific actions like 'send RSVP reminders' or 'create venue comparison tables'. | 2 / 3 |
Completeness | Describes what the skill does (plan and manage events) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' portion is also fairly weak, warranting a score of 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'events', 'scheduling', 'invitations', and 'logistics' that users might naturally say, but misses common variations like 'party planning', 'RSVP', 'venue', 'calendar', 'conference', 'meeting coordination', or 'event management'. | 2 / 3 |
Distinctiveness Conflict Risk | The event planning domain is somewhat specific, but 'scheduling' could overlap with calendar or meeting scheduling skills, and 'logistics' is broad enough to conflict with project management or travel planning skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
60%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is concise and well-structured as an overview that delegates to other utility skills, but it lacks a coherent multi-step workflow for event coordination and provides no concrete examples of actual command invocations with parameters. The instructions read more like a feature list than an actionable playbook.
Suggestions
Add a numbered workflow sequence showing the typical event coordination flow (e.g., 1. Create calendar event → 2. Upload materials → 3. Send invitations → 4. Track RSVPs) with validation checkpoints between steps.
Include at least one concrete end-to-end example with actual command parameters, e.g., `gws calendar +insert --title 'Q3 Offsite' --location 'Building A' --attendee user1@example.com --attendee user2@example.com`.
Add verification steps such as confirming the calendar event was created before sending invitations, or checking RSVP counts before finalizing logistics.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every line provides actionable guidance without explaining what events, calendars, or invitations are. No unnecessary padding or concept explanations. | 3 / 3 |
Actionability | Provides specific command references (e.g., `gws calendar +insert`, `gws gmail +send`) but lacks concrete examples with actual parameters, sample invocations, or expected outputs. The instructions describe what to do at a high level but aren't copy-paste ready. | 2 / 3 |
Workflow Clarity | The instructions are a flat list of independent actions with no clear sequencing, no validation checkpoints, and no feedback loops. For event coordination—which is inherently a multi-step process involving scheduling, inviting, tracking RSVPs, and announcing—there's no defined workflow order or error handling. | 1 / 3 |
Progressive Disclosure | The skill appropriately serves as an overview, referencing prerequisite utility skills and specific workflows (e.g., `+meeting-prep`, `+file-announce`, `+weekly-digest`) as one-level-deep references. Content is well-organized into clear sections. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- googleworkspace/cli
- Commit
c7c6646
- 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.