Events
coreyhaines31/marketingskills
When the user wants to plan, run, sponsor, speak at, or get pipeline from events — webinars, conferences, trade shows, meetups, dinners, workshops, virtual summits, or user conferences.
Browse, search, and export public Luma events from one Go binary — no account, no API key Trigger phrases: events in sf, AI events this week, what's happening in nyc on luma, luma events near me…
$ npx skills add mvanhorn/printing-press-library --skill pp-luma -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mvanhorn/printing-press-library pp-luma --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-skills/pp-luma .claude/skills/pp-luma && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pp-luma" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-luma into .claude/skills/pp-luma/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-luma", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-lumaType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mvanhorn/printing-press-library --skill pp-luma -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mvanhorn/printing-press-library pp-luma --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cli-skills/pp-luma .agents/skills/pp-luma && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pp-luma" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-luma into .agents/skills/pp-luma/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-luma", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mvanhorn/printing-press-library --skill pp-luma -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mvanhorn/printing-press-library pp-luma --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cli-skills/pp-luma .cursor/skills/pp-luma && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pp-luma" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-luma into .cursor/skills/pp-luma/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-luma", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mvanhorn/printing-press-library.git --path cli-skills/pp-luma--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mvanhorn/printing-press-library --skill pp-luma -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mvanhorn/printing-press-library pp-luma --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cli-skills/pp-luma .gemini/skills/pp-luma && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pp-luma" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-luma into .gemini/skills/pp-luma/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-luma", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mvanhorn/printing-press-library pp-lumaInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mvanhorn/printing-press-library --skill pp-luma -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .github/skills && cp -r skills-src/cli-skills/pp-luma .github/skills/pp-luma && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pp-luma" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-luma into .github/skills/pp-luma/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-luma", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mvanhorn/printing-press-library --skill pp-luma -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mvanhorn/printing-press-library pp-luma --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cli-skills/pp-luma .opencode/skills/pp-luma && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pp-luma" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-luma into .opencode/skills/pp-luma/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-luma", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
pp-lumaBrowse, search, and export public Luma events from one Go binary — no account, no API key Trigger phrases: events in sf, AI events this week, what's happening in nyc on luma, luma events near me…
Pp Luma is an agent skill from mvanhorn/printing-press-library. Browse, search, and export public Luma events from one Go binary — no account, no API key Trigger phrases: events in sf, AI events this week, what's happening in nyc on luma, luma events near me, use luma, run luma.
Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Official library of CLIs generated by the CLI Printing Press. Endorsed, tested, and community-contributed. The licence is Apache-2.0.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 76de244. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadBashFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
goclaudenpxFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Pp Luma loads about 3k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 1,309 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, BashAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from mvanhorn/printing-press-library at commit 76de244, republished under its Apache-2.0 licence (© mvanhorn). 1,309 words, ~3,002 tokens.
.claude/skills/pp-luma/SKILL.md (or your agent's skills folder).<!-- GENERATED FILE — DO NOT EDIT.
This file is a verbatim mirror of library/social-and-messaging/luma/SKILL.md,
regenerated post-merge by tools/generate-skills/. Hand-edits here are
silently overwritten on the next regen. Edit the library/ source instead.
See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->
This skill drives the luma-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:
$HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:npx -y @mvanhorn/printing-press-library install luma --cli-onlyluma-pp-cli --version$PATH for the agent/runtime that will invoke this skill.If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer). This installs into $GOPATH/bin (default $HOME/go/bin), so add that directory to $PATH instead:
go install github.com/mvanhorn/printing-press-library/library/social-and-messaging/luma/cmd/luma-pp-cli@latestIf --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.
luma reads Luma's public discovery surface (api.luma.com) to list events by city and category, fetch full event and calendar details, and mirror it all into a local SQLite store. On top of the raw API it adds what Luma never exposed publicly: full-text search, geo-radius lookup, cross-city aggregation, change tracking, and ICS export — all agent-native with --json and --select.
Use luma when an agent needs to discover or report on public Luma events — what's happening in a city, events for a topic, full details for an event or community, or a calendar export. It is ideal for read-only event discovery, aggregation across cities, and tracking how events fill up over time.
Do not use this CLI for:
These capabilities aren't available in any other tool for this API.
agenda — One flat, date-sorted list of upcoming events across multiple cities and categories at once.
Reach for this when the user asks 'what AI events are on this week' across several cities — no single Luma call can answer it.
luma-pp-cli agenda --city sf --city nyc --category cat-ai --window 7d --agentnear — Find events within N km of a lat/lng, ranked by distance.
Use when the user wants events near a point or venue, which no Luma API call supports.
luma-pp-cli near --lat 37.77 --lng -122.42 --radius-km 5 --window 14d --agentics — Export a synced/filtered set of events to a .ics calendar file your calendar app can import.
Use when the user wants events on their own calendar instead of re-reading JSON.
luma-pp-cli ics --city sf --category cat-ai --window 30d --out ai.icswatch — Show what changed on synced events since the previous sync — new, removed, filling up, sold out, rescheduled.
Reach for this to monitor events over time; a single API call can never show change.
luma-pp-cli watch --city sf --category cat-ai --agentcalendars compare — Side-by-side upcoming-event counts and total guest counts across several calendars (communities).
Use to benchmark which communities are most active or drawing the biggest crowds.
luma-pp-cli calendars compare cal-AAA cal-BBB cal-CCC --window 14d --agentcalendars — Fetch Luma calendar (community) details
luma-pp-cli calendars — Get a calendar (community) by its api_id (cal-...)discover — Discover featured events, places, and categories on Luma
luma-pp-cli discover categories — List event categories (AI, Crypto, Tech, Arts, ...) with upcoming-event countsluma-pp-cli discover home — Featured place, popular places, categories, and calendars on the Luma discover homeevents — Browse and fetch public Luma events
luma-pp-cli events get — Get full details for an event by its api_id (evt-...)luma-pp-cli events list — List upcoming events filtered by city (--city/--place-id) or category (--category)places — Browse cities/places that host Luma events
luma-pp-cli places calendars — List calendars (communities) active in a placeluma-pp-cli places get — Get a place (city) by slug (sf, nyc, miami, ...) or place api_idluma-pp-cli places map — Geographic points for events in a place, for mappingWhen you know what you want to do but not which command does it, ask the CLI directly:
luma-pp-cli which "<capability in your own words>"which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.
luma-pp-cli events get --event-id evt-XXXX --agent --select api_id,event.name,event.start_at,event.timezone,guest_count,ticket_countEvent detail is large and deeply nested; --select pulls only the fields you need so an agent doesn't burn context.
luma-pp-cli agenda --city sf --city nyc --category cat-ai --window 7d --agentUnions several cities filtered to a category into one flat, date-sorted list the API can't return.
luma-pp-cli near --lat 37.77 --lng -122.42 --radius-km 5 --window 14d --agentHaversine radius search over synced event coordinates — no Luma endpoint offers this.
luma-pp-cli ics --city sf --out sf.icsWrites an ICS file you can import into any calendar app.
No account or API key required. luma reads Luma's public, read-only discovery API the website itself uses. It cannot create events, manage guests, or read private/subscribed calendars — that is the paid Luma Plus API's job.
Run luma-pp-cli doctor to verify setup.
Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.
Pipeable — JSON on stdout, errors on stderr
Filterable — --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:
luma-pp-cli calendars --calendar-id 550e8400-e29b-41d4-a716-446655440000 --agent --select id,name,statusPreviewable — --dry-run shows the request without sending
Offline-friendly — sync/search commands can use the local SQLite store when available
Non-interactive — never prompts, every input is a flag
Read-only — do not use this CLI for create, update, delete, publish, comment, upvote, invite, order, send, or other mutating requests
Commands that read from the local store or the API wrap output in a provenance envelope:
{
"meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
"results": <data>
}Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal AND no machine-format flag (--json, --csv, --compact, --quiet, --plain, --select) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout.
When you (or the agent) notice something off about this CLI, record it:
luma-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
luma-pp-cli feedback --stdin < notes.txt
luma-pp-cli feedback list --json --limit 10Entries are stored locally at ~/.local/share/luma-pp-cli/feedback.jsonl. They are never POSTed unless LUMA_FEEDBACK_ENDPOINT is set AND either --send is passed or LUMA_FEEDBACK_AUTO_SEND=true. Default behavior is local-only.
Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.
Every command accepts --deliver <sink>. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:
| Sink | Effect |
|---|---|
stdout | Default; write to stdout only |
file:<path> | Atomically write output to <path> (tmp + rename) |
webhook:<url> | POST the output body to the URL (application/json or application/x-ndjson when --compact) |
Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.
A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.
luma-pp-cli profile save briefing --json
luma-pp-cli --profile briefing calendars --calendar-id 550e8400-e29b-41d4-a716-446655440000
luma-pp-cli profile list --json
luma-pp-cli profile show briefing
luma-pp-cli profile delete briefing --yesExplicit flags always win over profile values; profile values win over defaults. agent-context lists all available profiles under available_profiles so introspecting agents discover them at runtime.
| Code | Meaning |
|---|---|
| 0 | Success |
| 2 | Usage error (wrong arguments) |
| 3 | Resource not found |
| 5 | API error (upstream issue) |
| 7 | Rate limited (wait and retry) |
| 10 | Config error |
Parse $ARGUMENTS:
help, or --help → show luma-pp-cli --help outputinstall → ends with mcp → MCP installation; otherwise → see Prerequisites above--agent)go install github.com/mvanhorn/printing-press-library/library/social-and-messaging/luma/cmd/luma-pp-mcp@latestclaude mcp add luma-pp-mcp -- luma-pp-mcpclaude mcp listwhich luma-pp-cli
If not found, offer to install (see Prerequisites at the top of this skill).--agent flag:luma-pp-cli <command> [subcommand] [args] --agentluma-pp-cli <command> --help.© mvanhorn, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in cli-skills/pp-luma of mvanhorn/printing-press-library.
Open the folder on GitHubat commit 76de244
Pp Luma next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pp Luma this skillmvanhorn/printing-press-library | 2.1k | — | ~3k | Automated safety check: Notes | Apache-2.0 | |
| Eventscoreyhaines31/marketingskills | 54k | — | ~3k | Automated safety check: Pass | MIT | |
| Luma Event Attendeesgooseworks-ai/goose-skills | 1.2k | 1 repos | ~1.7k | Automated safety check: Notes | MIT | |
| Event Sourcing Architectdavila7/claude-code-templates | 32k | 4 repos | ~659 | Automated safety check: Pass | MIT | |
| Event Store Designwshobson/agents | 40k | 9 repos | ~828 | Automated safety check: Pass | MIT | |
| KubeSphere WizTelemetry Eventskubesphere/kubesphere | 17k | — | ~1.8k | Automated safety check: Pass | Custom licence |
coreyhaines31/marketingskills
When the user wants to plan, run, sponsor, speak at, or get pipeline from events — webinars, conferences, trade shows, meetups, dinners, workshops, virtual summits, or user conferences.
gooseworks-ai/goose-skills
Find speakers, hosts, and guest profiles at conferences and events on Luma.
davila7/claude-code-templates
Expert in event sourcing, CQRS, and event-driven architecture patterns.
wshobson/agents
Designs event stores for event-sourced systems: requirements, a comparison of EventStoreDB, PostgreSQL, Kafka, DynamoDB and Marten, and stream and versioning practices.
kubesphere/kubesphere
Installs and configures the WizTelemetry Events extension for KubeSphere, which exports Kubernetes events for storage, with dependency checks and the event query API.
0xsline/OpenChatCut
A skill your agent uses when a OpenChatCut video editing or creation workflow needs export, render, download, share, final delivery, subtitle-file export, render choice, local-only asset handling…
mvanhorn/printing-press-library
Desktop automation through the real Rust agent-desktop CLI, published in Printing Press through a small bridge.
mvanhorn/printing-press-library
Search, browse, and download Google Fonts from the terminal via the gfonts CLI.
mvanhorn/printing-press-library
The free, offline Trigger phrases: search 1688 for, find a factory on 1688 for, wholesale price on 1688 for, who is the cheapest supplier on 1688 for, compare 1688 suppliers for, use 1688, run 1688.
mvanhorn/printing-press-library
Inspect known Activity Japan plan IDs or URLs, compare dated prices and sessions, check language-sitemap coverage, and hand off to canonical booking pages.
mvanhorn/printing-press-library
Every Admin By Request portal action, plus a local SQLite mirror of audit, events, inventory and requests for ad-hoc...
mvanhorn/printing-press-library
macOS screen capture, window recording, GIF conversion, and agent evidence bundles from the terminal.
Browse, search, and export public Luma events from one Go binary — no account, no API key Trigger phrases: events in sf, AI events this week, what's happening in nyc on luma, luma events near me…. Pp Luma is an agent skill from mvanhorn/printing-press-library. Browse, search, and export public Luma events from one Go binary — no account, no API key Trigger phrases: events in sf, AI events this week, what's happening in nyc on luma, luma events near me, use luma, run luma.
Pp Luma fits situations like: phrases: events in sf; AI events this week; whats happening in nyc on luma; luma events near me.
Run `npx skills add mvanhorn/printing-press-library --skill pp-luma -a claude-code`. Or copy the skill folder (cli-skills/pp-luma in mvanhorn/printing-press-library) into .claude/skills/pp-luma in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mvanhorn/printing-press-library --skill pp-luma -a codex`. Or copy the skill folder (cli-skills/pp-luma in mvanhorn/printing-press-library) into .agents/skills/pp-luma in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mvanhorn/printing-press-library --skill pp-luma -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pp-luma, .gemini/skills/pp-luma, .github/skills/pp-luma and .opencode/skills/pp-luma in your project.
Going by SKILL.md and its folder, Pp Luma needs the command-line tools its instructions call (go, claude and npx). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Bash.
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Pp Luma is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Pp Luma: Events (coreyhaines31/marketingskills, 54k stars), Luma Event Attendees (gooseworks-ai/goose-skills, 1.2k stars), Event Sourcing Architect (davila7/claude-code-templates, 32k stars) and Event Store Design (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mvanhorn (a GitHub user) maintains it in mvanhorn/printing-press-library, which has 2,056 GitHub stars. The repository holds 506 skills in this directory. The repository was last updated on October 9, 2026.
Source: mvanhorn/printing-press-library on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.