review-week-level

Analyze Week node and Day summaries to detect weekly travel constraint violations.

98|7|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Sea-Go/Sea-BreakTheWaves --skill review-week-level
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-week-level
Source: https://github.com/Sea-Go/Sea-BreakTheWaves/tree/main/agent_v2/skills/review-week-level
Command: npx skills add https://github.com/Sea-Go/Sea-BreakTheWaves --skill review-week-level

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Week-level constraint review helps ensure travel pacing across a week stays within humanly tolerable bounds by checking rest days, transfer days, high-intensity days, and POI density.

Core Features & Use Cases

  • Inputs: Week node and Day summaries from a graph or coordinator.
  • Rules: Enforces restDayCount ≥ 1, transferDayCount ≤ 2, highIntensityDayCount ≤ 4, and POI density limits (average POIs per day ≤ 5 and main stops ≤ 3).
  • Outputs: JSON report with score, passed flag, and a list of constraint violations for actionable remediation.
  • Use cases: itinerary validation, personal planning, and safety-aware scheduling.

Quick Start

Audit a Week node against the defined weekly constraint rules to produce a structured violation report.

Frequently Asked Questions about review-week-level

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is week-level constraint review in travel itinerary validation?

Week-level constraint review is a data validation process that evaluates weekly travel pacing by checking rest days, transfer days, high-intensity days, and POI density against human limits. It outputs a structured JSON report with a score, passed flag, and violation details.

How do I check if my weekly travel itinerary stays within human limits?

To check if your weekly travel pacing is feasible, audit your Week node and Day summaries to enforce rules like restDayCount >= 1, transferDayCount <= 2, and highIntensityDayCount <= 4. This generates a structured violation report for actionable remediation.

What are the POI density limits for a feasible weekly travel schedule?

POI density limits for a feasible weekly travel schedule require an average of 5 POIs per day or fewer, and main stops must not exceed 3. These constraints ensure weekly travel pacing remains within humanly tolerable bounds.

Can I use schedule analysis for habit-tracking workflows?

Yes, schedule analysis applies to habit-tracking workflows where weekly limits determine feasible pacing. By analyzing Week nodes and Day summaries, the risk assessment detects constraint violations and outputs a JSON report to validate your routine.

Why does my itinerary validation report show a failed score?

Itinerary validation reports a failed score when weekly travel pacing violates human limits, such as having zero rest days, more than two transfer days, or exceeding POI density limits. The JSON output details these specific high-intensity day violations.

What inputs do I need to start a week-level schedule analysis?

To start week-level schedule analysis, provide a Week node and its Day summaries from your graph or coordinator. This data feeds the risk assessment to evaluate travel constraints and produce a structured JSON violation report.