Kyndlo Events

kyndlo-events — Kyndlo Event Management

CRITICAL: This skill has MANDATORY step-by-step workflows for both event creation and event validation. You MUST follow the exact steps in order. Do NOT skip steps. Do NOT ask your own questions. Do NOT improvise. The workflow tells you exactly what to run and what to ask at each step.

STOP — Read This First

When this skill is invoked (user says anything like "create events", "kyndlo-events", "generate events", etc.):

If the user says "validate events", "check events", "review events", or "validation" — skip directly to the Event Validation Workflow section below.

For event creation:

1. Do NOT ask the user for city, date range, event style, theme, or any other freeform questions 2. Do NOT try to gather requirements conversationally — the workflow below handles that 3. DO immediately start at Step 1 below and follow every step in order 4. DO run the CLI commands shown — they provide the data you need 5. DO wait for the user's response where indicated before moving to the next step 6. DO always check for existing events before creating — duplicates waste resources

Events are created from campaign tasks stored in the Kyndlo database, not from user-provided descriptions. The system tells you what events to create. Your job is to follow the workflow.

Setup

npm install -g gokyn
export KYNDLO_API_TOKEN="kyndlo_..."
export GOOGLE_PLACES_API_KEY="..."   # Required for venue discovery via goplaces

All gokyn commands accept --token if the env var is not set. Add --json to any command for machine-readable output. goplaces is used for venue discovery (Google Places API). It must be installed and configured separately.

Step 1: Verify token

Action: Run this command immediately — do not ask the user anything first.

gokyn whoami --json

Confirm the token is valid. If it fails, help the user set KYNDLO_API_TOKEN.

Step 2: Show campaigns and ask the user to pick one

Action: Run this command:

gokyn task campaigns

Then say to the user: > "Here are the available campaigns: [show the list with name, state, progress, pending tasks]. Which campaign would you like to work on?"

STOP and wait for the user's reply. Extract the campaign name and state from their choice.

Step 3: Show cities and ask which to prioritize

Action: Run this command using the state from the campaign they chose:

gokyn task cities --state ""

Then say to the user: > "Here are the cities in [state]: [show city list with populations]. Which city would you like to prioritize? Say a city name, or 'any' to work through all cities."

STOP and wait for the user's reply. Handle:

Step 4: Ask about county preference

Say to the user: > "Would you like to focus on a specific county, or work through all of them? (By default, I'll focus on major city counties and skip rural counties. Say 'include rural' if you want those too.)"

STOP and wait for the user's reply. Handle:

Step 5: Ask batch size

Say to the user: > "How many events should I create before pausing to report results? (e.g. 5, 10, 20)"

STOP and wait for the user's reply. Store this as the batch size.

Step 6: Fetch event creation rules (MANDATORY — do not skip)

Action: Run this command:

gokyn task rules

Read the full output and internalize every rule. These rules come from the Kyndlo admin dashboard and govern venue selection, descriptions, formatting, images, and quality. You must follow them strictly for every event.

Step 7: Confirm and begin

Say to the user: > "Ready to start. Here's your configuration: > - Campaign: [name] > - State: [state] > - City: [specific city / rotating through all] > - County filter: [ignore rural (default) / include rural / specific county] > - Batch size: [N] events per batch > - Rules: Loaded > > Shall I begin?"

STOP and wait for confirmation. Only proceed to the Autonomous Loop after the user says yes.

Category Name Mapping

Task activityCategory values sometimes differ from activity titles in the database. Use this table when searching for the activity ID:

| Task activityCategory | Search Term for gokyn activity list --search | |---|---| | Specialty Niche Museums | Specialty & Niche Museums | | Yoga Classes | Wellness centers | | Restaurant/Cafes with Animal Encounters | Coffee with animal encounters | | Community Theaters | Theater lounges | | Craft Cafes | Craft cafés | | Beach/Boardwalks | Beach Boardwalks | | Food Trucks | Food truck parks | | Planetariums | Planetarium |

If the task category is not in this table, use it as-is for the search.

Day-of-Week Reference

When setting --recurrence-days, use these day numbers:

| Day | Number | |-----|--------| | Sunday | 0 | | Monday | 1 | | Tuesday | 2 | | Wednesday | 3 | | Thursday | 4 | | Friday | 5 | | Saturday | 6 |

Include a day ONLY if the venue is open that day. Omit closed days entirely.

State Timezone Reference

| State | Timezone | |-------|----------| | Colorado | America/Denver | | Florida | America/New_York | | New York | America/New_York |

The Autonomous Loop

Process tasks in batches. Each batch creates up to N events (the batch size from onboarding), then pauses to report results and ask the user whether to continue.

Important: If the loop exits early for any reason, run the Cleanup step to release any uncompleted tasks.

Before each batch: Refresh rules

At the start of every batch (including the first), fetch the latest rules:

gokyn task rules

Re-read and internalize. Rules may have been updated by the Kyndlo admin between batches.

City rotation (when city = "any")

Track the current city. When task next returns "count": 0 for the current city:

1. Get the city list: gokyn task cities --state "" --json 2. For each city (in order), check for pending tasks: gokyn task context --campaign --city "" --json 3. Skip "Rural" if the user said "ignore rural counties" 4. Use the first city with remaining pending tasks 5. If no cities have pending tasks, stop the loop

Rural filtering

When the user chose "ignore rural counties":

Step 1: Claim a task

gokyn task next --campaign  --city  --assign --name "" --json

Apply filters based on onboarding preferences:

If "count": 0:

Extract from tasks[0]: _id (taskId), county, activityCategory, cluster, state.

Step 2: Map the category

Check the Category Name Mapping table above. If the activityCategory matches a left-column entry, use the corresponding right-column search term. Otherwise use the category as-is.

Step 3: Find the activity ID

gokyn activity list --search "" --json

Extract the activity _id from the first matching result. If no results, try shorter/partial search terms. If still no match, skip the task with reason "Activity not found for category: \".

Step 4: Research a venue

Find a real venue matching the task's activityCategory in county, state. Use goplaces (Google Places API) as the primary discovery tool.

#### 4a. Search for candidates

goplaces search " in  County, " --json --limit 5 --region US

This returns up to 5 venues with place_id, name, address, rating, and open_now.

#### 4b. Get full details for the best candidate

goplaces details  --json

Extract from the response:

#### 4c. Validation gates

Before using a venue, verify ALL of these:

1. County match — The address must be in the task's county. If the address says a different city/county, reject it. 2. Hours exist — regular_opening_hours must be present. If None or missing, reject the venue. 3. Public & safe — Must be open to the public and suitable for first-time social meetups.

Convert hours to open day numbers (0=Sun through 6=Sat). Include a day ONLY if the venue is open that day.

#### 4d. Fallback

If goplaces returns no results or all candidates fail validation:

Collect for the chosen venue:

Step 5: Check for duplicate events (MANDATORY — do not skip)

Before creating an event, you MUST check if a venue already exists as an event:

gokyn event list --search "" --json

Duplicate detection rules:

If you searched 5 candidates and all were duplicates, do NOT continue searching indefinitely — skip the task.

Step 6: Create the event

Look up the timezone from the State Timezone Reference table. Format open days as comma-separated numbers for --recurrence-days.

gokyn event create \
  --title "" \
  --description "<2-3 sentence description per rules>" \
  --activity :1 \
  --start-date-time "2027-01-01T09:00:00Z" \
  --end-date-time "2028-01-01T23:59:00Z" \
  --timezone "" \
  --location-type physical \
  --location-place "" \
  --location-address "
" \
  --location-lat  \
  --location-lng="" \
  --recurring \
  --recurrence-frequency weekly \
  --recurrence-interval 1 \
  --recurrence-days "" \
  --is-public=false \
  --is-premium-only \
  --is-active=false \
  --price  \
  --price-currency USD \
  --booking-url "" \
  --json

CLI syntax notes:

Extract the eventId from the JSON response.

Step 7: Generate and upload an event image (MANDATORY)

Every event must have an image. Use one of the following methods:

#### Option A: Use Kyndlo's built-in AI image generation (preferred)

gokyn image generate \
  --prompt "A welcoming  with , inviting for casual social meetups. Inspired by  in , ." \
  --event-id 

This generates an image using the AI provider configured in the Kyndlo dashboard (e.g. Gemini, OpenAI), optimizes it, uploads to R2, and attaches it to the event — all in one step.

#### Option B: Generate externally and upload

If you have your own image generation tool (DALL-E, FAL, Stable Diffusion, etc.), generate the image yourself, then upload:

gokyn image upload --file /tmp/venue-image.jpg --event-id 
or from base64:
gokyn image upload --base64 "" --mime-type image/png --event-id 

#### Prompt guidelines (for either method)

If generation or upload fails, log the error and continue — the event is still valid without an image.

Step 8: Complete the task

gokyn task complete  --event-id  --venue ""

Step 9: Track progress

Increment the batch counter. Log:

[Batch B, Task T/N] COMPLETED:  in  County (/) — Event ID: 

If the task was skipped:

[Batch B, Task T/N] SKIPPED:  County /  — Reason: 

Step 10: Check batch completion

If the batch counter has reached the batch size (N), go to Batch Report. Otherwise, loop back to Step 1.

Batch Report

After completing each batch of N events, present a report to the user:

=== Batch  Report ===
Campaign:       
City:           
Batch size:     
Created:        
Skipped:        
Failed:         
Events Created:
  -  in  () — Event ID: 
  - ...
Skipped Tasks:
  -  /  — 
  - ...
Cumulative Totals (all batches):
  Created:   |  Skipped:   |  Failed: 

Then check remaining work:

gokyn task context --campaign  --city "" --json

Report how many tasks remain in the current scope. Then ask:

> "Batch complete. tasks remaining in . Continue with the next batch?"

Wait for the user's response.

gokyn task release 

gokyn task release-stale --minutes 60

=== Event Creation Session Summary ===
Campaign:       
State:          
Cities worked:  
Total batches:  
Total created:  
Total skipped:  
Total failed:   
All Created Events:
  -  in  () — Event ID: 
  - ...
All Skipped Tasks:
  -  /  — 
  - ...
All Failed Tasks:
  -  /  — 
  - ...

gokyn task skip  --reason "No qualifying venue found in  County for "

# Release a single task
gokyn task release 
Release all stale tasks (assigned more than N minutes ago)
gokyn task release-stale --minutes 60

# 1. Register the state with its counties
gokyn task register-state --state "New York" \
  --counties "New York,Kings,Queens,Bronx,Richmond,Nassau,Suffolk"
2. Check city/metro areas
gokyn task cities --state "New York"
3. Seed the campaign
gokyn task seed --campaign "newyork-2027" --state "New York" \
  --counties "New York,Kings,Queens,Bronx,Richmond" \
  --clusters-json '{
    "intellectual": ["History Museums", "Bookstore Cafes"],
    "visionary": ["Escape Rooms", "Comedy Clubs"],
    "protector": ["Yoga Classes", "Botanic Gardens"],
    "creator": ["Art Museums", "Pottery Painting Studios"]
  }'
4. Verify
gokyn task campaigns
gokyn task context --campaign "newyork-2027"

gokyn validation summary

gokyn validation next --assign --json

gokyn event get  --json

goplaces search " in  County, " --json --limit 3 --region US

goplaces details  --json

gokyn validation submit  --status valid

gokyn validation submit  --status invalid \
  --issues-json '[{"field":"","severity":"","description":"","currentValue":"","expectedValue":""}]'

gokyn validation submit  --status invalid \
  --issues-json '[
    {"field":"recurrence.daysOfWeek","severity":"error","description":"Venue now closed on Mondays","currentValue":"0,1,2,3,4,5,6","expectedValue":"0,2,3,4,5,6"},
    {"field":"price","severity":"warning","description":"Entry fee increased","currentValue":"$0","expectedValue":"$10"}
  ]'

gokyn validation submit  --status needs_update \
  --notes "Hours changed for summer season — now opens at 10am instead of 9am"

[Batch B, V/N] VALID:  in  County — no issues
[Batch B, V/N] INVALID:  in  County —  issues found
[Batch B, V/N] NEEDS_UPDATE:  in  County — 

gokyn validation submit  --status invalid \
  --issues-json '[{"field":"other","severity":"error","description":"Venue not found on Google Places — may be permanently closed"}]'

=== Validation Batch  Report ===
Processed:      
Valid:           
Invalid:        
Needs Update:   
Results:
  -  () — VALID
  -  () — INVALID: 
  - ...
Cumulative Totals (all batches):
  Valid:   |  Invalid:   |  Needs Update: 

gokyn validation summary

gokyn activity list --search "yoga" --limit 10
gokyn activity list --category "wellness" --json
gokyn activity get 
gokyn activity categories
gokyn event list --limit 10
gokyn event list --search "garden" --is-active --json
gokyn event get 

gokyn event update  --title "New Title"
gokyn event update  --is-active=false
gokyn event update  --price 25 --price-currency USD
gokyn event update  --activity :1 --activity :2
gokyn event update  \
  --location-type physical \
  --location-place "New Venue" \
  --location-address "123 Main St" \
  --location-lat 40.7 \
  --location-lng="-74.0"
gokyn event delete 

gokyn task states                      # List registered US states
gokyn task counties --state "Colorado" # List counties in a state
gokyn task cities --state "Colorado"   # List metro areas + rural breakdown

npm install -g gokyn
export KYNDLO_API_TOKEN="kyndlo_..."
export GOOGLE_PLACES_API_KEY="..."   # Required for venue discovery via goplaces

All gokyn commands accept --token if the env var is not set. Add --json to any command for machine-readable output. goplaces is used for venue discovery (Google Places API). It must be installed and configured separately.