AD outgoing
Find and book real-world things to do — restaurants, bars, concerts, comedy, museums, events, and activities — via natural-language search. The general entry point to Outgoing; use it for any "what should we do / where should we eat / what's on near me" request, or route to a narrower companion skill when the occasion is specific (date-night, kids-weekend, trip-planning, work-meetup, enjoy-nature, friends-hangout, meet-new-people, pet-friendly, stay-active, accessible-outings) or the user wants to buy tickets (book-tickets). Works in cities worldwide.
Find and book real-world things to do — restaurants, bars, concerts, comedy, museums, events, and activities — via natural-language search.
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (outgoing) differs from the folder (outgoing-event-discovery)
- 100Tools and files. No external tools needed
- 100Steps. 5 steps
- 100Execution cost. Instruction body is 839 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 557: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.