From file to useful result
How to ask with this skill installed
Installing the skill gives your AI a method. Your request still has to provide the case-specific facts, constraints and expected output.
1Name the real task
Describe the decision or deliverable, not just the topic.
2Provide the evidence
Add source material, audience, limits and known facts.
3Define done
Set format, quality criteria and checks.
Source example
Replace the brackets with your case
When to use it
- Investigating why revenue is down despite full reservations
- Analyzing table turn times to increase covers without rushing guests
- Identifying which tables or sections are most/least productive
- Planning staffing levels for a new service
- Diagnosing why a particular server's covers are low
- Running a RevPASH analysis for a specific day part or week
Mistakes to avoid
- Optimizing table turns at the expense of guest experience — a 60-minute turn on a 4-top that needs 90 minutes for a birthday dinner will lose future revenue in a complaint; turns are averages, not mandates
- Not tracking turn time by table size — a 2-top always takes longer per person than an 8-top; comparing raw turn times without normalizing for party size is misleading
- Running too many covers in the first seating without thinking about second seating — if every table orders at 6:30 PM, the kitchen collapses at 7 PM regardless of how fast the host can seat them; staggered seating (e.g., reservations at 6:00 and 7:30) prevents kitchen surges
- Not having a closing table protocol — when the last reservation is at 9 PM, the staff naturally slows down because they know they're closing; a structured closing protocol prevents the 10-15 minutes of revenue lost in the final table's turn