メニュー
Fill an Obsidian trip note (created from the Trip Notes template) with flights, lodging, and a day-by-day outline. Use when populating a trip-notes note with booking details or an itinerary.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/andweeb/dotfiles --skill trip-notesコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Extract flight details from PDF confirmation files and generate formatted Markdown for Obsidian trip notes. Use when processing airline booking confirmations.
Generate an .ics calendar file for flights that imports cleanly into Fantastical (or any calendar). Use when the user wants flight legs added to their calendar, an ics/ical file for a flight, or a booking put on Fantastical.
Rewraps PS Vita NoNpDrm dump ZIP files so RomM + Argosy Launcher + Vita3K ZX can install them — ensures the Title-ID folder sits at the ZIP root and the filename carries the Title ID in brackets. Use when preparing PS Vita ROM zips for a self-hosted RomM library.
| name | trip-notes |
| description | Fill an Obsidian trip note (created from the Trip Notes template) with flights, lodging, and a day-by-day outline. Use when populating a trip-notes note with booking details or an itinerary. |
| argument-hint | <trip-note-path> [source files: flight/lodging PDFs] |
Populate a trip note (frontmatter type: trip-notes) with the non-deterministic
content the template leaves blank: flights, lodging, and a rough outline. Read
the note's frontmatter (start-date, end-date, destinations) as the input
contract, and always show proposed Markdown before writing into the note.
Delegate to the flight-extract skill for each PDF/email confirmation. Insert
the returned Markdown under the note's ### Flights heading (one #### block
per leg). Do not re-implement extraction — call flight-extract.
Format each lodging confirmation into a block under ### Lodging:
:fab_airbnb: [[Property Name]]
:luc_map_pin: [Full Address](maps-url-if-available)
- [Email Confirmation](url-if-available)
- Booking ID: **[id]**
- Check in: **[Full Day Name] [Month] [Date], [Year]** (after [time])
- Check out: **[Full Day Name] [Month] [Date], [Year]** (before [time])
Group multiple stays under ### Lodging, one block each, in date order. Omit
lines whose data is absent (no placeholders).
Draft a day-by-day scaffold under ## Rough Outline spanning start-date to
end-date, one bullet per day, seeded from the destinations and any context the
user pastes (group chat, ideas). Leave each day light for the user to fill:
## Rough Outline
- **[Month] [Date]:** arrival — [city]
- **[Month] [Date]:** [activity placeholder]
Match flight-extract: bold confirmation codes and date/times, 12-hour time
with AM/PM, full day names, omit absent fields. Always present proposed Markdown
in a fenced ```markdown block first, then ask before writing into the note.