Jak używać
- Skopiuj polecenie instalacji i sprawdź źródła przed instalacją we własnym środowisku agenta.
- W oryginale sprawdź wymagane narzędzia, dane dostępowe i obsługiwane środowiska.
- Opisz dane wejściowe i oczekiwany rezultat; porównaj wynik ze źródłami.
npx skills add https://github.com/sugatoray/aiskills --skill meeting-agendaPrzed rozpoczęciem
- Instalacja nie obejmuje subskrypcji modelu, limitu API ani uprawnień do plików.
- Gwiazdki i instalacje pokazują aktywność, a nie niezależny test jakości lub bezpieczeństwa.
Treść z repozytorium z zachowaniem nagłówków, przykładów, kodu, tabel, linków i obrazów.
Meeting agenda
Build a timed slide deck from an agenda by filling the bundled template, then hand over one working HTML file. Never hand-edit the template for a single deck; the build script writes the agenda into it safely.
Leave README.md, CHANGELOG.md and meta/ for maintainers. Read meta/MAINTAINERS.md only when changing the template itself.
Invocation
/meeting-agenda [[agenda text, notes, or a path to a file]] with these options:
| Option | Default | Contract |
|---|---|---|
--title | Inferred from the request, else none | Meeting name shown top-left and as the page title. |
--total | Sum of item minutes | Target length in minutes. Use it to allocate missing item times (below). If items already carry minutes that don't add up to it, say so; don't silently rescale. |
--theme | aurora | Studio themes: aurora (default), observatory (black, mono, watch-dial timer), abyss (deep teal), editorial (light, serif; for bright rooms and projectors) signal (black, white, yellow; high contrast), clarity (light, calm, Apple-style; the timer on a raised card) or clarity-dark (the same in true black). Classic themes: indigo, midnight, ocean, daylight or contrast. If the user mentions a bright room or a projector, suggest clarity, editorial or daylight; for accessibility, signal or contrast. |
--output | meeting-agenda.html in the working directory | Path of the HTML file to write. |
--demo | Off | Return the bundled 30-minute demo deck exactly as it ships. See Demo below. |
With no agenda at all, ask for one. If the user asks for a demo or an example, treat it as --demo.
Demo (--demo)
Copy the bundled deck byte for byte. Don't build, edit or re-theme it:
python3 scripts/build_deck.py --demo -o meeting-agenda.htmlThe script refuses an agenda, --title or --theme alongside --demo (exit 2). If the user passed any, say they were ignored, and offer a custom build instead. Then skip to 4. Deliver: send the file, show the demo's five items (10 + 8 + 5 + 3 + 4 = 30 minutes), and give the controls line.
1. Turn the input into agenda JSON
{ "title": "Team Planning Meeting", "theme": "aurora",
"items": [
{ "minutes": 10, "title": "Priorities for 2026 & 2027",
"points": ["What are the priorities for 2026?", "What are the priorities for 2027?"] }
] }- One item per agenda topic, in the user's order. Use the user's wording for titles. Keep each title short (about 8 words or fewer) and move the detail into
points. - `points` holds the sub-items, one string each. Omit it, or use
[], when an item has none. Don't invent points; if the user gave none, there are none. - `minutes` must be > 0; 0.5 steps are typical (
7.5shows as 7:30). - Times given for every item: use them as given.
- Times given for some items plus a
--total: spread the remaining minutes across the untimed items, rounded to 0.5. State the times you chose. - No times anywhere: ask. If the user wants you to decide, propose times and say so in the summary.
- Don't add items the user didn't list (no surprise "Intro" or "AOB"). You may suggest them in your reply.
2. Build the deck
Write the JSON to a temporary file, then run the script from this skill's directory:
python3 scripts/build_deck.py agenda.json -o meeting-agenda.html --title "Team Planning Meeting" --theme aurora-reads the JSON from stdin, and--checkvalidates without writing.- Exit 2 means invalid input. The error names the item and the problem (
item 3: title is required). Fix the JSON and run it again. - The script copies
assets/meeting-agenda.htmland replaces only its<script type="application/json" id="agenda-data">block, escaping every<. Titles that contain HTML or</script>are safe. It printswrote <path>: N items, M:SS planned.
3. Verify
- Check that the printed item count and planned total match what you intended.
- If a browser tool or Playwright is available, open the file and check that the first slide shows
01and your first title, and that the footer readsMeeting: 0:00 used / <total> planned. - Run the bundled suite (
python3 -m pytestin this directory) only if you changed the template or the script.
4. Deliver
Give the user:
- The HTML file (send it or link it; don't paste its source).
- A short table of the items (number, minutes, title) and the planned total. Point out any times you chose for them.
- The controls in one or two lines. Keyboard:
→/PgDnnext,←/PgUpback,Home/End,SpaceorPpause/resume,Rreset. Phone: swipe or tap (right side forward, left side back), hold to pause,‹ ›buttons. The gear edits the agenda: Apply remembers it in that browser, and Save HTML downloads an updated copy.
What the deck does (for answering questions)
- Slides: one per item, with a large two-digit number, the title, and the sub-points. Above the number, a cyan label reads "Agenda item 3 of 5 · 5 min". The default theme, Aurora, has a slowly drifting violet aurora, a glass dial and a "live" label; eleven other themes are a click away. Adapts to any number of items and any lengths. The "Agenda item N of M" line stays at the same height on every slide, so switching slides doesn't make the text jump.
- Timers: each slide has a violet-to-cyan ring countdown, captioned "of M:SS allotted",, that starts when the slide is shown and pauses when you leave it. It turns amber in the last 20% of the item's time, then red, pulsing and counting up (
+M:SS) past zero.SpaceorPpauses/resumes (like a video player), andRresets; the buttons do the same. - Footer: keyboard hints, clickable progress dashes (one per item, each filling with that item's time), a progress bar, then
Meeting: M:SS used / M:SS planned. The bar has one section per item, each filling with the time spent on that item. The bar turns amber at 80% of the planned total and red past it, and its tooltip shows the percentage used. - Phones and tablets: swipe left/right for next/previous, tap the right 70% / left 30% of the slide, long-press (½ s) to pause or resume, and
‹ ›buttons beside the progress dashes. Touch targets are at least 44 px, and the layout scales down to fit a phone. Mouse clicks on the slide don't navigate. - Settings (gear): two tabs.
- Contents: the deck title (shown top-left and as the page title; may be blank), a running total, and two views of the same draft. Quick View (default) is one list with inline title, sub-points and minutes, and ↑ ↓ ✕ on hover or focus. Detailed View has the item list on the left and the selected item on the right, with a −/+ minutes control, 5/10/15/30 quick picks and one line per sub-point. The last item can't be removed.
- Theme: twelve themes as preview cards: seven studio themes (Aurora, Observatory, Abyss, Editorial, Signal, Clarity, Clarity Dark), then the five classics (Indigo, Midnight, Ocean, Daylight, High contrast). Clicking one previews it live.
- Shared buttons: Reset to defaults (asks first), Cancel/Esc/× (discard changes, including a previewed theme), Save HTML (the agenda and theme go into the copy), and Apply or Ctrl/⌘+Enter (saved in the browser).
- Items without a title or with minutes ≤ 0 get a red edge and a short message, the footer counts them, and they block Apply and Save. While Settings is open the timer pauses and keys don't change slides.
- Offline and private: no network requests, and agenda text is never parsed as HTML. See
meta/SECURITY.md.