event-hosting
When the user wants to host a tech event, meetup, workshop, or community gathering — especially using Luma. Also use when the user mentions "host an event", "meetup", "workshop", "Luma event", or "community event".
75
70%
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/event-hosting/SKILL.mdQuality
Discovery
62%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description excels at trigger terms and distinctiveness, clearly identifying when it should be selected with natural user language and a specific platform (Luma). However, it critically fails to describe what the skill actually does — there are no concrete actions or capabilities listed, making it essentially a 'when' clause without a 'what' clause.
Suggestions
Add specific capability verbs describing what the skill does, e.g., 'Creates and publishes event pages on Luma, manages RSVPs, drafts event descriptions, and sets up registration workflows.'
Restructure to lead with concrete actions before the 'Use when...' clause, following the pattern: '[What it does]. Use when [triggers].'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description does not list any concrete actions or capabilities. It only describes when to use the skill (trigger conditions) but never states what the skill actually does — no verbs like 'creates', 'schedules', 'manages', or 'publishes' are present. | 1 / 3 |
Completeness | The 'when' is explicitly and thoroughly answered with clear trigger guidance. However, the 'what' — what the skill actually does — is entirely missing. There are no described capabilities or actions. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'host a tech event', 'meetup', 'workshop', 'Luma event', 'community event', 'community gathering', and 'host an event' are all phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around tech event hosting with Luma specifically. The combination of event types and the Luma platform makes it highly distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
77%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, highly actionable skill that provides concrete guidance for event hosting with Luma. Its main strength is the detailed output format template and specific Luma tips that add genuine value. The primary weakness is verbosity — some general event planning advice (common mistakes, general best practices) could be trimmed, and the lengthy content would benefit from splitting into a main overview and reference files.
Suggestions
Trim the 'Common mistakes' section and general best practices that Claude would already know (e.g., 'making it about your product instead of your audience's interests') to improve conciseness.
Move the detailed output format template and frameworks table into separate reference files (e.g., TEMPLATE.md, FORMATS.md) and link to them from the main skill to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some content that could be tightened — e.g., the 'Common mistakes' section and some best practices are general event planning wisdom that Claude likely already knows. The frameworks table and Luma-specific tips add genuine value, but the overall length (~150 lines) could be reduced without losing actionability. | 2 / 3 |
Actionability | The skill provides highly concrete, actionable guidance: specific event page copy structure, minute-by-minute run of show templates, promotion timelines with specific channels and actions, and detailed output format with markdown tables. The Luma-specific tips (1600x900px dimensions, Require Approval feature, co-hosts) are precise and immediately usable. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced from concept definition through follow-up, with each step containing specific sub-tasks. While this isn't a destructive/batch operation requiring validation checkpoints, the workflow includes natural checkpoints (define concept before writing copy, plan promotion before execution, prepare follow-up plan). The promotion plan includes a timeline working backward from the event date. | 3 / 3 |
Progressive Disclosure | The skill references related skills (community-discovery, founder-thought-leadership, etc.) which is good, but the main content is monolithic — the frameworks/best practices section, output format, and examples are all inline. The frameworks table and Luma tips could be separated into a reference file, and the detailed output template could be in a separate TEMPLATE.md to keep the main skill leaner. | 2 / 3 |
Total | 10 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- shawnpang/startup-founder-skills
- Commit
4ad31b4
- 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.