Getting a skill actually working
Downloading a skill is the easy part. These are short walkthroughs for the four assistants event teams actually use, plus how to publish your own, with the exact paths and the mistakes worth avoiding.
A skill is one markdown file. The only thing that changes is how each assistant wants to receive it.
Claude Code and Codex
use the file as-is, inside a folder
Claude.ai and ChatGPT
want that folder zipped before you upload
Publishing to eventskills
needs only the .md, no zip at all
Pick your assistant
Same skill file in every case. Only the place you put it changes.
Claude Code
Drop a skill folder into your skills directory and call it with a slash command.
Codex
Add a skill folder to the agents directory, then mention it with a dollar sign.
Claude.ai
Zip the skill folder, upload it under Customize, and Claude uses it in every chat.
ChatGPT
Upload a zipped skill under Plugins and ChatGPT uses it automatically when a request matches.
Publish to eventskills
One markdown file, a form that fills itself in, live in Browse immediately.
What a skill actually is
Worth thirty seconds if this is your first one.
It is just a file
A skill is a markdown file with a short block at the top saying what it does and when to use it. You can open it and read it before you run anything.
Your assistant decides when
That description is what your assistant matches against. Ask for something it covers and the skill gets pulled in without you naming it.
No integration project
Nothing to connect, no keys, no vendor review. Put the file in the right place and it works the next time you open a session.
Ready to try one?
Every skill in the directory is free, readable before you run it, and written by someone who runs events.