Menu

Individual skill

devday-guide

0upvotes

Help with OpenAI DevDay attendance, onsite logistics, session schedules, personal plans, livestreams, recordings, and DevDay Exchanges. Use for DevDay-specific questions, not general OpenAI API or app development.

OpenAI/Codex/plugins/openai-developers/skills/devday-guide/SKILL.md

Read pinned source

Source commit a2d33761e49b98f6ec1b48f12143264eb9b4ff4f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 10, 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)
71,172
Repository last updated
Nov 10, 2026
License
CC0-1.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# DevDay Guide

Help the user attend, follow, or learn from DevDay. Public event questions do not require an API key, Platform account connection, or developer onboarding.

## Verify event information

- Start with [the official DevDay site](https://devday.openai.com/) for the program, attendance FAQ, livestream, recordings, and accessibility information. For regional events, use [DevDay Exchanges](https://events.openai.com/devdayexchange2026) and official links from the DevDay site.
- Match the requested year and city. If a landing page has rolled over to another event, find an official page for the requested edition rather than substituting the latest agenda.
- For onsite questions about September 29, 2026 in San Francisco, read [the bundled attendee guide](references/devday-2026-attendee-guide.md). It contains dated logistics from the event guide, not a live agenda. Use it for check-in, wayfinding, meals, activities, and attendee services; prefer newer official event communications and onsite signage when details change.
- Check current public sources for session schedules, speakers, ticket availability, livestreams, and recordings, and cite the relevant pages. If a detail is only in the bundled guide, attribute it to the September 27 attendee-guide snapshot rather than implying it was verified on the website. Say when a current detail cannot be verified; do not fill gaps from memory.
- Apart from the curated bundled attendee guide, use public, unauthenticated sources for event facts, not employee-only repositories, Slack, Drive, planning documents, or previews. Do not fetch the source planning document at runtime. User-provided registration details can inform their own answer, but are not public event information.
- Preserve the published date, time zone, and overlapping sessions. A programming window is not a list of individual talks, and a venue address does not establish a check-in entrance or room map.

## Shape the answer to the request
Back to top