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 provides a reasonable high-level summary of event planning capabilities but lacks the specificity and explicit trigger guidance needed for reliable skill selection. It names the domain and a few action categories but doesn't enumerate concrete actions or include a 'Use when...' clause, making it harder for Claude to confidently select this skill over related ones.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'Use when the user asks about planning events, parties, conferences, coordinating RSVPs, booking venues, or managing event logistics.'
List more specific concrete actions such as 'create guest lists, send invitations, coordinate venue bookings, manage RSVPs, plan event timelines, and track budgets.'
Include common user-facing synonyms and variations like 'party planning', 'conference organization', 'RSVP tracking', 'venue selection', and 'event coordination' to improve trigger term coverage.
| 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 spreadsheets'. | 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, effectively referencing external utility skills and workflows. However, it lacks concrete examples with actual parameters and fails to sequence the multi-step event coordination process with validation checkpoints, which significantly reduces its actionability and workflow clarity.
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. Verify RSVPs) with explicit validation steps between stages.
Include at least one concrete, copy-paste-ready example showing a full event creation command with real parameters (e.g., `gws calendar +insert --title 'Q3 Offsite' --location 'Building A' --attendee user1@example.com --attendee user2@example.com`).
Add a verification step such as checking calendar entry existence or confirming invitation delivery after sending emails.
| 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 executable examples — no sample command invocations with actual parameters, no example event creation workflow with real arguments. | 2 / 3 |
Workflow Clarity | The instructions are a flat list of independent actions with no sequencing, no validation checkpoints, and no feedback loops. Event coordination is inherently multi-step (create event → prepare materials → send invitations → track RSVPs) but no ordering or verification is provided. | 1 / 3 |
Progressive Disclosure | Content is well-organized with clear sections (Relevant Workflows, Instructions, Tips) and references to external workflows and utility skills without nesting. The skill serves as a concise overview pointing to specific tools. | 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 | |
a3768d0
Table of Contents
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.