Atlas / Skills / revfactory / Travel Planner

Travel PlannerSAFE

skills/revfactory/travel-planner
Verdict
SAFE
Grade
B
Trust score
89 /100
Version
—
Hosts
—
License
Apache-2.0
Stars
1,297
01

Overview

An agent skill published by revfactory.

Read from source at commit 459e1bb8f76eOBSERVED · 2026-10-12
02

What it tells the agent

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: travel-planner
description: "A full pipeline where an agent team collaborates to generate everything from destination analysis to local information for travel planning. Used for 'plan a trip', 'Japan travel itinerary', 'Europe backpacking', 'weekend getaway', 'international travel prep', 'travel budget', 'accommodation recommendations', 'travel itinerary', 'local restaurants', 'travel route recommendations', etc. Supports analysis or improvement of existing itineraries. Real-time flight/accommodation booking, visa application processing, and travel agency package comparisons are outside this skill's scope."
---

# Travel Planner — Travel Planning Full Pipeline

Generates destination analysis, itinerary, accommodation, budget, and local information through agent team collaboration in one go.

## Execution Mode

**Agent Team** — 4 agents communicate directly via SendMessage and cross-verify.

## Agent Composition

| Agent | File | Role | Type |
|-------|------|------|------|
| destination-analyst | `.claude/agents/destination-analyst.md` | Destination research, attractions, safety info | general-purpose |
| itinerary-designer | `.claude/agents/itinerary-designer.md` | Daily itinerary, route optimization, accommodation | general-purpose |
| budget-manager | `.claude/agents/budget-manager.md` | Budget calculation, cost comparison, savings tips | general-purpose |
| local-guide | `.claude/agents/local-guide.md` | Transport, restaurants, culture, emergency info | general-purpose |

## Workflow

### Phase 1: Preparation (Orchestrator performs directly)

1. Extract from user input:
    - **Destination**: Country/City (recommend based on criteria if undecided)
    - **Duration**: How many days, departure/arrival dates
    - **Party**: Solo/Couple/Family/Friends + number of people
    - **Budget** (optional): Total budget or budget level (Budget/Standard/Luxury)
    - **Travel Style** (optional): Relaxation/Adventure/Cultural/Culinary
    - **Special Requests** (optional): Must-visit places, exclusions
2. Create `_workspace/` directory at project root
3. Organize inputs and save to `_workspace/00_input.md`
4. **Determine execution mode** based on request scope

### Phase 2: Team Assembly and Execution

| Order | Task | Owner | Dependencies | Deliverable |
|-------|------|-------|-------------|-------------|
| 1 | Destination Analysis | analyst | None | `_workspace/01_destination_analysis.md` |
| 2 | Itinerary + Accommodation | designer | Task 1 | `_workspace/02_itinerary.md`, `_workspace/03_accommodation.md` |
| 3a | Budget Plan | budget | Tasks 1, 2 | `_workspace/04_budget.md` |
| 3b | Local Information | guide | Tasks 1, 2 | `_workspace/05_local_guide.md` |

Tasks 3a (Budget) and 3b (Local Info) run **in parallel**.

**Inter-team communication flow:**
- analyst complete → transmit attractions/time/hours to designer, costs/rates to budget, culture/safety to guide
- designer complete → transmit daily costs/accommodation budget to budget, daily areas/segments to guide
- budget complete → transmit payment info to guide
- guide complete → if inconsistencies found with itinerary, request adjustment from designer

### Phase 3: Integration and Final Deliverables

1. Verify all files in `_workspace/`
2. Confirm consistency across itinerary-budget-local information
3. Report final summary to user:
    - Destination Analysis — `01_destination_analysis.md`
    - Itinerary — `02_itinerary.md`
    - Accommodation Guide — `03_accommodation.md`
    - Budget Plan — `04_budget.md`
    - Local Guide — `05_local_guide.md`

## Modes by Request Scale

| User Request Pattern | Execution Mode | Agents Deployed |
|---------------------|---------------|-----------------|
| "Plan an entire trip" | **Full Pipeline** | All 4 |
| "Where should I go in Japan?" | **Destination Recommendation** | analyst solo |
| "Paris 3-night itinerary only" | **Itinerary Mode** | analyst + designer |
| "Just calculate travel budget" | **Budget Mode** | budget solo |
| "Info I need while there" | **Guide Mode** | guide solo |
| "Improve this itinerary" (existing file) | **Analysis Mode** | designer + budget |

**Using existing files**: If the user provides an existing itinerary, copy to `_workspace/02_itinerary.md` and skip the designer.

## Data Transfer Protocol

| Strategy | Method | Purpose |
|----------|--------|---------|
| File-based | `_workspace/` directory | Store and share major deliverables |
| Message-based | SendMessage | Real-time key info transfer, revision requests |
| Task-based | TaskCreate/TaskUpdate | Progress tracking, dependency management |

File naming convention: `{order}_{agent}_{deliverable}.{ext}`

## Error Handling

| Error Type | Strategy |
|-----------|----------|
| Web search failure | Work from general knowledge, note "Latest information verification needed" |
| Destination undecided | Recommend 3 destinations based on user criteria |
| Budget exceeded | Present budget alternatives + adjust priorities |
| Agent failure | Retry once → proceed without that deliverable if failed, note omission in report |
| Itinerary-info inconsistency | Request adjustment from designer (up to 2 times) |

## Test Scenarios

### Normal Flow
**Prompt**: "Plan a 4-night 5-day trip to Tokyo for a couple. Budget $1,500, focusing on food tourism."
**Expected Results**:
- Destination analysis: Tokyo attractions, culinary spots, entry requirements, optimal season
- Itinerary: 5-day schedule, food-focused routes, organized by areas like Tsukiji/Shibuya/Shinjuku
- Accommodation: 3 centrally-located recommendations + booking tips
- Budget: Allocation within $1,500 (flights/accommodation/meals/transport), Budget/Standard/Luxury comparison
- Local guide: Transit (Suica), restaurant list, basic Japanese phrases, emergency contacts

### Existing File Flow
**Prompt**: "Check if this itinerary fits the budget and add local info" + attached itinerary file
**Expected Results**:
- Copy existing itinerary to `_workspace/02_itinerary.md`
- 
03

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codeNA
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
pinned
Secrets in source
none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.

Audited 2026-10-12 · audit v0.4.1 · source sha 459e1bb8f76efull audit observations/trust-audit/skill/revfactory__travel-planner.json · Report an issue / request a re-scan
04

Audit history

Every audit this skill has had.

DateSourceVerdictGradeScoreChange
2026-10-12459e1bb8f76eSAFEB89first audit
05

Questions

Is Travel Planner safe to install?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.

What can Travel Planner access on my machine?

The audit observed no filesystem, network or shell use at all in its source.

How current is this page?

The grade is for one exact copy of the source (459e1bb8f76e), read on 2026-10-12. The repository is watched, and a new audit runs when it changes — this is the first audit.

Advertisement