event-planning
Help plan an event — from a birthday dinner to a wedding. Scales to the size of the occasion. Handles venue research, guest lists, timelines, vendors, and budgets.
72
65%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./examples/event-planning/SKILL.mdQuality
Discovery
67%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 does a good job listing specific capabilities and establishing a clear niche in event planning. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. Adding trigger guidance and a few more natural keyword variations would strengthen it significantly.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to plan an event, organize a party, or coordinate a celebration.'
Include additional natural trigger terms users might say, such as 'party planning', 'celebration', 'baby shower', 'corporate event', 'catering', or 'RSVP'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: venue research, guest lists, timelines, vendors, and budgets. Also specifies the range of events (birthday dinner to wedding) and notes scaling behavior. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the nature of the description, which per the rubric caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes natural terms like 'event', 'birthday dinner', 'wedding', 'venue', 'guest lists', 'budgets', and 'vendors', which are terms users would naturally say. However, it misses common variations like 'party planning', 'celebration', 'RSVP', 'catering', 'corporate event', or 'baby shower'. | 2 / 3 |
Distinctiveness Conflict Risk | Event planning is a fairly distinct niche. The combination of venue research, guest lists, timelines, vendors, and budgets clearly carves out a specific domain that is unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured conversational workflow skill with clear step sequencing and good use of validation checkpoints via ask_user_input_v0. Its main weaknesses are the lack of concrete output examples (invitation drafts, budget tracker formats, timeline templates) and some verbosity that could be trimmed. The tiered event complexity is a strong design choice, but the skill would benefit from supporting reference files for templates and examples.
Suggestions
Add concrete example outputs for key deliverables — e.g., a sample invitation draft, a budget tracker table format, and a day-of timeline template — so Claude knows exactly what format to produce.
Specify which tools to use for venue/vendor research (e.g., web search tool names) rather than the vague 'research options' instruction.
Extract the tiered checklists and output templates into separate referenced files (e.g., CHECKLISTS.md, TEMPLATES.md) to improve progressive disclosure and reduce the main file's length.
Trim tone/personality instructions to 1-2 sentences — Claude can infer 'be warm and creative' without the extended explanation about event planning not feeling like project management.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some unnecessary verbosity — e.g., the warm tone instructions ('event planning should feel exciting, not like project management') and some redundant phrasing. The checklist tiers are useful but could be tightened. It doesn't over-explain concepts Claude knows, but it's not maximally lean either. | 2 / 3 |
Actionability | The skill provides a clear process with specific steps and tool references (ask_user_input_v0), and the venue presentation format is well-specified. However, there's no executable code, no concrete example of an invitation draft or budget tracker format, and guidance like 'research options' is vague — it doesn't specify which tools to use for research or how to structure outputs like the budget tracker. | 2 / 3 |
Workflow Clarity | The 10-step workflow is clearly sequenced with logical progression from intake to execution to follow-up. It includes validation checkpoints (confirm via ask_user_input_v0 before booking/purchasing), error recovery (step 10 handles walls/alternatives), and appropriate feedback loops. The tiered complexity scaling is well-defined. | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to supporting materials. For a skill of this complexity — covering everything from birthday dinners to weddings — it would benefit from separating the tiered checklists, example invitation templates, and budget tracker formats into referenced files. However, the internal organization with numbered steps and bold headers provides decent structure. | 2 / 3 |
Total | 9 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- douglasvought/wiggle-skills
- Commit
b27906e
- 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.