Events

Build a personal event system for tracking concerts, conferences, parties, appointments, and everything in between.

Security Scan

The skill's requests and runtime instructions match its stated purpose (personal event tracking); it is an instruction-only skill that creates and manages markdown files under ~/events/ and does not request credentials or install software.

Purpose & Capability

The name/description (personal event system) aligns with the instructions: creating ~/events/, organizing markdown event files, tracking RSVPs/confirmation numbers and surfacing upcoming events. No unrelated services, binaries, or credentials are requested.

Instruction Scope

The SKILL.md explicitly instructs the agent to create and manage files under ~/events/ (create directories and markdown files, read/write event entries). This is coherent with the purpose but does perform local filesystem writes in the user's home directory — worth noting for users who care about where data is stored.

Install Mechanism

No install spec, no code files, and no external downloads — lowest-risk model (instruction-only).

Credentials

No environment variables, credentials, or config paths are requested. The scope of access is limited to file operations implied by the instructions.

Persistence & Privilege

always is false and the skill does not request elevated or platform-wide privileges. It does expect to read/write its own workspace (~ /events/) but does not modify other skills or system configuration.

Assessment

This skill is instruction-only and appears to only create/manage markdown files in ~/events/. Before installing, decide whether you’re comfortable with the agent creating and writing files in your home folder. Avoid storing highly sensitive secrets (full payment card data, credentials) in those event files — confirmation numbers and ticket info may be stored in plain text. If you use cloud sync (Dropbox, iCloud, Google Drive), remember that event files may be synced to those services; consider using an unsynced local folder if you want tighter control. Finally, because the agent may be invoked autonomously (platform default), review what prompts/actions it will take before granting it ongoing write access to your filesystem.

Core Behavior

• User mentions event → offer to track it
• User planning event → help organize details
• User asks what's coming up → surface relevant events
• Create ~/events/ as workspace

File Structure

~/events/
├── upcoming/
│   ├── concerts/
│   ├── conferences/
│   ├── social/
│   └── appointments/
├── hosting/
├── past/
├── annual/
│   └── recurring.md
└── calendar.md

Event Entry

# radiohead-may.md
## Event
Radiohead — MSG

## Date & Time
May 15, 2024, 8:00 PM

## Venue
Madison Square Garden, NYC

## Tickets
Section 112, Row 8
Confirmation: TM-789456

## Logistics
Doors 7pm, meeting Jake at 6:30
No large bags allowed

Hosting an Event

# hosting/birthday-2024/
├── overview.md    # date, venue, status checklist
├── guests.md      # confirmed, pending, declined
└── details.md     # food, drinks, music, setup

Guest tracking:

## Confirmed (12)
- Sarah + 1
- Jake

## Pending (5)
- Tom — following up

## Declined (2)
- Amy — out of town

Annual Recurring

# recurring.md
## Birthdays
- Mom: March 22
- Dad: July 8

## Annual Events
- Company retreat: September
- Industry conference: March (register early)

Quick Calendar View

# calendar.md
## March 2024
- 5: Jake's birthday party
- 12-14: SXSW Austin
- 22: Mom's birthday

Multi-Day Events

# sxsw-2024/
├── overview.md    # dates, location, registration, travel
└── schedule.md    # day-by-day sessions and plans

What To Track

• Date, time, location
• Tickets/confirmation numbers
• Logistics (parking, doors, dress code)
• Who you're going with
• RSVPs when hosting

What To Surface

• "Concert next week — doors at 7pm"
• "Mom's birthday in 5 days"
• "Registration closes tomorrow"
• "15 confirmed for Saturday"

Progressive Enhancement

• Start: add upcoming events
• Add annual dates (birthdays, holidays)
• Track past events for memories
• Build hosting checklists

What NOT To Do

• Forget confirmation numbers
• Miss registration deadlines
• Lose track of RSVPs when hosting
• Skip logistics details