Detalle del Skill
travel-plan-spreadsheet-generator
Useful when an editable travel-planning workbook is requested, but not for general planning.
Revisar antes de usar
La revisión automática comprueba relevancia, no seguridad ni respaldo. Lee las instrucciones de la fuente antes de usar este Skill.
SKILL.md
Este extracto es una copia guardada durante la revisión. La fuente externa contiene la versión completa y actual.
--- name: travel-plan-spreadsheet-generator description: "Create .xlsx travel workbooks with itinerary, preparation, or shopping sheets for trip, holiday, or conference planning. Skip prose itineraries, recommendation chat, and calendar-only scheduling." compatibility: "Requires: python3 with openpyxl. Optional: @oai/artifact-tool or an equivalent spreadsheet renderer for visual verification." references: - workbook-spec - intake-protocol - research-policy - trip-model - mapping-rules - gotchas - cross-harness-notes --- # travel-plan-spreadsheet-generator Turn messy travel inputs into a calm, editable `.xlsx` workbook with deterministic structure and pragmatic trip-planning judgment. ## Decision Tree What did the user actually ask for? - The user wants an editable workbook, spreadsheet, tracker, or `.xlsx` Use this skill. - The user gave PDFs, screenshots, notes, bookings, shopping asks, or conference constraints Extract everything you can first. Do not ask questions that the attachments already answer. - The request is missing material facts that would make the workbook wrong Ask exactly one consolidated intake batch. Group it as `Required to proceed`, `Useful but optional`, and `Documents or screenshots that would improve accuracy`. Read `references/intake-protocol.md`. - The request has non-blocking ambiguity Proceed with explicit assumptions and visible review flags. Do not stop the build just to perfect every detail. - The user only wants prose, lightweight recommendations, or a casual itinerary chat Do not use this skill as the primary tool. - You are in an OpenAI or Codex-style environment and `/home/oai/skills/spreadsheets/SKILL.md` exists Read that file before spreadsheet work, then continue with this skill's workbook-specific rules. ## Quick Reference | Need | Read or run | Why | | --- | --- | --- | | One-batch intake discipline | `references/intake-protocol.md` | Prevent drip-fed questioning | | Deterministic workbook contract | `references/workbook-spec.md` | Sheet order, widths, merges, formulas, palette | | Canonical trip model fields | `references/trip-model.md` | Build the internal model before writing cells | | Field-to-sheet mapping | `references/mapping-rules.md` | Keep Pack vs Buy vs Prep clean | | Volatile travel research rules | `references/research-policy.md` | Verify visas, transit, medicine, conference dates, and other unstable facts | | Build the workbook | `python3 scripts/build_workbook.py --trip-model /path/to/model.json` | Generate the `.xlsx` artifact | | Validate the workbook | `python3 scripts/validate_workbook.py /path/to/output.xlsx --trip-model /path/to/model.json` | Check structure, formulas, validations, and row patterns | | Visual-risk scan | `python3 scripts/render_check.py /path/to/output.xlsx` | Catch likely clipping or spillover when a renderer is unavailable | | Review packaging and sample build | `python3 scripts/test_skill.py /path/to/skill` | Run the local functional smoke test | ## Operating Rules 1. Start with extraction, not interrogation. Read the user's PDFs, screenshots, pasted notes, flight details, hotel confirmations, shopping asks, and fixed commitments before asking anything. 2. Separate blockers from non-blockers. If essential trip facts are still missing, ask one consolidated clarification batch and only one batch unless the user later changes scope. 3. Build a canonical trip model before touching the workbook. Use `templates/trip_model_schema.json` and `references/trip-model.md`. 4. Keep the deterministic and heuristic layers separate: - Use `scripts/build_workbook.py` for filename strategy, sheet order, merges, widths, formulas, validations, fills, fonts, borders, and fixed row patterns. - Use judgment for extracting messy facts, reconciling contradictions, deciding pace, keeping shopping visible, pruning absurd plans, and deciding when split plans are required. 5. Default to the whole group staying together unless the eLeer la fuente completa en GitHub (abre una página externa)