Individual skill
conference-shared-calendar
Create or maintain a shared conference reference calendar from an official agenda, including sessions, side events, sharing permissions, timezone checks, and duplicate-safe updates. Use when a participant or team wants a shared event calendar or an importable agenda.
skills/ariel-cohen/conference-shared-calendar/SKILL.md
Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 237
- Repository last updated
- Oct 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- productivity Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,123 bytesSKILL.mdcore · 4,123 bytesSKILL.mdcore · 4,123 bytesSKILL.mdcore · 4,123 bytesSKILL.mdcore · 4,123 bytesSKILL.mdcore · 4,123 bytesagents/openai.yamlasset · 244 bytesassets/calendar-worksheet.mddoc · 776 bytesreferences/google-calendar.mddoc · 1,560 bytes
Read excerpt
# Shared conference calendar
Create a useful reference agenda that does not consume people's meeting availability.
## Establish the inputs
Use `assets/calendar-worksheet.md`. Reuse information already supplied. Ask only for missing facts that affect correctness: official source, event dates, venue IANA timezone, calendar owner/destination, and intended readers/editors. Never infer timezone from the operator's computer. Distinguish a private team calendar from a publicly shared event calendar.
Inspect the existing destination and prior imports before creating anything. Prefer an authorized existing calendar when it serves the purpose. Use a connector/API when available; otherwise use the authenticated browser. With no live access, prepare an ICS and exact setup instructions and label the live setup unfinished.
## Normalize the agenda
Read the official agenda and linked session details. Capture source ID, title, date, start/end, timezone, venue/room, speaker, source URL, and confidence. Retain concurrent sessions; this is a reference calendar, not one person's itinerary. Do not copy private notes into shared descriptions.