← 返回 Skills 市场
harrylabsj

Weekly Errand Route Card

作者 haidong · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ 安全检测通过
74
总下载
0
收藏
0
当前安装
1
版本数
在 OpenClaw 中安装
/install weekly-errand-route-card
功能描述
Build a practical weekly errand route card when the user has too many errands, repeated backtracking, or wasted trips. Use to dump errands, group stops by ar...
使用说明 (SKILL.md)

Weekly Errand Route Card

Purpose

Help the user turn a scattered list of weekly errands into a route card grouped by area, deadline, required items, stop timing, and done status. The goal is fewer wasted trips and fewer forgotten papers, returns, packages, bags, cards, keys, or pickup codes.

This is a prompt-only home and admin planning workflow. It does not provide traffic, navigation, legal, medical, or professional driving advice.

Use This Skill When

Use this skill when the user says they:

  • Have too many errands and keep wasting trips.
  • Need to combine pickups, drop-offs, returns, groceries, pharmacy runs, appointments, post office stops, school tasks, repairs, or household admin.
  • Want errands grouped by neighborhood, area, deadline, hours, or must-bring items.
  • Need a printable or reusable route card with checkboxes.
  • Want help deciding what can be batched, deferred, delegated, or done online.

Do not use it as live navigation, a traffic forecast, emergency dispatch, or advice to ignore store hours, road rules, safety, weather warnings, fatigue, or vehicle limits.

Safety Boundary

  • Keep timing realistic. Add buffers for parking, walking, lines, loading, payment, restrooms, and stop transitions.
  • Do not encourage speeding, distracted driving, unsafe multitasking, illegal parking, risky shortcuts, or driving while tired, impaired, stressed, or unwell.
  • Add safe breaks for long routes, routes with children or dependents, heavy loading, bad weather, unfamiliar areas, or time-sensitive clusters.
  • Recommend rescheduling, splitting the route, using delivery, asking for help, or choosing a safer day if the plan is too tight.
  • For errands involving medications, legal documents, money, school pickup, caregiving, or official deadlines, preserve the user's stated requirements and note uncertainty instead of guessing.
  • Do not invent addresses, hours, policies, fees, traffic conditions, or availability. Use placeholders when details are missing.

Best Inputs

Ask only for details that change the route. If the user does not know, use placeholders and continue.

  • Errand list with stop names, rough locations or areas, and what needs to happen.
  • Deadline or time window for each stop.
  • Store or office hours if known.
  • Required items: IDs, cards, returns, receipts, bags, prescriptions, forms, keys, packages, coolers, coupons, pickup codes, or reusable containers.
  • Start and end location, transport mode, parking constraints, and whether anyone is coming along.
  • Estimated stop duration, urgency, weather concerns, physical load, and energy limits.
  • Errands that can be done online, delegated, skipped, or moved to another day.

Workflow

  1. Dump the errands. Capture every errand as a stop with task, area, deadline, time window, must-bring items, and estimated duration.
  2. Clarify constraints. Flag fixed-time stops, closing times, pickup windows, cold items, heavy loads, child or caregiver constraints, and tasks that require documents or payment.
  3. Group by area. Cluster errands by neighborhood, corridor, building, mall, campus, or direction of travel. Separate online or phone tasks from physical stops.
  4. Prioritize deadlines. Put fixed-time, closing-soon, and high-consequence stops ahead of flexible errands. Mark errands that can wait.
  5. Build the must-bring list. Create a consolidated checklist for items to gather before leaving and items to keep separate by stop.
  6. Sequence the route. Order stops to reduce backtracking while respecting time windows, storage needs, heavy items, parking, and start or end location.
  7. Check timing realism. Add travel placeholders, stop buffers, break points, meal or hydration needs, and a latest-start time if useful.
  8. Mark done and adjust. Provide checkboxes for each stop, a skip or defer column, and a short review section for what to batch differently next week.

Output Format

Return the route card in this order.

1. Planning Safety Check

Briefly state that this is a planning aid, not live navigation or traffic advice. Call out any route that looks too tight, unsafe, too long without breaks, or dependent on missing hours.

2. Errand Dump

Stop Task Area Deadline or window Must-bring items Estimated stop time Status
Not started

3. Area Groups

Area group Stops in this group Why group them Flexible or fixed

Include online, phone, or delivery alternatives as their own group when useful.

4. Deadline and Risk Priorities

Priority Stop or task Reason Action
Fixed-time first
Closing-soon
High-consequence
Flexible or deferrable

5. Must-Bring Checklist

Group items as:

  • Gather before leaving:
  • Keep handy in the car, bag, or pocket:
  • Stop-specific items:
  • Cold, fragile, heavy, or high-value items:
  • Unknown items to confirm:

6. Route Sequence

Order Stop Area Action Time window Bring Buffer Done
1 [ ]

Add route notes below the table:

  • Start location:
  • End location:
  • Suggested latest start:
  • Break points:
  • Parking or loading notes:
  • Stops to split to another day if the route runs late:

7. Realistic Timing Check

Segment Estimated travel or transition Stop time Buffer Running total
Start to Stop 1

Use placeholders for travel time if distances or traffic are unknown. State assumptions plainly.

8. Done and Defer Tracker

Stop Done? If skipped, why? New date or next step
[ ]

9. Next-Week Tune-Up

End with short review questions:

  • Which area grouping saved the most time?
  • Which item was almost forgotten?
  • Which stop should be paired with a regular weekly anchor?
  • Which errand can move online, be delegated, or be dropped?
  • What time buffer should be changed next week?

10. Open Questions

List missing details that would make the route card more specific, such as addresses, hours, appointment windows, required items, vehicle or mobility constraints, or whether cold or heavy items are involved.

Style Rules

  • Be practical, concise, and calm.
  • Use route card language: area, stop, window, must-bring, buffer, break, done, defer.
  • Do not over-optimize. A workable route with enough buffer is better than a fragile perfect route.
  • Keep checklists visible and easy to scan.
  • Preserve user-stated deadlines and uncertain details rather than guessing.
  • Recommend splitting the route when timing, fatigue, weather, or load makes the plan unrealistic.
安全使用建议
This skill appears safe to use as a planning prompt. It may ask for personal errand details such as locations, deadlines, pickup codes, medications, or documents, so share only what is necessary and verify store hours, traffic, road conditions, and safety-critical details yourself.
功能分析
Type: OpenClaw Skill Name: weekly-errand-route-card Version: 1.0.0 The 'weekly-errand-route-card' skill is a prompt-only workflow designed to help users organize errands into a structured route. It contains no executable code, network requests, or sensitive data access, and its instructions (SKILL.md) focus entirely on data organization and safety boundaries for driving.
能力标签
cryptocan-make-purchases
能力评估
Purpose & Capability
The stated purpose and visible instructions consistently focus on organizing errands into area groups, timing, safety buffers, and checklists.
Instruction Scope
The skill includes clear boundaries against live navigation, traffic claims, unsafe driving, invented addresses/hours, and over-tight scheduling.
Install Mechanism
There is no install spec, no required binaries, no required environment variables, and skill.json declares hasExecutableCode=false and requiresApi=false.
Credentials
The requested user inputs, such as locations, deadlines, store hours, and must-bring items, are proportionate to creating an errand route card.
Persistence & Privilege
The artifacts show no persistence mechanism, credential use, privileged access, background execution, or account mutation.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install weekly-errand-route-card
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /weekly-errand-route-card 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v1.0.0
**Initial release – weekly-errand-route-card skill** - Transforms scattered errand lists into a consolidated, area-grouped weekly route card. - Adds planning tools: area grouping by stops, deadline prioritization, must-bring lists, and route sequencing with realistic buffers. - Includes tables for errand dump, area clusters, deadline/risk priorities, must-bring items, and a sequenced checklist with timing and status trackers. - Safety checks and workflow steps ensure no unsafe, rushed, or overloaded routes are planned. - Designed as a printable or reusable planning aid—excludes live navigation and legal/medical advice.
元数据
Slug weekly-errand-route-card
版本 1.0.0
许可证 MIT-0
累计安装 0
当前安装数 0
历史版本数 1
常见问题

Weekly Errand Route Card 是什么?

Build a practical weekly errand route card when the user has too many errands, repeated backtracking, or wasted trips. Use to dump errands, group stops by ar... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 74 次。

如何安装 Weekly Errand Route Card?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install weekly-errand-route-card」即可一键安装,无需额外配置。

Weekly Errand Route Card 是免费的吗?

是的,Weekly Errand Route Card 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

Weekly Errand Route Card 支持哪些平台?

Weekly Errand Route Card 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 Weekly Errand Route Card?

由 haidong(@harrylabsj)开发并维护,当前版本 v1.0.0。

💬 留言讨论